mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Chris Clayton <chris@theclaytons.giointernet.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CDMRW in 2.6
Date: Fri, 13 Aug 2004 13:54:26 +0200	[thread overview]
Message-ID: <20040813115426.GN2663@suse.de> (raw)
In-Reply-To: <200408131253.49321.chris@theclaytons.giointernet.co.uk>

On Fri, Aug 13 2004, Chris Clayton wrote:
> On Friday 13 Aug 2004 07:15, Jens Axboe wrote:
> > On Mon, Aug 09 2004, Chris Clayton wrote:
> > > cdrom: hdc: mrw address space DMA selected
> > > cdrom open: mrw_status 'mrw complete'
> > > hdc: command error: status=0x51 { DriveReady SeekComplete Error }
> > > hdc: command error: error=0x54
> > > end_request: I/O error, dev hdc, sector 1048576
> >
> > Command was aborted, probably the media isn't writable after all.  Can
> > you try and force a full format with cdrwtool?
> 
> Jens,
> 
> Did you mean cdrwtool or cdmrw?

Sorry, meant cdmrw of course.

> I've done a format with cdrwtool (cdrwtool -t 10 -d /dev/hdc -q) but
> when I try and mount it (mount -o rw,noatime -t udf /dev/hdc /cdmrw)
> and mount gives the message:
> 
> mount: block device /dev/hdc is write-protected, mounting read-only
> 
> dmesg shows no error after cdrwtool has run but has the following new
> messages after the media is mounted:
> 
> cdrom: hdc: mrw address space DMA selected
> cdrom open: mrw_status 'not mrw'
> UDF-fs INFO UDF 0.9.8.1 (2004/29/09) Mounting volume 'LinuxUDF', timestamp 
> 2004/08/13 12:35 (1000)
> 
> The media does, however, mount OK for packet writing (sudo mount -t
> udf -o rw,noatime /dev/pktcdvd/cdrw /cdrw) using another kernel
> patched with the packet writing patches Peter Osterlund has submitted
> for the -mm series.
> 
> I'll try a full (as opposed to quick) blank with cdrwtool plus a
> forced format with cdmrw and report back when that has finished.

Yes please do that, if that doesn't work it's really screwed.

-- 
Jens Axboe


  reply	other threads:[~2004-08-13 11:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-09 16:25 Chris Clayton
2004-08-12 20:23 ` Bill Davidsen
2004-08-13 12:08   ` Chris Clayton
2004-08-13  7:15 ` Jens Axboe
2004-08-13  7:55   ` Alan Jenkins
2004-08-13  8:01     ` Jens Axboe
2004-08-13 12:47       ` Chris Clayton
2004-08-13 11:47         ` Jens Axboe
2004-12-22  1:24           ` Daniel Drake
2004-08-13 12:53   ` Chris Clayton
2004-08-13 11:54     ` Jens Axboe [this message]
2004-08-13 14:35       ` Chris Clayton
2004-08-13 13:50         ` Jens Axboe
2004-08-13 16:15           ` Chris Clayton

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=20040813115426.GN2663@suse.de \
    --to=axboe@suse.de \
    --cc=chris@theclaytons.giointernet.co.uk \
    --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

Powered by JetHome