From: Andreas Heinlein <aheinlein@gmx.com>
To: dm-devel@redhat.com
Subject: Re: Possible severe bug in the device mapper?
Date: Tue, 01 Feb 2011 14:29:51 +0100 [thread overview]
Message-ID: <4D480ACF.8060305@gmx.com> (raw)
In-Reply-To: <4D47DAEB.6010506@redhat.com>
> 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
I mean filesystem. But the strange thing about my observation is that
obviously no inconsistency is ever detected, except for openSuSE. The
filesystem on the loopback device under Ubuntu and Fedora, backed by the
no-longer-existing usb drive, can be happily read from and written to
and even be fsck'ed without any problems. Only after completely
unmounting it, deleting the loopback device, then re-inserting the drive
and loop-mounting again you can see that data was lost. 'remount-ro' is
set in all cases.
Andreas
prev parent reply other threads:[~2011-02-01 13:29 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
2011-02-01 13:29 ` Andreas Heinlein [this message]
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=4D480ACF.8060305@gmx.com \
--to=aheinlein@gmx.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