Re: 2.6.0, cdrom still showing directories after being erased

[Jens Axboe <axboe@suse.de>]

On Thu, Feb 05 2004, Pavel Machek wrote:
> Hi!
> 
> > > > > I believe he meant to write he umounted it.
> > > > > The problem is that there is still some data left in CDRW's cache and it 
> > > > > needs to be emptied. That happens when CDRW is ejected and reinserted 
> > > > > (that is why windows burning software ie. Nero wants to eject the CDR/RW 
> > > > > when it gets written or erased).
> > > > > Maybe kernel could flush the buffers/caches or whatever is there when 
> > > > > CDROM gets mounted. But im afraid about compatibility with broken drives 
> > > > > such as LG.
> > > > 
> > > > There's no command to invalidate read cache, you are probably thinking
> > > > of the SYNC_CACHE command to flush dirty data to media (which is what LG
> > > > fucked up).
> > > > 
> > > > IMO, it's a user problem.
> > > 
> > > Does not look like so.
> > > 
> > > mount
> > > umount
> > > cdrecord -blank
> > > mount
> > > see old data
> > > 
> > > That looks pretty bad. If there's no other solution, we might just
> > > document it, but...
> > 
> > Nonsense. Even if the above was what the user did (I believe he didn't
> > umount the device before blanking it), then it'd be a hardware "bug".
> > It's common to require an eject to completely clear the cache.
> 
> Later in the thread user said he did indeed do umount, and it is
> reproducible for him.
> 
> Okay, we may be dealing with the buggy hardware at this point. Would
> it make sense to tell the drive to flush it caches? If there's no
> other possibility, we might want cdrecord to reset drive at the end of
> blank and/or to make it eject...

Just have cdrecord eject the disc, it's pretty common. Resetting the
drive is a bit drastic, imho.

-- 
Jens Axboe