From: "Carlo Nyto" <carlonyto@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Slow tape drive timeout
Date: Tue, 1 Apr 2008 16:30:14 -0400 [thread overview]
Message-ID: <9d95d80e0804011330w53652286j1349ef7fda29bedb@mail.gmail.com> (raw)
I am experiencing a two minute timeout open()ing a tape device when
there is no tape in the drive.
open() with O_NONBLOCK succeeds immediately, however.
The problem is that I am trying to set up Legato on a system that has
multiple tape drives. For certain common operations, Legato tries to
open() each tape drive multiple times. On a system with multiple tape
drives, this adds up to a significant amount of time wasted due to
this timeout.
Solaris does not have this problem, and Legato support advises that
they are at the mercy of the operating system.
Changing the timeout with e.g. "mt -f /dev/nst0 sttimeout 15" does not
change the timeout to 15 seconds, it is still exactly 2 minutes.
This happens with kernel 2.6.24.4, as well as RedHat's 2.6.9-67.
Here is a snippet of strace -T -tt output:
15:56:18.688392 open("/dev/nst0", O_RDONLY) = -1 ENOMEDIUM (No medium
found) <120.480482>
In this case, the tape device is a Quantum DLT-S4 connected to with an
Emulex FC card, via a Fibre Channel SAN.
Any help would be appreciated. Thanks.
next reply other threads:[~2008-04-01 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 20:30 Carlo Nyto [this message]
2008-04-02 5:09 ` Kai Makisara
[not found] <fa.iY7vJs54MoScDgyQ4PUWZsO+3Jw@ifi.uio.no>
[not found] ` <fa.of3hIrxfNefAS08Tzqfm1dI0BOo@ifi.uio.no>
2008-04-03 4:21 ` Robert Hancock
2008-04-03 18:34 ` Kai Makisara
2008-04-04 2:25 ` Robert Hancock
2008-04-04 18:04 ` Kai Makisara
[not found] <aepft-NF-5@gated-at.bofh.it>
[not found] ` <aepft-NF-7@gated-at.bofh.it>
[not found] ` <aepfs-NF-3@gated-at.bofh.it>
[not found] ` <aeCw6-5Yu-35@gated-at.bofh.it>
2008-04-04 9:37 ` Bodo Eggert
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=9d95d80e0804011330w53652286j1349ef7fda29bedb@mail.gmail.com \
--to=carlonyto@gmail.com \
--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
all inboxes | Powered by JetHome®