From: Michael Buesch <mb@bu3sch.de>
To: Jan Kara <jack@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>
Subject: Re: Oops when using growisofs
Date: Wed, 25 Jun 2008 11:46:29 +0200 [thread overview]
Message-ID: <200806251146.30142.mb@bu3sch.de> (raw)
In-Reply-To: <20080625093700.GB15865@duck.suse.cz>
On Wednesday 25 June 2008 11:37:00 Jan Kara wrote:
> > Yeah the IO error is the trigger.
> > I noticed that it had obvious troubles accessing the DVD that was in the drive.
> > It sweeped over it for several seconds, then hung the system for 2 or 3 seconds
> > and then oopsed. But after that everything continued to work as usual.
> > (Except kded of course)
> Hmm, by "accessing" do you mean that you've mounted the burned DVD and when
> browsing it the IO error and the oops occured or that IO error happened
> when burning? It is important because in the first case i_blkbits would be
> taken from some ISOFS inode desribing some file while in the second case
> i_blkbits are from the inode of the device...
I don't know. kded, which caused the oops, is always running. It is a KDE daemon
that polls device state and so on. So yeah, it might have accessed the drive
while growisofs was writing to it.
However with "accessing" I mean the DVD drive motor was spinning up and down
and the laser lens was moving like crazy. The sound that happens, if you put
a completely scratched DVD into the drive and it is unable to make sense of it.
However, this was not scratched. It was a new DVD with one session on it that
I just burnt 5 minutes before that. So I wanted to append another session to it
and it crashed and resulted in IO errors in growisofs.
--
Greetings Michael.
next prev parent reply other threads:[~2008-06-25 9:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-22 16:18 Oops when using growisofs Michael Buesch
2008-06-22 21:22 ` Arnd Bergmann
2008-06-22 21:31 ` Arnd Bergmann
2008-06-22 22:09 ` Michael Buesch
2008-06-22 22:05 ` Michael Buesch
2008-06-22 22:28 ` Michael Buesch
2008-06-23 6:34 ` Andrew Morton
2008-06-23 6:59 ` Nick Piggin
2008-06-24 17:28 ` Jan Kara
2008-06-24 18:39 ` Michael Buesch
2008-06-25 1:42 ` Arnd Bergmann
2008-06-25 9:37 ` Jan Kara
2008-06-25 9:46 ` Michael Buesch [this message]
2008-06-26 17:05 ` Jan Kara
2008-06-26 18:11 ` Jens Axboe
2008-06-26 18:21 ` Michael Buesch
2008-06-26 18:36 ` Jens Axboe
2008-06-26 18:39 ` Michael Buesch
2008-06-26 18:41 ` Jens Axboe
2008-06-29 19:39 ` Michael Buesch
2008-07-09 18:46 ` Jan Kara
2008-07-22 9:25 ` Andrew Morton
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=200806251146.30142.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=jack@suse.cz \
--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