LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
Cc: Mark Lord <lkml@rtr.ca>,
Frank van Maarseveen <frankvm@frankvm.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
linux-kernel@vger.kernel.org, Alan Cox <alan@redhat.com>
Subject: Re: libata /dev/scd0 problem: mount after burn fails without eject
Date: Fri, 04 May 2007 10:16:32 +0200 [thread overview]
Message-ID: <463AEBE0.7010506@gmail.com> (raw)
In-Reply-To: <6bffcb0e0705010731v44cfad1awf4342121245f7ab3@mail.gmail.com>
Michal Piotrowski wrote:
> On 01/05/07, Mark Lord <lkml@rtr.ca> wrote:
>> Forwarding to linux-scsi and linux-ide mailing lists.
>>
>> Frank van Maarseveen wrote:
>> > Tested on 2.6.20.6 and 2.6.21.1
>> >
>> > I decided to swich from the old IDE drivers to libata and now there
>> > seems to be a little but annoying problem: cannot mount an ISO image
>> > after burning it.
>> >
>> > May 1 14:32:55 kernel: attempt to access beyond end of device
>> > May 1 14:32:55 kernel: sr0: rw=0, want=68, limit=4
>> > May 1 14:32:55 kernel: isofs_fill_super: bread failed, dev=sr0,
>> iso_blknum=16, block=16
>> >
>> > an "eject" command seems to fix the state of the PATA DVD writer
>> > or driver. The problem occurs for burning a CD and for DVD too with
>> > identical error messages.
Right after burning, if you run 'fuser -v /dev/sr0', what does it say?
--
tejun
next prev parent reply other threads:[~2007-05-04 8:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 13:59 Frank van Maarseveen
2007-05-01 14:17 ` Mark Lord
2007-05-01 14:31 ` Michal Piotrowski
2007-05-04 8:16 ` Tejun Heo [this message]
2007-05-04 8:37 ` Frank van Maarseveen
2007-05-04 8:41 ` Tejun Heo
2007-05-04 8:44 ` Frank van Maarseveen
2007-05-01 14:58 ` Gene Heskett
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=463AEBE0.7010506@gmail.com \
--to=htejun@gmail.com \
--cc=alan@redhat.com \
--cc=frankvm@frankvm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=michal.k.k.piotrowski@gmail.com \
--subject='Re: libata /dev/scd0 problem: mount after burn fails without eject' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).