Re: 2.6.0, cdrom still showing directories after being erased

[John Bradford]

Quote from Pavel Machek <pavel@xxxxxxx>:
> Hi!
> 
> > > mount
> > > umount
> > > cdrecord -blank
> > > mount
> > > see old data
> > > 
> > > That looks pretty bad. If there's no other solution, we might just
> > > document it, but...
> > 
> > I think cdrecord should be hacked to complain loudly if the device is
> > already mounted.  Regardless of the device cache not being cleared,
> > (which is a firmware bug, in my opinion), blanking a mounted device is
> > usually not what the user intended.  This is not a kernel problem as
> > such, and should be dealt with in userspace.
> 
> But it is _not_ mounted at that point. User did no mistake.

OK, then this proves that this thread has been going on _way_ too
long, because not only have we discussed both scenarios during the
course of it, but I have managed to confuse both of them in the same
post :-).

In the scenario you describe, where the disc is unmounted, there is
nothing for cdrecord to complain about.  All that could really be done
is to hack cdrecord to reset the device afterwards for broken devices,
which would presumably flush the device's own cache.  However, even
this may not be sufficient, as from reading another post in this
thread, it seems that we need to force the drive to report that the
media has changed before the kernel will flush _it's_ buffers.

Obviously, that could be worked around in the kernel, but I would
expect the device to report media changed if it's been erased,
(although whether that is part of the spec or not, I have no idea).

John.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/