On Wed, Aug 16, 2017 at 03:31:59PM +0800, Eryu Guan wrote: > On Wed, Aug 16, 2017 at 03:02:14PM +0800, Eryu Guan wrote: > > > + > > > +_scratch_unmount > > > + > > > +# agi->freecount is 0 here, corrupt it to show extra free inodes > > > +$XFS_DB_PROG -x -c "agi 0" -c "write -d freecount 10" $SCRATCH_DEV >/dev/null 2>&1 > > > > redirect stdout and stderr to $seqres.full for debug purpose > > And you can use _scratch_xfs_db wrapper instead of open coded xfs_db > command. > > And I found that "write -d" failed on a crc=0 XFS, though "write -c" > allows corrupted data and bad CRC, but touch couldn't reproduce the hang > in this case, because kernel detected bad crc first and aborted inode > creation. What error did you get, specifically? Sounds more like a bug in write/fuzz -d to me. :) --D > > I think we can force a CRC enabled XFS by > > _scratch_mkfs -m crc=1,finobt=0 >>$seqres.full 2>&1 > > Thanks, > Eryu > -- > To unsubscribe from this list: send the line "unsubscribe fstests" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
