From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] e2fsck: ignore differing NEEDS_RECOVERY flag on backup sbs
Date: Thu, 26 Mar 2009 11:31:41 -0500 [thread overview]
Message-ID: <49CBADED.7040909@redhat.com> (raw)
In-Reply-To: <49281F18.7080404@redhat.com>
Eric Sandeen wrote:
> This is for RH bugzilla 471925 - Complete scan of filesystems expanded online
>
> When we resize online, the primary superblock gets copied to all
> the backups, and of course since we're mounted the NEEDS_RECOVERY
> flag is set. A subsequent fsck will find the backups have the
> NEEDS_RECOVERY flag set while the primary does not, and this
> forces a full fsck pass.
>
> I think this flag can be safely ignored in the flag comparisons.
ping on this? Andreas wondered about masking the flag when sb backups
are written, but I think that only needs to be done in kernelspace; from
reading code & testing offline resize, I don't think userspace needs
further changes.
-Eric
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> ---
>
> Index: e2fsprogs/e2fsck/super.c
> ===================================================================
> --- e2fsprogs.orig/e2fsck/super.c 2008-11-22 07:54:47.000000000 -0600
> +++ e2fsprogs/e2fsck/super.c 2008-11-22 08:59:45.953060973 -0600
> @@ -860,7 +860,8 @@ void check_super_block(e2fsck_t ctx)
> * try to discourage it in the future. In particular, for the newer
> * ext4 files, especially EXT4_FEATURE_RO_COMPAT_DIR_NLINK and
> * EXT3_FEATURE_INCOMPAT_EXTENTS. So some of these may go away in the
> - * future.
> + * future. EXT3_FEATURE_INCOMPAT_RECOVER may also get set when
> + * copying the primary superblock during online resize.
> *
> * The kernel will set EXT2_FEATURE_COMPAT_EXT_ATTR, but
> * unfortunately, we shouldn't ignore it since if it's not set in the
> @@ -869,7 +870,8 @@ void check_super_block(e2fsck_t ctx)
> */
> #define FEATURE_RO_COMPAT_IGNORE (EXT2_FEATURE_RO_COMPAT_LARGE_FILE| \
> EXT4_FEATURE_RO_COMPAT_DIR_NLINK)
> -#define FEATURE_INCOMPAT_IGNORE (EXT3_FEATURE_INCOMPAT_EXTENTS)
> +#define FEATURE_INCOMPAT_IGNORE (EXT3_FEATURE_INCOMPAT_EXTENTS| \
> + EXT3_FEATURE_INCOMPAT_RECOVER)
>
> int check_backup_super_block(e2fsck_t ctx)
> {
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-26 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 15:02 [PATCH] e2fsck: ignore differing NEEDS_RECOVERY flag on backup sbs Eric Sandeen
2008-11-22 17:36 ` Andreas Dilger
2008-11-23 3:29 ` Eric Sandeen
2009-03-26 16:31 ` Eric Sandeen [this message]
2009-04-07 17:22 ` 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=49CBADED.7040909@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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).