From: Jens Axboe <axboe@suse.de>
To: Kasper Sandberg <lkml@metanurb.dk>
Cc: Alessandro Suardi <alessandro.suardi@gmail.com>,
Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>,
LKML Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: DVD burning still have problems
Date: Mon, 24 Jan 2005 18:32:08 +0100 [thread overview]
Message-ID: <20050124173207.GO2707@suse.de> (raw)
In-Reply-To: <1106587488.13336.6.camel@localhost>
On Mon, Jan 24 2005, Kasper Sandberg wrote:
> On Mon, 2005-01-24 at 16:07 +0100, Jens Axboe wrote:
> > On Sun, Jan 23 2005, Alessandro Suardi wrote:
> > > On Sun, 23 Jan 2005 21:26:55 +0100, Volker Armin Hemmann
> > > <volker.armin.hemmann@tu-clausthal.de> wrote:
> > > > Hi,
> > > >
> > > > have you checked, that cdrecord is not suid root, and growisofs/dvd+rw-tools
> > > > is?
> > > >
> > > > I had some probs, solved with a simple chmod +s growisofs :)
> > >
> > > Lucky you. Burning as root here, cdrecord not suid. Tried also
> > > burning with a +s growisofs, but...
> > >
> > > 794034176/4572807168 (17.4%) @2.4x, remaining 18:47
> > > 805339136/4572807168 (17.6%) @2.4x, remaining 18:42
> > > :-[ WRITE@LBA=60eb0h failed with SK=3h/ASC=0Ch/ACQ=00h]: Input/output error
> > > builtin_dd: 396976*2KB out @ average 2.4x1385KBps
> > > :-( write failed: Input/output error
> >
> > As with the original report, the drive is sending back a write error to
> > the issuer. Looks like bad media.
> when i do the following:
> 1: get a brand new 25pack box.
> 2: burn with my 2.6.11-rc1-bk9, and it fails
> 3: boot 2.6.9-rc1 and -rc4, and it works perfectly
> i find it extremely unlikely that the dvd's (of the same pack) i try on
> a newer kernel than 2.6.9-rcX just happens to be the faulty ones..
> especially since other persons report aswell..
Perhaps some command earlier is being rejected which causes this later
hardware reported error due to some setting being different? It could be
something like that, one thing is for sure - the error generated as
displayed _is_ a media error and it _is_ being generated by the
hardware.
Someone suggested logging possibly rejected commands, I think that would
be a good idea to try.
--
Jens Axboe
next prev parent reply other threads:[~2005-01-24 17:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 20:26 DVD burning still have problems Volker Armin Hemmann
2005-01-23 20:59 ` Alessandro Suardi
2005-01-24 1:46 ` Tim Fairchild
2005-01-24 17:26 ` Kasper Sandberg
2005-01-24 17:34 ` Jens Axboe
2005-01-24 15:07 ` Jens Axboe
2005-01-24 16:48 ` Alessandro Suardi
2005-01-24 17:21 ` Jens Axboe
2005-01-24 17:24 ` Kasper Sandberg
2005-01-24 17:32 ` Jens Axboe [this message]
2005-01-24 19:37 ` Alan Cox
2005-01-24 20:45 ` Jens Axboe
2005-01-24 20:56 ` Alessandro Suardi
2005-01-24 21:44 ` Alan Cox
2005-01-24 23:01 ` Kasper Sandberg
2005-01-24 23:48 ` Alan Cox
2005-01-28 13:42 ` Kasper Sandberg
2005-01-28 13:47 ` Jens Axboe
2005-01-28 14:05 ` Kasper Sandberg
2005-01-28 14:45 ` Kasper Sandberg
2005-01-24 23:02 ` Alessandro Suardi
2005-01-24 23:44 ` Alessandro Suardi
-- strict thread matches above, loose matches on Subject: below --
2005-01-23 16:06 Kasper Sandberg
2005-01-23 16:28 ` Alessandro Suardi
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=20050124173207.GO2707@suse.de \
--to=axboe@suse.de \
--cc=alessandro.suardi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metanurb.dk \
--cc=volker.armin.hemmann@tu-clausthal.de \
/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