From: Dave Chinner <david@fromorbit.com>
To: "Marcin Mirosław" <marcin@mejor.pl>
Cc: xfs@oss.sgi.com
Subject: Re: Enabling lazy counters damages filesystem
Date: Thu, 29 Apr 2010 11:43:12 +1000 [thread overview]
Message-ID: <20100429014312.GA2512@dastard> (raw)
In-Reply-To: <20100428230447.GJ9783@dastard>
On Thu, Apr 29, 2010 at 09:04:47AM +1000, Dave Chinner wrote:
> On Wed, Apr 28, 2010 at 04:34:25PM +0200, Marcin Mirosław wrote:
> > Hello,
> > Please look at this:
> > # mkfs.xfs -f /dev/malowazne/test
> > meta-data=/dev/malowazne/test isize=256 agcount=4, agsize=524288 blks
> > = sectsz=512 attr=2
> > data = bsize=4096 blocks=2097152, imaxpct=25
> > = sunit=0 swidth=0 blks
> > naming =version 2 bsize=4096 ascii-ci=0
> > log =internal log bsize=4096 blocks=2560, version=2
> > = sectsz=512 sunit=0 blks, lazy-count=0
> > realtime =none extsz=4096 blocks=0, rtextents=0
> >
> > # xfs_check /dev/malowazne/test
> > # xfs_check /dev/malowazne/test
> >
> > It's still clean.
> >
> > # xfs_admin -c 1 /dev/malowazne/test
> > Enabling lazy-counters
> > # xfs_check /dev/malowazne/test
> > sb_features2 (0xa) not same as sb_bad_features2 (0x8)
> ....
>
> > So as you can see lazy conters are still turn on.
> > I'm using:
> > # mkfs.xfs -V
> > mkfs.xfs version 3.0.3
>
> This was fixed in 3.0.5, IIRC. Please upgrade.
Actually, 3.1.0 was the first release with the fix to xfs_db that
prevents this problem.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-29 1:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 14:34 Enabling lazy counters damages filesystem Marcin Mirosław
2010-04-28 21:40 ` Eric Sandeen
2010-04-28 23:04 ` Dave Chinner
2010-04-29 1:43 ` Dave Chinner [this message]
2010-04-29 1:51 ` Eric Sandeen
2010-04-29 2:05 ` Dave Chinner
2010-04-29 8:03 ` Marcin Mirosław
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=20100429014312.GA2512@dastard \
--to=david@fromorbit.com \
--cc=marcin@mejor.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox