From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: "Marcin Mirosław" <marcin@mejor.pl>, xfs@oss.sgi.com
Subject: Re: Enabling lazy counters damages filesystem
Date: Wed, 28 Apr 2010 20:51:30 -0500 [thread overview]
Message-ID: <4BD8E622.80100@sandeen.net> (raw)
In-Reply-To: <20100429014312.GA2512@dastard>
Dave Chinner wrote:
...
> Actually, 3.1.0 was the first release with the fix to xfs_db that
> prevents this problem.
>
> Cheers,
>
> Dave.
not so sure:
# rpm -q xfsprogs
xfsprogs-3.1.1-7
# mkfs.xfs -dfile,name=fsfile,size=10g -llazy-count=0
meta-data=fsfile isize=256 agcount=4, agsize=655360 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=2621440, 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_admin -c 1 fsfile
Enabling lazy-counters
# xfs_check fsfile
sb_features2 (0xa) not same as sb_bad_features2 (0x8)
# xfs_repair fsfile
Phase 1 - find and verify superblock...
superblock has a features2 mismatch, correcting
writing modified primary superblock
...
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-29 1:49 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
2010-04-29 1:51 ` Eric Sandeen [this message]
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=4BD8E622.80100@sandeen.net \
--to=sandeen@sandeen.net \
--cc=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