-----BEGIN PGP SIGNED MESSAGE-----
On Tue, 6 Mar 2012, Dave Chinner wrote:
> 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 wrong with your
That's a very good news for me.
> So you're using the versions that detect inconsistencies correctly,
> and also write everythign consistently. So it's a problem from an
> old mkfs binary (2.9.x or 3.0.x) or caused by something you've done
> poking around with xfs_db.
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 probably more than 7-8 years old.
The only thing I set to those filesystem over the years is log2 attribute
using xfs_admin (and the filesystem label). But since xfs_admin cannot set
the ATTR2 I had to use xfs_db.
> "Once xfs_info reports attr=2 for the filesytem, you
> can remove the attr2 mount option..."
> The attr2 feature bit will only get set when the attr2 format
> is first used, so if you're workload isn't causing attr2 format
> inodes to be created, the feature bit will not get set. Hence you
> need to leave the mount option set until xfs_info (which reads the
> superblock feature bits) reports it being set.
Oh... I see. Thank you.
> IOWs, if you have to resort to using xfs_db to set a feature bit,
> you are doing something wrong. xfs_admin and/or mount options give
> you control over all feature bits that are safe for user
OK. I'll keep that in mind.
> There's nothing wrong with either of them, likewise there is nothing
> really wrong with your filesystem.
However, it would be nice if xfs_repair would correct secondary
> > An most important: it's possible in the future to loose some data?
OK. That's what it really matter.
> So, if you want to make everything absolutely consistent with xfs_db
> (seeing as something is inconsistenti as a result of either the age
> of the filesystems or the poking you've done) then you need to copy
> the sb_features2 field to sb_bad_features2 field in every secondary
> superblock. i.e. something like:
Thanks, but I think I'm going to skip this. In the future maybe I will
try-it but not for now.
Thank you very much for your help.
// Gabriel VLASIU
// OpenGPG-KeyID : 0xE684206E
// OpenGPG-Fingerprint: 0C3D 9F8B 725D E243 CB3C 8428 796A DB1F E684 206E
// OpenGPG-URL : http://www.vlasiu.net/public.key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
-----END PGP SIGNATURE-----