From: Jan Ciger <jan.ciger@epfl.ch>
To: Oliver.Neukum@lrz.uni-muenchen.de
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: umounting
Date: Tue, 22 Jan 2002 20:46:11 +0100 [thread overview]
Message-ID: <m16T6sl-021O8uC@ligsg2.epfl.ch> (raw)
In-Reply-To: <20020122150703.B13509@pcmaftoul.esrf.fr> <m16T2IB-02103HC@ligsg2.epfl.ch> <16T6BH-1ZiPWiC@fwd07.sul.t-online.com>
In-Reply-To: <16T6BH-1ZiPWiC@fwd07.sul.t-online.com>
On Tuesday 22 January 2002 20:01, you wrote:
> > When a second user comes and unmounts a disk, then the data are flushed
> > (the old data) and he gets a fs corruption, because the data were not
> > from his disk.
>
> No. The sbp2 driver should report a disk change. If such a thing happens,
> there's a kernel bug. Pulling out a mounted disk may cause a corrupted
> filesystem on that disk but not on others.
Maybe there is a problem in the driver, that it does not report the media
change, but anyway, you WILL get a corrupted filesystem, when you unmount
such disk with another media in drive - it is exactly like that - the driver
didn't report the change and the filesystem layer thinks, that it has still
the same media in drive and happily flushes e.g. ext2 data to a VFAT disk ...
Then you get the corruption of the second disk.
But I am not familiar with the sbp2 driver, but this is a quite standard
behavior for removable media.
Jan
next prev parent reply other threads:[~2002-01-22 19:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 14:07 umounting Samuel Maftoul
2002-01-22 14:52 ` umounting Jan Ciger
2002-01-22 19:01 ` umounting Oliver Neukum
2002-01-22 19:46 ` Jan Ciger [this message]
2002-01-23 8:06 ` umounting Samuel Maftoul
2002-01-23 21:42 ` umounting Oliver Neukum
2002-01-23 23:52 ` umounting Samuel Maftoul
2002-01-24 9:22 ` umounting Xavier Bestel
2002-01-22 22:10 ` umounting Horst von Brand
2002-01-23 10:33 ` umounting Jan Ciger
2002-01-23 10:40 ` umounting Horst von Brand
2002-01-23 11:01 ` umounting Jan Ciger
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=m16T6sl-021O8uC@ligsg2.epfl.ch \
--to=jan.ciger@epfl.ch \
--cc=Oliver.Neukum@lrz.uni-muenchen.de \
--cc=linux-kernel@vger.kernel.org \
/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