FORUMS: list search recent posts

Finding old Quantum LTFS packages

COW Forums : Archiving and Back-Up

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
Ben Powis
Finding old Quantum LTFS packages
on Aug 23, 2018 at 12:31:57 pm

Hello,

I am having a bit of an issue with trying to get our LTO5 archive tapes to read properly in our Quantum LTO5 Half Height Model B tape drives. They are mounting up alright but it seems that they were formatted and had media put onto them using an newer version of the Quantum LTFS software as it comes up with this message in terminal:

LTFS17096W The index read from the tape uses a newer version of the LTFS Format than the one supported by this software. Not all functionality may be available. If this tape is modified, the index will be downgraded to format version 2.0.0.

The issue is that I have downloaded the latest version of Quantum LTFS software and it says the same thing except that the index read from the uses an OLDER version of the LTFS software. So i am stuck now trying to get a hold of the ltfs packages that came in between the two versions that I have, but I can't find anything online on how I would get hold of previous versions of this. The only things I have found are the source versions that you can use to create your own packages but I have struggled with using those and I think it is a bit beyond my technical skill.

Would anyone be able to help me out in tracking these down? Currently the tapes are mounting and showing that the tapes are populated, but there is no media showing on them at all, as if the media is there but invisible.

Many thanks

Ben


Return to posts index

Martin Greenwood
Re: Finding old Quantum LTFS packages
on Aug 23, 2018 at 1:38:13 pm

Indeed it is normal to see that message when reading older tapes with a newer LTFS. Older tapes can be read without issue. However if you don't see any files that that suggests an issue with the tapes. If you want to post or email me the full dialog from the mount command I can take a look.

Best,

Martin Greenwood
martin@yoyotta.com

CTO

YoYotta


Return to posts index

Ben Powis
Re: Finding old Quantum LTFS packages
on Aug 23, 2018 at 1:46:38 pm

Hi Martin,

Thanks very much for lending a hand. I am having the issue with multiple tapes which is making me think that it is to do with the drives communication with the tapes.

I have updated to the latest version of Quantum ICU Framework and LTFS software and it is having the same problem of not showing the media but coming up with a different mount process which I have posted below. I am currently using an LTFS mount script that my predecessor created for mounting and unmounting, I have copied and pasted it into terminal so that you can see that actual commands etc.

QFSHARE:~ admin$ #!/bin/bash
QFSHARE:~ admin$ echo Do not close this window unless it says Process Completed
Do not close this window unless it says Process Completed
QFSHARE:~ admin$ if [ -d "/Volumes/LTFS0" ] ; then
> echo LTFS0 folder already exists - Please run LTFS_unmount_0 to try to clear this
> exit 1
> fi
QFSHARE:~ admin$ INSTANCESOFLTFS=`ps -ax | grep -v grep | grep -i ltfs0 | wc -l`
QFSHARE:~ admin$ if [ $INSTANCESOFLTFS -gt 0 ]; then
> echo LTFS process already running - Please run LTFS0_unmount to try to clear this
> exit 2
> fi
QFSHARE:~ admin$ sudo mkdir /Volumes/LTFS0/
QFSHARE:~ admin$ sudo ltfs /Volumes/LTFS0 -o devname=0 -ovolname=LTFS0
Password:

