From: Jakub Bogusz <qboosh@pld-linux.org>
To: linux-kernel@vger.kernel.org
Subject: "attempt to access beyond end of device" on ide-scsi+sr_mod in 2.6.0-test3
Date: Fri, 15 Aug 2003 00:54:37 +0200 [thread overview]
Message-ID: <20030814225437.GA31481@satan.blackhosts> (raw)
Hello,
I mounted my CDRW disk with isofs through ide-scsi as I used to do
in Linux 2.4 (drive is CD recorder, and I'm using 2.6 for testing, so
I haven't changed configuration for direct ATAPI writing).
I successfully read some files, but when I was trying to read more,
I/O errors occurred. Kernel said:
kernel: attempt to access beyond end of device
kernel: sr0: rw=0, want=315596, limit=307404
kernel: Buffer I/O error on device sr0, logical block 78898
kernel: attempt to access beyond end of device
kernel: sr0: rw=0, want=315600, limit=307404
kernel: Buffer I/O error on device sr0, logical block 78899
[...etc., many times...]
I unmounted and mounted again the same disk and everything was OK
- I couldn't repeat that errors. That disk contained ~222MB of data.
But when I inserted _larger_ CD (over 500MB of data) and tried to read
some files, I/O errors happened again:
kernel: attempt to access beyond end of device
kernel: sr0: rw=0, want=1270892, limit=453448
kernel: Buffer I/O error on device sr0, logical block 317722
kernel: attempt to access beyond end of device
kernel: sr0: rw=0, want=1270896, limit=453448
kernel: Buffer I/O error on device sr0, logical block 317723
[...]
But see - now limit matches the _previous_ disk!
unmounting and mounting the same disk helped again.
(I've made even more tests to confirm this)
It seems that kernel updates some device block count too late (after
some data reads?), remembering count for _previous_ mounted disk, not
the current one.
This behaviour is specific for sr_mod and/or ide-scsi.
When I mounted CD through plain ide-cd, such errors didn't happen.
PS. please Cc answers to me
--
Jakub Bogusz http://cyber.cs.net.pl/~qboosh/
PLD Linux http://www.pld-linux.org/
reply other threads:[~2003-08-14 22:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030814225437.GA31481@satan.blackhosts \
--to=qboosh@pld-linux.org \
--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®