public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH e2fsprogs] UPDATED: ignore "safe" flag differences when fsck compares superblocks
Date: Sat, 26 Jan 2008 22:51:10 -0600	[thread overview]
Message-ID: <479C0DBE.4000606@redhat.com> (raw)
In-Reply-To: <20080127042216.GB24842@mit.edu>

Theodore Tso wrote:
> This is what I've checked in.  See the comment about why we can't
> ignore a difference for the extended attribute feature.

Ok.  Unfortunately, that one really hurts on fedora, or any distro which
writes xattrs during install.

The installer mkfs's, mounts, installs with selinux, reboots => force
recheck of the entire filesystem, because the kernel wrote extended
attributes for selinux, but only to the primary superblock.

Solely having this set in primary but not in the backups should hardly
be a trigger for a full filesystem check, should it?

-Eric

>           	     	  	       	       - Ted
> 
> commit a8cde73acbf6e0f9c0a3601e4f5fac2b01a27bd2
> Author: Theodore Ts'o <tytso@mit.edu>
> Date:   Sat Jan 26 23:17:50 2008 -0500
> 
>     Ignore "safe" flag differences when e2fsck compares superblocks

  reply	other threads:[~2008-01-27  4:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 17:37 [PATCH e2fsprogs] ignore "safe" flag differences when fsck compares superblocks Eric Sandeen
2008-01-25 18:29 ` [PATCH e2fsprogs] UPDATED: " Eric Sandeen
2008-01-27  4:22   ` Theodore Tso
2008-01-27  4:51     ` Eric Sandeen [this message]
2008-01-27  5:25       ` Theodore Tso

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=479C0DBE.4000606@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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