Sorry, try again.
Password:
Sorry, try again.
Password:
307 LTFS14000I LTFS starting, QUANTUMLTFS Standalone version 2.2.2, log level 2
307 LTFS14058I LTFS Format Specification version 2.2.0
307 LTFS14104I Launched by "ltfs /Volumes/LTFS0 -o devname=0 -ovolname=LTFS0"
307 LTFS14105I This binary is built for Mac OS X
307 LTFS14106I GCC version is 4.2.1 Compatible Clang Compiler
307 LTFS17087I Kernel version: Darwin Kernel Version 17.5.0: Mon Mar 5 22:24:32 PST 2018; root:xnu-4570.51.1~1/RELEASE_X86_64
307 LTFS14063I Sync type is "time", Sync time is 300 sec
307 LTFS17085I Plugin: Loading "ltotape" driver
307 LTFS17085I Plugin: Loading "unified" iosched
307 LTFS20013I Drive type is Quantum LTO5, serial number is HU1304UAGJ, firmware revision is 3210
307 LTFS17160I Maximum device block size is 1048576
307 LTFS11005I Mounting the volume
307 LTFS17302W Cannot retrieve attribute (User Medium Text Label=0x803)
307 LTFS17302W Cannot retrieve attribute (Barcode=0x806)
307 LTFS10023I LTFS volume information:
307 LTFS10031I Volume Name : (null)
307 LTFS10024I Volser(Barcode) :
307 LTFS10025I Volume UUID : 812ada0b-0f57-4b7c-94e7-422d1185d2c1
307 LTFS10026I Format Time : 2016-03-10 13:26:06.386252000 GMT
307 LTFS10027I Block Size : 524288
307 LTFS10028I Compression : Enabled
307 LTFS10029I Index Partition : ID = a, SCSI Partition = 0, Total Capacity = 36476 MiB, Available Space = 36476 MiB
307 LTFS10030I Data Partition : ID = b, SCSI Partition = 1, Total Capacity = 1367865 MiB, Available Space = 180529 MiB

307 LTFS14111I Initial setup completed successfully
307 LTFS14112I Invoke 'mount' command to check the result of final setup
307 LTFS14113I Specified mount point is listed if succeeded

The parts that stand out to me are the two "Cannot retrieve attribute" messages.

Kind Regards,

Ben


Return to posts index


Martin Greenwood
Re: Finding old Quantum LTFS packages
on Aug 24, 2018 at 8:34:33 am

The attribute messages can be ignored, they just indicate an older format.

Data has been written to the tape as the available data space shown is approx 180GB. However the index space shows no usage... this isn't expected. Even with an newly formatted tape the available space on the index partition should be less than the total index capacity. So this might indicate corruption. Do you see this same result with other tapes?

It's as if the data has been deleted from the tape using Finder or Explorer. When this happens the data isn't actually removed. So the space is still used, but a new index is created making the old files disappear.
This is because LTFS always appends new files, never overwriting existing files.

Each time a group of new files are written to, or deleted from an LTFS tape a new index is created and it's possible to rollback to previous generations (rollback points).

A plug for our YoYotta LTFS software here... if using our app then each generation will be labeled telling you the stage of the archive, writing/copied/complete and also the source file path. This makes it easy to find the required generation if files have been accidentally removed or the tape index has been damaged due to an equipment or power failure.

So the next step would be to list the available generations by typing this into a terminal.

ltfsck -l 0

Hopefully you will see some Generations listed. You can then mount the tape (in a read-only mode) at a previous generation when the files still existed using this command. Replacing the 10 with the required generation.

ltfs /Volumes/LTFS -o devname=0 -o rollback_mount=10

If nothing is listed then the empty index partition may be preventing access to the files. You would then need to get a recovery specialist to look at the tapes.

Good luck !

Martin

CTO

YoYotta.com


Return to posts index

Ben Powis
Re: Finding old Quantum LTFS packages
on Aug 29, 2018 at 1:26:58 pm

Hi Martin,

Once again thank you so much for taking the time to help me out with this.

The element that concerns me and makes me think that it is not an issue with the tapes is that this issue is occurring with every single LTO 5 tape from our archive that I am mounting up in the tape drives. They are still the same tape drives we have been using for many years so there is no change there, the only difference is the change in LTFS software and OS that has changed since this issue occurred.

I have used a tape and rolled back to a previous generation and it is now showing up with the media, so I guess it is acting like the media has been corrupted, but that seems like something that would be so unlikely to happen to all LTO 5 archive tapes that we have?

Cheers,

Ben


Return to posts index

