From: bugme-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 12207] New: block reads/writes > 122880 bytes to USB tape drive gives EBUSY
Date: Fri, 12 Dec 2008 13:41:43 -0800 (PST) [thread overview]
Message-ID: <bug-12207-11613@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=12207
Summary: block reads/writes > 122880 bytes to USB tape drive
gives EBUSY
Product: IO/Storage
Version: 2.5
KernelVersion: 2.6.16
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: SCSI
AssignedTo: linux-scsi@vger.kernel.org
ReportedBy: philipm@sybase.com
Latest working kernel version: 2.6.13
Earliest failing kernel version: 2.6.16 (that I've been able to test, may be
2.6.14)
Distribution: Red Hat Enterprise 4, 5, Fedora 9, SuSE 9, 10, SuSE Enterprise
10, and Ubuntu 8.04 tested
Hardware Environment: both x86 and amd64 on server, Quantum CD160UE-SST tape
drive with 80/160 GB tape
Software Environment: Linux
Problem Description:
Any attempt to read() or write() more than 122880 bytes at a time to the USB
tape device results in EBUSY.
Steps to reproduce:
This happened inside our application when attempting to do a backup with a
large write size. However, it can be reproduced with tar:
- tar -b 240 -cf /dev/st0 foo (works)
- tar -b 241 -cf /dev/st0 foo
tar: /dev/st0: Cannot write: Device or resource busy
tar: Error is not recoverable: exiting now
The reads and writes worked fine in 2.6.13 and earlier.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-12-12 21:42 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 21:41 bugme-daemon [this message]
2008-12-22 17:44 ` [Bug 12207] block reads/writes > 122880 bytes to USB tape drive gives EBUSY bugme-daemon
2008-12-22 18:08 ` bugme-daemon
2008-12-22 18:09 ` bugme-daemon
2008-12-22 18:09 ` bugme-daemon
2008-12-23 7:30 ` bugme-daemon
2008-12-23 12:31 ` Oliver Neukum
2008-12-23 12:32 ` bugme-daemon
2008-12-23 13:56 ` bugme-daemon
2008-12-23 13:59 ` bugme-daemon
2008-12-23 14:47 ` Boaz Harrosh
2008-12-23 14:55 ` James Bottomley
2008-12-23 15:33 ` James Bottomley
2008-12-23 14:42 ` bugme-daemon
2008-12-23 14:46 ` bugme-daemon
2008-12-23 14:48 ` bugme-daemon
2008-12-23 14:54 ` bugme-daemon
2008-12-23 14:56 ` bugme-daemon
2008-12-23 15:33 ` bugme-daemon
2008-12-23 16:18 ` bugme-daemon
2008-12-23 16:30 ` Kai Makisara
2008-12-23 16:42 ` James Bottomley
2008-12-23 16:30 ` bugme-daemon
2008-12-23 16:42 ` bugme-daemon
2008-12-24 2:56 ` bugme-daemon
2008-12-24 4:19 ` FUJITA Tomonori
2008-12-24 4:19 ` bugme-daemon
2008-12-30 19:39 ` bugme-daemon
2009-02-05 21:12 ` bugme-daemon
2009-02-05 21:48 ` bugme-daemon
2009-03-09 20:48 ` bugme-daemon
2009-03-09 20:55 ` bugme-daemon
2009-03-22 20:52 ` bugme-daemon
2009-03-26 19:35 ` bugzilla-daemon
2009-04-07 10:43 ` bugzilla-daemon
2009-04-09 21:08 ` bugzilla-daemon
2009-04-10 9:48 ` bugzilla-daemon
2009-04-10 15:19 ` bugzilla-daemon
2009-04-10 19:29 ` bugzilla-daemon
2009-04-11 2:38 ` bugzilla-daemon
2009-04-11 6:12 ` bugzilla-daemon
2009-04-11 14:26 ` bugzilla-daemon
2009-04-15 9:55 ` bugzilla-daemon
2009-04-15 15:42 ` bugzilla-daemon
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=bug-12207-11613@http.bugzilla.kernel.org/ \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.