From: Bill Davidsen <davidsen@tmr.com>
To: Joerg Schilling <Joerg.Schilling@fokus.fraunhofer.de>
Cc: adi@hexapodia.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6.30-rc2] CD-R: wodim intermittent failures: [sr0] Add. Sense: Logical block address out of range, sector 0
Date: Mon, 27 Apr 2009 15:07:12 -0400 [thread overview]
Message-ID: <49F60260.9080602@tmr.com> (raw)
In-Reply-To: <49f07fa8.UFHStOXJD5eYq3ER%Joerg.Schilling@fokus.fraunhofer.de>
Joerg Schilling wrote:
> I see two possible problems that should be first resolved.
>
> 1) You are using "wodim" instead of cdrecord.
> "wodim" is a very old version (4+ years) of cdrecord with
> additional bugs. Due to Copyright & GPL violations, it cannot
> even be legally distributed.
>
> 2) You may be using the linux hald version
>
> I recommend to first get a recent original cdrtools package from
>
> ftp://ftp.berlios.de/pub/cdrecord/alpha/
>
> and to try with this after running "make install" as root.
> As Linux requires root privileges for many SCSI commands, you need to
> install cdreord suid root which is automatically done via "make install"
> as root.
>
> If your problem persists, try to kill hald. Hald on Linux has many problems:
>
> - It looks for the wrong state transitions on the CD drive
> and thus distrurbes CD/DVD/BD writing. It may e.g. try to mount a CD
> that has not yet been fully written.
>
Appears to be true, but that's not a kernel problem, it's a hald problem, the
fix belongs there.
> - The O_EXCL metod it believes on just cannot ever work correctly:
>
> - You would not be able to read out written media CD-DA or CD-ROM
>
> - You would not be able to deal with multi-session media
>
I don't quite see how these two follow from using O-EXCL, assuming the device is
released after writing, but see next:
> - As Linux offers to access CD/DVD/BD-drives vie more than one
> device driver and as these device drivers don't know each other
> O_EXCL cannot work anyway.
>
And that is a kernel problem, allowing multiple access paths which don't share
exclusion is a dubious design decision. O_EXCL really should work.
> If your problem still persists, you may have a Linux kernel problem.
>
The usual solution is to tell hald and your window manager of choice not to
mount things automatically, or at least not while they are opened. But that's a
fudge, not a fix, O_EXCL should positively prevent this problem.
> BTW: please keep me on CC:
>
> Jörg
>
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2009-04-27 19:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 14:48 [2.6.30-rc2] CD-R: wodim intermittent failures: [sr0] Add. Sense: Logical block address out of range, sector 0 Joerg Schilling
2009-04-27 19:07 ` Bill Davidsen [this message]
2009-05-13 1:52 ` Kyle Moffett
2009-05-13 11:50 ` Joerg Schilling
-- strict thread matches above, loose matches on Subject: below --
2009-04-21 1:52 Andy Isaacson
2009-04-22 21:49 ` Andrew Morton
2009-04-23 6:46 ` Robert Hancock
2009-04-23 7:07 ` Andy Isaacson
2009-05-12 21:52 ` Andy Isaacson
2009-05-12 23:23 ` Robert Hancock
2009-05-13 1:00 ` Andy Isaacson
2009-05-13 1:08 ` Robert Hancock
2009-05-13 2:27 ` Andy Isaacson
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=49F60260.9080602@tmr.com \
--to=davidsen@tmr.com \
--cc=Joerg.Schilling@fokus.fraunhofer.de \
--cc=adi@hexapodia.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