Martin Greenwood
Re: Finding old Quantum LTFS packages
on Aug 29, 2018 at 1:54:48 pm

After rolling back what is the output from the mount command? Keen to see if the Index is showing some space used now.

I agree that it's odd if all tapes are like this. Only thing I can say is in past we have done a lot of forward and backwards version mounting of LTFS tapes without seeing any data disappear.

Also what was the initial output of the ltfsck -l 0 command ?
When was the last generation written ? This timestamp is the update to the tape that wiped the data so the date might give you a clue as to what has happened...

Martin

YoYotta.com


Return to posts index


Ben Powis
Re: Finding old Quantum LTFS packages
on Aug 29, 2018 at 4:33:33 pm

Hi Martin,

Here is the output of what happens after the mount command is issued when rolling back to the most recent generation that was before recent checks (back in 2012). It appears that the index partition still isn't showing and kind of population, would this be pointing to an issue with the tape drives being able to read the index partition as opposed to it not actually being populated?

QFSHARE:~ admin$ ltfs /Volumes/LTFS -o devname=0 -o rollback_mount=40
307 LTFS14000I LTFS starting, QUANTUMLTFS Standalone version 2.2.2, log level 2
307 LTFS14058I LTFS Format Specification version 2.2.0
307 LTFS14104I Launched by "ltfs /Volumes/LTFS -o devname=0 -o rollback_mount=40"
307 LTFS14105I This binary is built for Mac OS X
307 LTFS14106I GCC version is 4.2.1 Compatible Clang Compiler
307 LTFS17087I Kernel version: Darwin Kernel Version 17.5.0: Mon Mar 5 22:24:32 PST 2018; root:xnu-4570.51.1~1/RELEASE_X86_64
307 LTFS14063I Sync type is "time", Sync time is 300 sec
307 LTFS17085I Plugin: Loading "ltotape" driver
307 LTFS17085I Plugin: Loading "unified" iosched
307 LTFS20013I Drive type is Quantum LTO5, serial number is HU1304UAGJ, firmware revision is 3210
307 LTFS17160I Maximum device block size is 1048576
307 LTFS11005I Mounting the volume
307 LTFS17302W Cannot retrieve attribute (User Medium Text Label=0x803)
307 LTFS17302W Cannot retrieve attribute (Barcode=0x806)
307 LTFS17095W The index read from the tape uses an old version of the LTFS format. If this tape is modified, the index upgrades format version to 2.2.0 from 2.0.0.
307 LTFS17077I Traverse(B): find target generation 40 (b)
307 LTFS10023I LTFS volume information:
307 LTFS10031I Volume Name : (null)
307 LTFS10024I Volser(Barcode) :
307 LTFS10025I Volume UUID : 0958792f-c2ab-4451-b5e2-507091e8862c
307 LTFS10026I Format Time : 2012-12-18 14:49:14.513681000 GMT
307 LTFS10027I Block Size : 524288
307 LTFS10028I Compression : Enabled
307 LTFS10029I Index Partition : ID = a, SCSI Partition = 0, Total Capacity = 36476 MiB, Available Space = 36476 MiB
307 LTFS10030I Data Partition : ID = b, SCSI Partition = 1, Total Capacity = 1367865 MiB, Available Space = 574040 MiB

307 LTFS14072I Rollback mount is specified. Mounting as read-only at generation 40.
307 LTFS14111I Initial setup completed successfully
307 LTFS14112I Invoke 'mount' command to check the result of final setup
307 LTFS14113I Specified mount point is listed if succeeded

In terms of the initial output of the ltfsck command it has come up with this:

