From: Jens Axboe <axboe@suse.de>
To: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0, cdrom still showing directories after being erased
Date: Thu, 5 Feb 2004 22:31:58 +0100 [thread overview]
Message-ID: <20040205213158.GI11683@suse.de> (raw)
In-Reply-To: <20040205212417.GI10547@stud.uni-erlangen.de>
On Thu, Feb 05 2004, Thomas Glanzmann wrote:
> Hi,
>
> > 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...
>
> It's not the drive, it's the kernel. We have to tell the kernel to
> *flush* *it's* buffers when doing an umount. See my other posting.
Partly, I still think the drive should report media changed after
knowingly doing a TOC blank (or change). But see my other post, should
work.
--
Jens Axboe
next prev parent reply other threads:[~2004-02-05 21:34 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 21:24 2.6.0, cdrom still showing directories after being erased Thomas Glanzmann
2004-02-05 21:31 ` Jens Axboe [this message]
-- 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-03 13:18 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
[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
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=20040205213158.GI11683@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sithglan@stud.uni-erlangen.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.