From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH e2fsprogs] UPDATED: ignore "safe" flag differences when fsck compares superblocks
Date: Sun, 27 Jan 2008 00:25:35 -0500 [thread overview]
Message-ID: <20080127052535.GD24842@mit.edu> (raw)
In-Reply-To: <479C0DBE.4000606@redhat.com>
On Sat, Jan 26, 2008 at 10:51:10PM -0600, Eric Sandeen wrote:
> 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 right fix is to simply force the extended attribute features on in
mke2fs. We can do this in mke2fs.conf. I plan to change it so that
by default it's enabled for ext3 filesystems.
- Ted
prev parent reply other threads:[~2008-01-27 5:25 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
2008-01-27 5:25 ` Theodore Tso [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=20080127052535.GD24842@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@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