My broken fs http://ixion.pld-linux.org/~arekm/p2/x1/web2-home.metadump.gz thanks to "xfsprogs: fixes for 3.2.1" by Dave is now almost in good shape. What I found interesting is that repairing it with current git xfs_repair and then mounting (-o usrquota,prjquota) on 3.16.0-rc4 gives me: [32208.142316] XFS (sdb): Mounting V4 Filesystem [32208.205449] XFS (sdb): Ending clean mount [32208.258991] XFS (sdb): Quotacheck needed: Please wait. [32821.930437] XFS (sdb): Quotacheck: Done. Then I umount it and mount again (same options as before) but on 3.10.43 kernel: [ 111.325889] XFS (sdb): Mounting Filesystem [ 111.419331] XFS (sdb): Failed to initialize disk quotas. [ 111.419339] XFS (sdb): Ending clean mount What did change in later kernels that could have meaning here? (so I could try to backport that change). For testing I mounted again on 3.16 and: [33870.472769] XFS (sdb): Mounting V4 Filesystem [33870.543539] XFS (sdb): Ending clean mount [33870.597791] XFS (sdb): Quotacheck needed: Please wait. [34484.332879] XFS (sdb): Quotacheck: Done and again on 3.10.43: [ 1649.215390] XFS (sdb): Mounting Filesystem [ 1649.316894] XFS (sdb): Failed to initialize disk quotas. [ 1649.316902] XFS (sdb): Ending clean mount (there was an additional problems with hangs on quotacheck like http://sprunge.us/LYQO (3.16.0-rc3-00006-g16874b2) http://sprunge.us/FfhR (3.15.3) http://sprunge.us/ObWI (3.10.20) but it only happened when doing quotacheck on image mounted via loop. Wasn't able to trigger it when using real disk, so blaming loop code for now) -- Arkadiusz Miśkiewicz, arekm / maven.pl _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
