Forum Replies Created

  • Ben Powis

    August 29, 2018 at 4:33 pm in reply to: Finding old Quantum LTFS packages

    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

  • Ben Powis

    August 29, 2018 at 1:26 pm in reply to: Finding old Quantum LTFS packages

    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

  • Ben Powis

    August 23, 2018 at 1:46 pm in reply to: Finding old Quantum LTFS packages

    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

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy