- 1. failed to set versionnum in AG 1 (score: 1)
- Author: Gabriel VLASIU <gabriel@xxxxxxxxxx>
- Date: Sun, 4 Mar 2012 18:09:12 +0200 (EET)
- Hi! On all my older partitions with xfs I have this problem: versionnum [0xb4b4+0x8] = V4,ATTR,NLINK,ALIGN,DIRV2,LOGV2,EXTFLG,MOREBITS,ATTR2 writing all SBs Superblock has mismatched features2 fields
- /archives/xfs/2012-03/msg00098.html (7,676 bytes)
- 2. Re: failed to set versionnum in AG 1 (score: 1)
- Author: Dave Chinner <david@xxxxxxxxxxxxx>
- Date: Mon, 5 Mar 2012 12:10:32 +1100
- it already has the attr2 feature bit set. What version of xfs_db are you using? And why do you need to set the attr2 feature this way? It gets set automatically when it gets used because on recent ke
- /archives/xfs/2012-03/msg00102.html (8,060 bytes)
- 3. Re: failed to set versionnum in AG 1 (score: 1)
- Author: Gabriel VLASIU <gabriel@xxxxxxxxxx>
- Date: Mon, 5 Mar 2012 09:31:38 +0200 (EET)
- Hi Dave! Yes, it has. But another (old) partition does not have ATTR2 enabled. And the error is the same when I try to set ATTR2. And the funny thing is, after that, version report ATTR2 as set. All
- /archives/xfs/2012-03/msg00109.html (10,808 bytes)
- 4. Re: failed to set versionnum in AG 1 (score: 1)
- Author: Dave Chinner <david@xxxxxxxxxxxxx>
- Date: Tue, 6 Mar 2012 09:28:07 +1100
- That's because the error you are getting is for setting the value into secondary superblocks, but the primary superblock has had the value set correctly. No, most definitely not. There's nothing wron
- /archives/xfs/2012-03/msg00122.html (12,947 bytes)
- 5. Re: failed to set versionnum in AG 1 (score: 1)
- Author: Gabriel VLASIU <gabriel@xxxxxxxxxx>
- Date: Tue, 6 Mar 2012 09:30:23 +0200 (EET)
- Hi! I see. That's a very good news for me. I do not "poke" around filesystems with data. I use xfs in production since redhat 9. I do not know how old are the filesystems in question but some are pro
- /archives/xfs/2012-03/msg00125.html (11,880 bytes)
This search system is powered by
Namazu