On Wed, Jan 11, 2017 at 7:32 PM, Darrick J. Wong <darrick.wong@xxxxxxxxxx> wrote: > On Wed, Jan 11, 2017 at 12:01:22PM +0200, Amir Goldstein wrote: ... > Ok well I definitely don't see /this/ happening. I gather you built > xfsprogs with the insane geometry patch; if so, against what git commit? against djwon-devel from your tree: 75581a8 xfs_db: sanitize geometry on load 2efc292 xfs_scrub: create a script to scrub all xfs filesystems xfstests head is: 1377e1e xfs: fuzz every field of every structure > And, did the binary get installed as /usr/sbin/xfs_db, or is this just > the system xfs_db? /usr/sbin/xfs_db I ran "make realclean; make; sudo make install;" My system is ubuntu 16.4, in case it matters for shell or anything. > > In any case, all that extra output is supposed to end up in > $seqres.full, not on stdout. At most you should see admonishments about > scrub or repair failing to detect/fix things; those messages look like: > > "offline repair failed (4) with $field = $fuzzverb" > Strange. Anyway it's late now and run has not completed yet. Tomorrow I'll narrow down on 1301 and 1316 to see what's what. Hopefully, we can get another test sample from Eryu by then, to see if I'm the only one seeing these errors. Amir. -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
