public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Fox!MURDER" <fox@murder.cz>
To: "Martin Povolný" <xpovolny@aurora.fi.muni.cz>
Cc: Derek Foreman <manmower@signalmarketing.com>,
	John Bradford <john@grabjohn.com>, M?ns Rullg?rd <mru@kth.se>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.0, cdrom still showing directories after being erased
Date: Tue, 03 Feb 2004 20:56:47 +0100	[thread overview]
Message-ID: <401FFCFF.6020309@murder.cz> (raw)
In-Reply-To: <20040203195116.GA2961@aurora.fi.muni.cz>

Can you mount it even after issuing cdrecord -toc?

Tomas Zvala


Martin Povolný wrote:

>Dne: Tue, Feb 03, 2004 at 01:09:45PM -0600, Derek Foreman napsal:
>  
>
>>Just making cdrecord -eject at the end of the process will probably
>>workaround what is almost certainly a hardware bug.  or just eject the
>>disc by hand before attempting to re-use it.
>>    
>>
>
>yes, -eject helps, as well as ejecting manually or ejecting using 'eject'
>
>  
>
>>I had an old writer that did much the same thing.  After burning a disc,
>>it would still see it as blank until you ejected and reloaded.
>>
>>to Martin:
>>Does cdrecord -toc still show a valid toc after you blank the disc?
>>(definately buggy hardware)
>>    
>>
>
>no, it does not:
>
>$ cdrecord -dev=/dev/cdrom -toc
>Cdrecord-Clone 2.01a19 (i686-pc-linux-gnu) Copyright (C) 1995-2003 Jörg Schilling
>scsidev: '/dev/cdrom'
>devname: '/dev/cdrom'
>scsibus: -2 target: -2 lun: -2
>Warning: Open by 'devname' is unintentional and not supported.
>Linux sg driver version: 3.5.27
>Using libscg version 'schily-0.7'
>Device type    : Removable CD-ROM
>Version        : 0
>Response Format: 1
>Vendor_info    : 'HL-DT-ST'
>Identifikation : 'RW/DVD GCC-4480B'
>Revision       : '1.00'
>Device seems to be: Generic mmc2 DVD-ROM.
>Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
>Driver flags   : MMC-2 SWABAUDIO BURNFREE
>Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R
>cdrecord.mmap: Success. read toc: scsi sendcmd: no error
>CDB:  43 00 00 00 00 00 00 00 04 00
>status: 0x2 (CHECK CONDITION)
>Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 24 00 00 00
>Sense Key: 0x5 Illegal Request, Segment 0
>Sense Code: 0x24 Qual 0x00 (invalid field in cdb) Fru 0x0
>Sense flags: Blk 0 (not valid)
>resid: 4
>cmd finished after 0.000s timeout 40s
>cdrecord.mmap: Cannot read TOC header
>cdrecord.mmap: Cannot read TOC/PMA
>pie:martin:~
>
>but I can still mount it, and see the erased data:
>
>pie:martin:~
>$ mount /cdrom/
>pie:martin:~
>$ ls /cdrom/
>Beskydy2003-2004
>  
>  
>
>>And does ejecting and reloading the disc make things work as expected?
>>    
>>
>
>it does
>
>  
>

  reply	other threads:[~2004-02-03 19:56 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03 13:18 2.6.0, cdrom still showing directories after being erased Martin Povolný
2004-02-03 13:31 ` Måns Rullgård
2004-02-03 13:45 ` Richard B. Johnson
2004-02-03 15:00   ` Tomas Zvala
2004-02-03 15:24     ` Richard B. Johnson
2004-02-03 15:45       ` Tomas Zvala
2004-02-03 16:02       ` John Bradford
2004-02-03 16:17         ` Måns Rullgård
2004-02-03 16:35           ` John Bradford
2004-02-03 17:46             ` Martin Povolný
2004-02-03 18:02               ` Martin Povolný
2004-02-03 18:53               ` John Bradford
2004-02-03 19:03                 ` Måns Rullgård
2004-02-03 20:35                   ` Richard B. Johnson
2004-02-03 20:59                     ` John Bradford
2004-02-03 22:40                     ` Jens Axboe
2004-02-03 23:05                       ` Martin Schlemmer
2004-02-04  7:37                         ` John Bradford
2004-02-05 23:31                           ` Eduard Bloch
2004-02-06  7:58                             ` John Bradford
2004-02-08 10:15                               ` Eduard Bloch
2004-02-08 10:32                                 ` Jens Axboe
2004-02-08 11:06                                 ` John Bradford
2004-02-03 22:03                   ` Måns Rullgård
2004-02-03 19:31               ` Tomas Zvala
2004-02-03 19:09             ` Derek Foreman
2004-02-03 19:51               ` Martin Povolný
2004-02-03 19:56                 ` Fox!MURDER [this message]
     [not found]                   ` <Pine.LNX.4.58.0402031358450.770@uberdeity>
2004-02-03 21:07                     ` Tomas Zvala
2004-02-03 15:28     ` Jens Axboe
2004-02-05 18:23       ` Pavel Machek
2004-02-05 20:04         ` John Bradford
2004-02-05 21:06           ` Pavel Machek
2004-02-05 21:36             ` John Bradford
2004-02-05 20:41         ` Jens Axboe
2004-02-05 21:09           ` Pavel Machek
2004-02-05 21:12             ` Jens Axboe
2004-02-05 21:17               ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-02-05 20:33 Thomas Glanzmann
2004-02-05 20:54 ` Jens Axboe
2004-02-05 21:16   ` Thomas Glanzmann
2004-02-05 21:29     ` Jens Axboe
2004-02-05 21:41     ` John Bradford
2004-02-13 23:19   ` Pavel Machek
2004-02-05 21:24 Thomas Glanzmann
2004-02-05 21:31 ` Jens Axboe

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=401FFCFF.6020309@murder.cz \
    --to=fox@murder.cz \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manmower@signalmarketing.com \
    --cc=mru@kth.se \
    --cc=xpovolny@aurora.fi.muni.cz \
    /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