From: Will Trives <will@trivescon.com.au>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
yannick.dirou@axetic.com, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH #upstream-fixes] libata: update atapi_eh_request_sense() such that lbam/lbah contains buffer size
Date: Wed, 12 Dec 2007 19:50:25 +1100 [thread overview]
Message-ID: <1197449425.3467.16.camel@Athas> (raw)
In-Reply-To: <475F9E20.4000800@gmail.com>
I'm no expert but it might have something to do with the disc supporting
that incremental stuff, so you don't need to blank the disc the
traditional way.
On Wed, 2007-12-12 at 17:38 +0900, Tejun Heo wrote:
> Hello,
>
> Will Trives wrote:
> >> This drive or media does not support the 'BLANK media' command
> >>> wodim: Cannot blank disk, aborting.
> >>> wodim: Some drives do not support all blank types.
> >>> wodim: Try again with wodim blank=all.
> >> wodim suggests "blank=all", does it work?
> >>
> > Nope same thing happens.
> >
> > "dvd+rw-format /dev/sr0 -force" Works ok though.
>
> This looks like a wodim or drive/media problem and for some reason wodim
> thinks that the media can't be blanked. Hmmm.. why do you need -force
> to dvd+rw-format? What happens if you don't use -force?
>
next prev parent reply other threads:[~2007-12-12 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 3:12 [PATCH #upstream-fixes] libata: update atapi_eh_request_sense() such that lbam/lbah contains buffer size Tejun Heo
2007-12-12 3:21 ` [PATCH #upstream-fixes] libata: fix ATAPI draining Tejun Heo
2007-12-18 1:43 ` Jeff Garzik
2007-12-12 8:05 ` [PATCH #upstream-fixes] libata: update atapi_eh_request_sense() such that lbam/lbah contains buffer size Will Trives
2007-12-12 8:16 ` Tejun Heo
2007-12-12 8:16 ` Will Trives
2007-12-12 8:38 ` Tejun Heo
2007-12-12 8:50 ` Will Trives [this message]
2007-12-12 8:48 ` Yannick Dirou
2007-12-18 1:37 ` Jeff Garzik
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=1197449425.3467.16.camel@Athas \
--to=will@trivescon.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=yannick.dirou@axetic.com \
/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;
as well as URLs for NNTP newsgroup(s).