From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266188AbUBCXFW (ORCPT ); Tue, 3 Feb 2004 18:05:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266192AbUBCXFW (ORCPT ); Tue, 3 Feb 2004 18:05:22 -0500 Received: from wblv-254-118.telkomadsl.co.za ([165.165.254.118]:31624 "EHLO gateway.lan") by vger.kernel.org with ESMTP id S266188AbUBCXFG (ORCPT ); Tue, 3 Feb 2004 18:05:06 -0500 Subject: Re: 2.6.0, cdrom still showing directories after being erased From: Martin Schlemmer Reply-To: Martin Schlemmer To: Jens Axboe Cc: "Richard B. Johnson" , =?ISO-8859-1?Q?M=E5ns_Rullg=E5rd?= , John Bradford , Martin =?ISO-8859-1?Q?Povoln=FD?= , Linux Kernel Mailing Lists , alan@redhat.com In-Reply-To: <20040203224021.GK11683@suse.de> References: <401FB78A.5010902@zvala.cz> <200402031602.i13G2NFi002400@81-2-122-30.bradfords.org.uk> <200402031635.i13GZJ9Q002866@81-2-122-30.bradfords.org.uk> <20040203174606.GG3967@aurora.fi.muni.cz> <200402031853.i13Ir1e0003202@81-2-122-30.bradfords.org.uk> <20040203224021.GK11683@suse.de> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-jU1p/KAdUL1ChKMTod+5" Message-Id: <1075849526.11322.9.camel@nosferatu.lan> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Wed, 04 Feb 2004 01:05:27 +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org --=-jU1p/KAdUL1ChKMTod+5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, 2004-02-04 at 00:40, Jens Axboe wrote: > On Tue, Feb 03 2004, Richard B. Johnson wrote: > > On Tue, 3 Feb 2004, [iso-8859-1] M=C3=A5ns Rullg=C3=A5rd wrote: > >=20 > > > John Bradford writes: > > > > > > > Regardless of specs, I don't know what the majority of devices in t= he > > > > real world actually do. Maybe Jens and Alan, (cc'ed), can help. > > > > > > Just tested with an ASUS SCB-2408 in my laptop. It gives read errors > > > after doing a fast erase, just like it should. > > > > > > -- > > > M=C3=A5ns Rullg=C3=A5rd > > > mru@kth.se > > > - > >=20 > > I had to borrow a R/W CDROM because most everybody uses CR-R only > > here. That's why it took so long to check. With SCSI, Linux 2.4.24, > > cdrecord fails to umount the drive before it burns it. The result > > is that the previous directory still remains at the mount-point. > > This, even though cdrecord ejected the drive to "re-read" its > > status. > >=20 > > Bottom line: If the CDROM isn't umounted first, you can still > > get a directory entry even though the CDROM has been written with > > about 500 magabytes of new data. >=20 > So what? Just because you can do it, doesn't mean it's a valid thing to > do. You can literally come up with thousands of similar weird things, if > you wanted to. >=20 > This whole discussion is silly and pointless. I am assuming its cdrecord's responsibility to check if the device is not in use? How difficult will it be to add a kernel side stopper to this (as it will after all also stop this thread) ? --=20 Martin Schlemmer --=-jU1p/KAdUL1ChKMTod+5 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBAICk2qburzKaJYLYRAutNAJ9If1Ow2lK4SlH7Wq+4BLc1oDa0zgCdG5gt IdmlxHDQGCD+3eRuNkBvxng= =PxGQ -----END PGP SIGNATURE----- --=-jU1p/KAdUL1ChKMTod+5--