LTFS16000I Starting ltfsck, QUANTUMLTFS Standalone version 2.2.2, log level 2
LTFS16088I Launched by "ltfsck -l 0"
LTFS16089I This binary is built for Mac OS X
LTFS16090I GCC version is 4.2.1 Compatible Clang Compiler
LTFS17087I Kernel version: Darwin Kernel Version 17.5.0: Mon Mar 5 22:24:32 PST 2018; root:xnu-4570.51.1~1/RELEASE_X86_64
LTFS16084I List indexes in backward direction strategy
LTFS17085I Plugin: Loading "ltotape" driver
LTFS20013I Drive type is Quantum LTO5, serial number is HU1304UAGJ, firmware revision is 3210
LTFS17160I Maximum device block size is 1048576
LTFS16018I Listing LTFS file system rollback points on '0'
LTFS16023I LTFS volume information:
LTFS16024I Volser (bar code) :
LTFS16025I Volume UUID : 0958792f-c2ab-4451-b5e2-507091e8862c
LTFS16026I Format time : 2012-12-18 14:49:14.513681000 GMT
LTFS16027I Block size : 524288
LTFS16028I Compression : Enabled
LTFS16029I Index partition : ID = a, SCSI Partition = 0
LTFS16030I Data partition : ID = b, SCSI Partition = 1

LTFS11005I Mounting the volume
LTFS17302W Cannot retrieve attribute (User Medium Text Label=0x803)
LTFS17302W Cannot retrieve attribute (Barcode=0x806)
LTFS10023I LTFS volume information:
LTFS10031I Volume Name : (null)
LTFS10024I Volser(Barcode) :
LTFS10025I Volume UUID : 0958792f-c2ab-4451-b5e2-507091e8862c
LTFS10026I Format Time : 2012-12-18 14:49:14.513681000 GMT
LTFS10027I Block Size : 524288
LTFS10028I Compression : Enabled
LTFS10029I Index Partition : ID = a, SCSI Partition = 0, Total Capacity = 36476 MiB, Available Space = 36476 MiB
LTFS10030I Data Partition : ID = b, SCSI Partition = 1, Total Capacity = 1367865 MiB, Available Space = 574040 MiB

Generation: Date Time Zone SelfPtr->BackPtr (Part, Pos)
(UTC Date UTC Time UTC)
Commit Message
-------------------------------------------------------------------------------
42: 2018-08-29 14:27:10.453985420 BST (0, 5)->(1, 1627160)
(2018-08-29 13:27:10.453985420 UTC)
No commit message
42: 2018-08-29 14:27:10.453985420 BST (1, 1627160)->(1, 1627156)
(2018-08-29 13:27:10.453985420 UTC)
No commit message
41: 2018-08-29 13:27:08.972121309 BST (1, 1627156)->(1, 1627149)
(2018-08-29 12:27:08.972121309 UTC)
No commit message
LTFS17095W The index read from the tape uses an old version of the LTFS format. If this tape is modified, the index upgrades format version to 2.2.0 from 2.0.0.
40: 2012-12-18 18:10:19.014665000 GMT (1, 1627149)->(1, 1611298)
(2012-12-18 18:10:19.014665000 UTC)
No commit message
LTFS17095W The index read from the tape uses an old version of the LTFS format. If this tape is modified, the index upgrades format version to 2.2.0 from 2.0.0.
39: 2012-12-18 18:05:17.018265000 GMT (1, 1611298)->(1, 1559845)
(2012-12-18 18:05:17.018265000 UTC)
No commit message

And it then continues to roll back through the generations until it gets down to 1.

Kind Regards,

Ben


Return to posts index

Martin Greenwood
Re: Finding old Quantum LTFS packages
on Aug 29, 2018 at 4:50:25 pm

The index size probably isn't relevant. I would guess this is just a difference in the earlier LTFS format.

Was the first tape you tried write-protected from the start?
I would suggest trying another tape and ensuring it's write protected before loading.

Then see if your files are visible after mounting.
If not then at least you can perform the roll back mount command to access files on the tapes.

Best,

Martin

YoYotta.com


Return to posts index

<< PREVIOUS   •   VIEW ALL   •   PRINT   •   NEXT >>
© 2018 CreativeCOW.net All Rights Reserved
[TOP]