linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Add a norecovery option to ext3/4?
Date: Mon, 9 Apr 2007 05:31:34 +0200	[thread overview]
Message-ID: <20070409033134.GB13980@implementation> (raw)
In-Reply-To: <4619B202.3050601@redhat.com>

Eric Sandeen, le Sun 08 Apr 2007 22:24:50 -0500, a écrit :
> Samuel Thibault wrote:
> >Distribution installers usually try to probe OSes for building a suited
> >grub menu.  Unfortunately, mounting an ext3 partition, even in read-only
> >mode, does perform some operations on the filesystem (log recovery).
> >This is not a good idea since it may silently garbage data.  
> 
> Can you elaborate?  Under what circumstances is log replay going to harm 
> data?  Do you mean that the installer mounts partitions, looking for 
> what OS is installed?  How is that harmful?
> 
> Ohhh... this is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417407 
> isn't it?

Yes.

> Hm, so the root cause there seems that the installer found 2 legs of a 
> mirror and mounted them independently, recovering them independently... 
> But why did that cause problems?

Because that thrashed his data (or at least it didn't help to keep data
safe).

> Other options you may have in the installer, though, is to check for
> md superblocks before mounting bare partitions, or maybe use the
> BLKROSET ioctl to set the block device to read-only prior to mount,
> for added insurance...

That's one the things proposed in the bugreport yes.

Samuel

  reply	other threads:[~2007-04-09  3:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09  0:05 Add a norecovery option to ext3/4? Samuel Thibault
2007-04-09  3:24 ` Eric Sandeen
2007-04-09  3:31   ` Samuel Thibault [this message]
2007-04-09  3:42     ` Eric Sandeen
2007-04-09 14:00       ` Theodore Tso
2007-04-09  4:29   ` Brad Campbell
2007-04-09 10:14   ` Andreas Dilger
2007-04-09 13:42   ` Valdis.Kletnieks
2007-04-09 16:37   ` Jan Engelhardt
2007-04-11 20:06   ` Pavel Machek
2007-04-09 15:43 ` Phillip Susi
2007-04-09 16:20   ` Kyle Moffett
2007-04-09 17:21   ` Eric Sandeen
2007-04-10  7:22     ` Jörn Engel
2007-04-10 11:27       ` Theodore Tso
2007-04-10 12:08         ` Jörn Engel
2007-04-10 16:44           ` Matt Mackall
2007-04-10 18:54     ` Phillip Susi
2007-04-10 19:18       ` Eric Sandeen
2007-04-10 22:04         ` Phillip Susi
2007-04-11 20:09         ` Bill Davidsen
2007-04-12 13:54           ` Benny Amorsen
2007-04-15 18:49           ` 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=20070409033134.GB13980@implementation \
    --to=samuel.thibault@ens-lyon.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@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;
as well as URLs for NNTP newsgroup(s).