| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Enabling lazy counters damages filesystem |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Wed, 28 Apr 2010 20:51:30 -0500 |
| Cc: | Marcin Mirosław <marcin@xxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <20100429014312.GA2512@dastard> |
| References: | <4BD84771.4030804@xxxxxxxx> <20100428230447.GJ9783@dastard> <20100429014312.GA2512@dastard> |
| User-agent: | Thunderbird 2.0.0.24 (Macintosh/20100228) |
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
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Enabling lazy counters damages filesystem, Dave Chinner |
|---|---|
| Next by Date: | Re: Enabling lazy counters damages filesystem, Dave Chinner |
| Previous by Thread: | Re: Enabling lazy counters damages filesystem, Dave Chinner |
| Next by Thread: | Re: Enabling lazy counters damages filesystem, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |