Results 1 to 9 of 9

Thread: amlabel errors

Hybrid View

  1. #1
    Join Date
    Jan 2014
    Posts
    6

    Default amlabel errors

    Hi,

    Because of the good comments, I decided to give amanda community version a try instead of custom tape archiving scripts.

    When I did a test with virtual tapes, all went well but now I try to apply it to a real taperobot scenario.

    The problem is that I cannot label any tapes: (here I loaded tape from slot 23)

    [[email protected] ~]$ amlabel set01 set01-23
    Reading label...
    Found an empty tape.
    Writing label 'set01-23'...
    Checking label...
    Checking the tape label failed: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy


    This error, I receive with any tape in the robot.

    I can read and write with tar to the tapes without issues.

    tape writer is /dev/nst0
    tape robot is /dev/sg1

    Status:
    [[email protected] ~]$ mt -f /dev/nst0 status
    SCSI 2 tape drive:
    File number=0, block number=0, partition=0.
    Tape block size 0 bytes. Density code 0x46 (LTO-4).
    Soft error count since last status=0
    General status bits on (41010000):
    BOT ONLINE IM_REP_EN

    It seems that the next tape was loaded automatically after trying the amlabel on slot 23:

    [[email protected] ~]$ mtx -f /dev/sg1 status
    Storage Changer /dev/sg1:1 Drives, 24 Slots ( 0 Import/Export )
    Data Transfer Element 0:Full (Storage Element 24 Loaded)
    Storage Element 1:Full
    Storage Element 2:Full
    Storage Element 3:Full
    Storage Element 4:Full
    Storage Element 5:Full
    Storage Element 6:Full
    Storage Element 7:Full
    Storage Element 8:Full
    Storage Element 9:Full
    Storage Element 10:Full
    Storage Element 11:Full
    Storage Element 12:Full
    Storage Element 13:Full
    Storage Element 14:Full
    Storage Element 15:Full
    Storage Element 16:Full
    Storage Element 17:Full
    Storage Element 18:Full
    Storage Element 19:Full
    Storage Element 20:Full
    Storage Element 21:Full
    Storage Element 22:Full
    Storage Element 23:Full
    Storage Element 24:Empty


    In case it can be helpfull, this is my tape type as provided by the amtape command:

    define tapetype LTO4 {
    comment "SUN LTO4 (HP G3) Created by amtapetype; compression disabled"
    length 794402368 kbytes
    filemark 1416 kbytes
    speed 77479 kps
    #blocksize 64 kbytes
    readblocksize 1m
    }


    Any advice to get the labeling correct? It seems that without labeling I cannot continue with the dumps and amcheck will always fail on the issue of the labeling.


    thanks.

  2. #2
    Join Date
    Jan 2014
    Posts
    6

    Default

    for the record, this is what amcheck gives me:

    [[email protected]]$ amcheck set01
    Amanda Tape Server Host Check
    -----------------------------
    Holding disk /amanda/holding/set01/hd1: 176644096 kB disk space available, using 52428800 kB as requested
    slot 24: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 1: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 2: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 3: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 4: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 5: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 6: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 7: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 8: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 9: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 10: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 11: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 12: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 13: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 14: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 15: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 16: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 17: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 18: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 19: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 20: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 21: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 22: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    slot 23: Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy
    all slots have been loaded
    Taper scan algorithm did not find an acceptable volume.
    (expecting a new volume)
    ERROR: No acceptable volumes found
    NOTE: conf info dir /var/lib/amanda/set01/curinfo does not exist
    NOTE: it will be created on the next run.
    Server check took 2006.632 seconds

    Amanda Backup Client Hosts Check
    --------------------------------
    Client check: 0 hosts checked in 0.000 seconds. 0 problems found.

    (brought to you by Amanda 3.3.5)



    and this is the debug output

    [[email protected]]$ cat /var/log/amanda/server/set01/amcheck.20140116100257.debug
    Thu Jan 16 10:02:57 2014: thd-0xc4f4d0: amcheck: pid 26228 ruid 0 euid 500 version 3.3.5: start at Thu Jan 16 10:02:57 2014
    Thu Jan 16 10:02:57 2014: thd-0xc4f4d0: amcheck: pid 26228 ruid 0 euid 500 version 3.3.5: rename at Thu Jan 16 10:02:57 2014
    Thu Jan 16 10:02:57 2014: thd-0xc4f4d0: amcheck-server: Spawning "/usr/libexec/amanda/amcheck-device /usr/libexec/amanda/amcheck-device set01" in pipeline
    Thu Jan 16 10:36:23 2014: thd-0xc4f4d0: amcheck-server: userbad: 0
    Thu Jan 16 10:36:23 2014: thd-0xc4f4d0: amcheck-server: confbad: 0
    Thu Jan 16 10:36:23 2014: thd-0xc4f4d0: amcheck-server: tapebad: 1
    Thu Jan 16 10:36:23 2014: thd-0xc4f4d0: amcheck-server: disklow: 0
    Thu Jan 16 10:36:23 2014: thd-0xc4f4d0: amcheck-server: logbad: 0
    Thu Jan 16 10:36:23 2014: thd-0xc4f4d0: amcheck-server: infobad: 0
    Thu Jan 16 10:36:23 2014: thd-0xc4f4d0: amcheck-server: indexbad: 0
    Thu Jan 16 10:36:23 2014: thd-0xc4f4d0: amcheck-server: pgmbad: 0
    Thu Jan 16 10:36:23 2014: thd-0xc4f4d0: amcheck: pid 26228 finish time Thu Jan 16 10:36:23 2014


    TapeBAD worries me because it only seems an issue in amanda, not with normal tar.

    Is it possible that my tapedrive is not supported by Amanda for some reason?

    [[email protected] ~]# mtx -f /dev/sg1 inquiry
    Product Type: Medium Changer
    Vendor ID: 'HP '
    Product ID: 'MSL G3 Series '
    Revision: 'E.00'
    Attached Changer API: No

  3. #3
    Join Date
    Jan 2014
    Posts
    6

    Default

    In meantime, I tried following test to find why the device is locked but could not find any.

    [[email protected] ~]# find /proc/ -wholename '/proc/*/fd/*' -ls | grep -i "nst"
    find: `/proc/23709/task/23709/fd/5': No such file or directory
    find: `/proc/23709/fd/5': No such file or directory

    [[email protected] ~]# lsof | grep -i nst

    [[email protected] ~]# lsof | grep -i sg1
    [[email protected] ~]# find /proc/ -wholename '/proc/*/fd/*' -ls | grep -i "sg1"
    find: `/proc/24189/task/24189/fd/5': No such file or directory
    find: `/proc/24189/fd/5': No such file or directory

    => so nothing to see here


    I tested dd to write to tape which worked like a charm, no msg whatsoever.

    It seems scsci connected and since all hardware is working fine with tar and dd I assume that there is no module or other driver issue, is that correct?


    thanks.

  4. #4
    Join Date
    Nov 2005
    Location
    Canada
    Posts
    1,049

    Default

    Can you post the amlabel debug file and the amcheck-device debug file.

  5. #5
    Join Date
    Jan 2014
    Posts
    6

    Default

    the amcheck-device.20140116100257.debug is in fact a sequence of the same messages; one for every tape in the changer:

    <begin of the log>
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: pid 26231 ruid 500 euid 500 version 3.3.5: start at Thu Jan 16 10:02:57 2014
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: pid 26231 ruid 500 euid 500 version 3.3.5: rename at Thu Jan 16 10:02:57 2014
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: chg-robot: using statefile '/var/amanda/chg-robot-dev-sg1'
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: Amanda::Taper::Scan::traditional stage 1: search for oldest reusable volume
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: Amanda::Taper::Scan::traditional no oldest reusable volume
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: Amanda::Taper::Scan::traditional stage 2: scan for any reusable volume
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: invoking /usr/sbin/mtx -f /dev/sg1 status
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Changer /dev/sg1:1 Drives, 24 Slots ( 0 Import/Export )
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Data Transfer Element 0:Full (Storage Element 24 Loaded)
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 1:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 2:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 3:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 4:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 5:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 6:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 7:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 8:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 9:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 10:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 11:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 12:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 13:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 14:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 15:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 16:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 17:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 18:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 19:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 20:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 21:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 22:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 23:Full
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: mtx: Storage Element 24:Empty
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: my_robot: updating state
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: my_robot: requested volume is already in drive 0
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: my_robot: polling 'tape:/dev/nst0' to see if it's ready
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: Device is in variable block size
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: Device tape:/dev/nst0 error = 'Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device
    or resource busy'
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: Device tape:/dev/nst0 setting status flag(s): DEVICE_STATUS_DEVICE_ERROR, DEVICE_STATUS_VOLUME_UNLABELED, and DEVICE_STATUS_VOLUME_ERROR
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: my_robot: setting current slot to 24
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: my_robot: too early for another 'status' invocation
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: Amanda::Taper::Scan::traditional stage 2: scan for any reusable volume
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: my_robot: too early for another 'status' invocation
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: my_robot: loading next relative to 24: 1
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: my_robot: using drive 0
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: my_robot: unloading drive 0
    Thu Jan 16 10:02:57 2014: thd-0x1199b40: amcheck-device: invoking /usr/sbin/mtx -f /dev/sg1 unload 24 0
    Thu Jan 16 10:03:42 2014: thd-0x1199b40: amcheck-device: my_robot: unload complete
    Thu Jan 16 10:03:42 2014: thd-0x1199b40: amcheck-device: invoking /usr/sbin/mtx -f /dev/sg1 load 1 0
    Thu Jan 16 10:04:33 2014: thd-0x1199b40: amcheck-device: my_robot: polling 'tape:/dev/nst0' to see if it's ready
    Thu Jan 16 10:04:33 2014: thd-0x1199b40: amcheck-device: Device is in variable block size
    Thu Jan 16 10:04:33 2014: thd-0x1199b40: amcheck-device: Device tape:/dev/nst0 error = 'Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy'
    Thu Jan 16 10:04:33 2014: thd-0x1199b40: amcheck-device: Device tape:/dev/nst0 setting status flag(s): DEVICE_STATUS_DEVICE_ERROR, DEVICE_STATUS_VOLUME_UNLABELED, and DEVICE_STATUS_VOLUME_ERROR
    Thu Jan 16 10:04:33 2014: thd-0x1199b40: amcheck-device: my_robot: setting current slot to 1
    Thu Jan 16 10:04:33 2014: thd-0x1199b40: amcheck-device: invoking /usr/sbin/mtx -f /dev/sg1 status
    ...
    (repeat for every tape)
    ...
    Thu Jan 16 10:36:23 2014: thd-0x1199b40: amcheck-device: my_robot: updating state
    Thu Jan 16 10:36:23 2014: thd-0x1199b40: amcheck-device: Amanda::Taper::Scan::traditional stage 2: scan for any reusable volume
    Thu Jan 16 10:36:23 2014: thd-0x1199b40: amcheck-device: my_robot: too early for another 'status' invocation
    Thu Jan 16 10:36:23 2014: thd-0x1199b40: amcheck-device: my_robot: no next slot relative to 23
    Thu Jan 16 10:36:23 2014: thd-0x1199b40: amcheck-device: new Amanda::Changer::Error: type='failed', reason='notfound', message='all slots have been loaded'
    Thu Jan 16 10:36:23 2014: thd-0x1199b40: amcheck-device: Amanda::Taper::Scan::traditional result: scan failed
    Thu Jan 16 10:36:23 2014: thd-0x1199b40: amcheck-device: pid 26231 finish time Thu Jan 16 10:36:23 2014

    <end of the log>

  6. #6
    Join Date
    Jan 2014
    Posts
    6

    Default

    for amlabel.20140116131853.debug :

    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: pid 24503 ruid 500 euid 500 version 3.3.5: start at Thu Jan 16 13:18:53 2014
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: Arguments: kmska_set01 kmska_set01-23
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: pid 24503 ruid 500 euid 500 version 3.3.5: rename at Thu Jan 16 13:18:53 2014
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: chg-robot: using statefile '/var/amanda/chg-robot-dev-sg1'
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: invoking /usr/sbin/mtx -f /dev/sg1 status
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Changer /dev/sg1:1 Drives, 24 Slots ( 0 Import/Export )
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Data Transfer Element 0:Full (Storage Element 23 Loaded)
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 1:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 2:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 3:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 4:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 5:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 6:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 7:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 8:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 9:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 10:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 11:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 12:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 13:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 14:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 15:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 16:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 17:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 18:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 19:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 20:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 21:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 22:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 23:Empty
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: mtx: Storage Element 24:Full
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: my_robot: updating state
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: my_robot: requested volume is already in drive 0
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: my_robot: polling 'tape:/dev/nst0' to see if it's ready
    Thu Jan 16 13:18:53 2014: thd-0x2486780: amlabel: Device is in variable block size
    Thu Jan 16 13:18:59 2014: thd-0x2486780: amlabel: Device tape:/dev/nst0 error = 'Error reading Amanda header: Error reading 1048576 bytes from /dev/nst0: Device or resource busy'
    Thu Jan 16 13:18:59 2014: thd-0x2486780: amlabel: Device tape:/dev/nst0 setting status flag(s): DEVICE_STATUS_DEVICE_ERROR, DEVICE_STATUS_VOLUME_UNLABELED, and DEVICE_STATUS_VOLUME_ERROR
    Thu Jan 16 13:18:59 2014: thd-0x2486780: amlabel: Building type TAPESTART header of 1048576-1048576 bytes with name='kmska_set01-23' disk='' dumplevel=0 and blocksize=1048576
    Thu Jan 16 13:18:59 2014: thd-0x2486780: amlabel: Device tape:/dev/nst0 error = 'Error writing tapestart header: Kernel gave unexpected write() result of "Device or resource busy" on device /dev/nst0'
    Thu Jan 16 13:18:59 2014: thd-0x2486780: amlabel: Device tape:/dev/nst0 setting status flag(s): DEVICE_STATUS_DEVICE_ERROR
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: invoking /usr/sbin/mtx -f /dev/sg1 status
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Changer /dev/sg1:1 Drives, 24 Slots ( 0 Import/Export )
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Data Transfer Element 0:Full (Storage Element 23 Loaded)
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 1:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 2:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 3:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 4:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 5:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 6:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 7:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 8:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 9:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 10:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 11:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 12:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 13:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 14:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 15:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 16:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 17:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 18:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 19:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 20:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 21:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 22:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 23:Empty
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: mtx: Storage Element 24:Full
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: my_robot: updating state
    Thu Jan 16 13:19:02 2014: thd-0x2486780: amlabel: pid 24503 finish time Thu Jan 16 13:19:02 2014

  7. #7
    Join Date
    Jan 2014
    Posts
    6

    Default

    In the meantime, I found something more or less interesting:

    I have no trouble writing or readin to tape as stated before.

    While I'm writing my own script for tape backup, I found that the "tell" option of mt gave me the same input/output error.

    [[email protected] taper]# mt -f /dev/nst0 eod
    [[email protected] taper]# mt -f /dev/nst0 tell

    somewhere on the net I found this option:
    mt -f /dev/nst0 stsetoptions scsi2logical

    After which the tell function works:
    [[email protected] taper]# mt -f /dev/nst0 tell
    At block 2.

    At least it shows something that is not an error.


    However, this setting did not help with the amanda input/output problem.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •