From: Zdenek Kabelac <zkabelac@redhat.com>
To: dm-devel@redhat.com
Subject: Re: Possible severe bug in the device mapper?
Date: Tue, 01 Feb 2011 11:05:31 +0100 [thread overview]
Message-ID: <4D47DAEB.6010506@redhat.com> (raw)
In-Reply-To: <4D47D29F.5040200@gmx.com>
Dne 1.2.2011 10:30, Andreas Heinlein napsal(a):
> Am 31.01.2011 12:20, schrieb Joe Thornber:
>> On Mon, 2011-01-31 at 10:30 +0100, Andreas Heinlein wrote:
>>> 2. Create a loopback device with this file (losetup -f
>>> /media/somedrive/testfile)
>> I'm just trying to understand your complaint here. If device-mapper
>> wasn't in the equation here, and you were using the loop-back device
>> directly (i.e. by putting a filesystem on it and mounting). Then you
>> pulled the removable device, what happens?
>>
>> - Joe
>>
>> --
>> dm-devel mailing list
>> dm-devel@redhat.com
>> https://www.redhat.com/mailman/listinfo/dm-devel
> Thank you for your advice. Actually, it still happens without
> device-mapper, so I'm at the wrong place here. Sorry for that. I did
> some more tests with different distros and releases (Ubuntu 10.10 and
> 11.04alpha1, OpenSuse 11.3, Fedora 14), and almost all showed this
> behaviour; only OpenSuse immediatley set the device to read-only on the
> first write attempt, Ubuntu 11.04alpha1 crashed, but this may be because
> of the alpha status. Still not quite what one would expect, though.
Do you mean 'device' or filesystem as read-only?
For filesystem you may easily switch error behavior so you will not destroy
your data when inconsistency is detected (tune2fs -e remount-ro)
Zdenek
next prev parent reply other threads:[~2011-02-01 10:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 9:30 Possible severe bug in the device mapper? Andreas Heinlein
2011-01-31 11:13 ` Milan Broz
2011-01-31 11:20 ` Joe Thornber
2011-02-01 9:30 ` Andreas Heinlein
2011-02-01 10:03 ` Joe Thornber
2011-02-01 10:05 ` Zdenek Kabelac [this message]
2011-02-01 13:29 ` Andreas Heinlein
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=4D47DAEB.6010506@redhat.com \
--to=zkabelac@redhat.com \
--cc=dm-devel@redhat.com \
/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