Help

Start a discussion
UNSOLVED

gmoreno1

updated

19 years ago

G

gmoreno1

11 Posts

0

3523

September 24th, 2007 07:00

Inappropriate ioctl for device

On a storage node, when I run the inquire command, I have the folowin message:
NetWorker: SYSTEM error: failed to set SCSI timeout on device '/dev/nst0' (Inappropriate ioctl for device)

scsidev@2.2.0: |Disk, /dev/nst0
NetWorker: SYSTEM error: failed to set SCSI timeout on device '/dev/nst1' (Inappropriate ioctl for device)

scsidev@2.3.0: |Disk, /dev/nst1

if I run the stinit command, the result is:
stinit, processing tape 0
The manufacturer is 'IBM', product is 'ULTRIUM-TD3', and revision '6B20'.

stinit, processing tape 1
The manufacturer is 'IBM', product is 'ULTRIUM-TD3', and revision '6B20'.
This is OK, but inquire can't access to the tape drive.

Someone know what is the problem?

Thanks
  • D

    dpinink_silva

    2 Intern

    •

    724 Posts

    2474

    0

    Posted September 24th, 2007 07:00

    I've seem this ioctl error sometimes when tty is not configured correctly. Does the drive works fine? If you can configure and use the drives without problems, I believe you can ignore this error on inquire.
  • B

    ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    2474

    0

    Posted September 24th, 2007 12:00

    In your case, inappropriate ioctl is caused by the fact that your nst devices are recognized as disks (see inquire output). To have it strange even more, nst1 gets reported on 2 different targets.

    What do you get when checking devices with mt command?
  • B

    ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    2474

    0

    Posted September 24th, 2007 12:00

    Oh, and those are IBM drives... which usually come with set of their own drivers.. you do use them? Not sure if on Linux they create separate set of device path (on HPUX and Solaris they do if used).
  • G

    gmoreno1

    11 Posts

    2474

    0

    Posted September 24th, 2007 14:00

    Hi:

    mt output

    SCSI 2 tape drive:
    File number=-1, block number=-1, partition=0.
    Tape block size 0 bytes. Density code 0x0 (default).
    Soft error count since last status=0
    General status bits on (50000):
    DR_OPEN IM_REP_EN

    SCSI 2 tape drive:
    File number=-1, block number=-1, partition=0.
    Tape block size 0 bytes. Density code 0x0 (default).
    Soft error count since last status=0
    General status bits on (8050000):
    EOD DR_OPEN IM_REP_EN

    Gabriel.
  • B

    ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    2474

    0

    Posted September 24th, 2007 14:00

    First is ok (empty drive), second one is strange (I would expect BOT rather than EOD). What about IBM drivers?
  • G

    gmoreno1

    11 Posts

    2474

    0

    Posted September 24th, 2007 15:00

    On dell Web Site is not present drivers for LINUX.

    stinit.conf maybe????? this file is not present on server......


    gabriel.
  • B

    ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    2474

    0

    Posted September 25th, 2007 07:00

    What about IBM ftp? Anyway, LTO3 and stinit.def reference can be easily be traced with Google.

Dell Support Resources

Latest Solutions

View More