mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Tomas Zvala <tomas@zvala.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0, cdrom still showing directories after being erased
Date: Tue, 3 Feb 2004 10:24:14 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0402031018170.31411@chaos> (raw)
In-Reply-To: <401FB78A.5010902@zvala.cz>

On Tue, 3 Feb 2004, Tomas Zvala 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.
>
> Tomas Zvala

That's not what he said and, I assure you that if he unmounted
it there would not be any buffers to flush. Execute `man umount`.

The problem is that the cd-burner allowed the read-only file-system
to be modified while it was mounted. That is an applications problem
because the file-system is R/O, but the device is not. The kernel
will correctly prevent writes to the R/O file-system, and will
correctly allow writes to the underlying device. It is up to
the application (cdrecord) to prevent undesired operations.

>
> Richard B. Johnson wrote:
>
> >On Tue, 3 Feb 2004, Martin [iso-8859-2] Povolný wrote:
> >
> >
> >
> >>I have debian's 2.6.0-686-smp only with PNP BIOS disabled (fails to
> >>boot with enabled, as described by other people).
> >>
> >>I did
> >>
> >>$ mount /cdrom/
> >>$ ls /cdrom/
> >>
> >>got listing of files and directories on the cdrom
> >>then
> >>
> >>$ cdrecord dev=/dev/hdc -blank=fast -v
> >>...
> >>Blanking time:   21.570s
> >>$ mount /cdrom
> >>$ ls /cdrom
> >>
> >>
> >
> >Can you really initialize the CDROM while it's mounted? Although
> >the kernel doesn't care, cdrecord should. Suggest that you
> >contact the cdrecord author.
> >
> >Cheers,
> >Dick Johnson
> >Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
> >            Note 96.31% of all statistics are fiction.
> >
> >
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at  http://www.tux.org/lkml/
> >
> >
> >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2004-02-03 15:22 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
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=Pine.LNX.4.53.0402031018170.31411@chaos \
    --to=root@chaos.analogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomas@zvala.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

all inboxes | Powered by JetHome®