From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "Marcin Mirosław" <marcin@mejor.pl>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfsprogs: write both features2 fields when xfs_admin changes lazy_count
Date: Thu, 29 Apr 2010 12:28:25 +1000 [thread overview]
Message-ID: <20100429022825.GD2512@dastard> (raw)
In-Reply-To: <4BD8E9F8.4090701@sandeen.net>
On Wed, Apr 28, 2010 at 09:07:52PM -0500, Eric Sandeen wrote:
> xfs_admin -c invokes repair directly to change lazy_count,
> but it doesn't write both features2 fields, so this:
>
> # mkfs.xfs -dfile,name=fsfile,size=10g -llazy-count=0
> # xfs_admin -c 1 fsfile
> # xfs_repair fsfile
>
> yields errors.
>
> Reported-by: Marcin Mirosław <marcin@mejor.pl>
> Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Reviewed-by: Dave Chinner <david@fromorbit.com>
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-04-29 2:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 2:07 [PATCH] xfsprogs: write both features2 fields when xfs_admin changes lazy_count Eric Sandeen
2010-04-29 2:28 ` Dave Chinner [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=20100429022825.GD2512@dastard \
--to=david@fromorbit.com \
--cc=marcin@mejor.pl \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.