public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ruud Linders <rkmp@xs4all.nl>
To: linux-kernel@vger.kernel.org
Cc: Kai.Makisara@kolumbus.fi
Subject: Re: SCSI Tape hangs when no tape loaded (2.5.6x)
Date: Sun, 16 Feb 2003 17:21:15 +0100	[thread overview]
Message-ID: <3E4FBA7B.8010808@xs4all.nl> (raw)


Kai,

That did it !

I was running mt-st-0.5b, upgrading to 0.7 fixed the 'mt' command as
well as the 'stinit' command which caused my boot to delay for 2 minutes
as that was called from the boot scripts.

THanks
 >On Sun, 16 Feb 2003, Ruud Linders wrote:
 >
 >>
 >>
 >> On both 2.5.60 and 2.5.61 when there is no tape loaded in my SCSI DAT
 >> tape drive, access to the drive blocks for exactly 2 minutes
 >> before timing out and giving an I/O error.
 >>
 >> # mt stat
 >> ....... < 2 minutes later > ...
 >> /dev/tape: Input/output error
 >>
 >Does you mt open the tape device with the O_NONBLOCK option? If not, this
 >is what is expected. mt-st version >= 0.6 does use this option. I don't
 >know about other mt's.
 >
 >The open() behaviour of st was changed at 2.5.3 to conform with SUS
 >(blocking) and what the other Unices do (timeout). If the device is opened
 >without O_NONBLOCK, the driver waits for some time (default 2 minutes) for
 >the device to become ready. If it does not become ready, an error is 
returned.
 >
 >	Kai
 >
 >P.S. I just tested 2.5.61 and in my system 'mt status' without tape in
 >the drive works as expected (i.e., prints status immediately).
 >


             reply	other threads:[~2003-02-16 16:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-16 16:21 Ruud Linders [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-16 14:17 SCSI Tape hangs when no tape loaded (2.5.6x) Ruud Linders
2003-02-16 15:25 ` Kai Makisara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E4FBA7B.8010808@xs4all.nl \
    --to=rkmp@xs4all.nl \
    --cc=Kai.Makisara@kolumbus.fi \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox