On Wed, Apr 01, 2015 at 09:54:15PM +0800, Eryu Guan wrote: > xfs used to panic in this test, this xfs commit fix the bug > > 8d6c121 xfs: fix buffer use after free on IO error > > ext4 and btrfs trigger WARNING on current 4.0-rc3 kernel > > Signed-off-by: Eryu Guan <[email protected]> .... > +# lvm uses some space for metadata > +_scratch_mkfs_sized $((300 * 1024 * 1024)) >>$seqres.full 2>&1 > +$LVM_PROG vgcreate -f $vgname $SCRATCH_DEV >>$seqres.full 2>&1 > +$LVM_PROG lvcreate --yes -L 256M -n $lvname $vgname >>$seqres.full 2>&1 > + > +# _mkfs_dev exits the test on failure, this can make sure lv is created in > +# above vgcreate/lvcreate steps > +_mkfs_dev /dev/mapper/$vgname-$lvname
So on my 1p test VM, this fails with +mkfs.xfs: cannot open /dev/mapper/vg_081-base_081: Device or resource busy The problem is that udev has not finished setting up the device before mkfs is run. Hence we need a "udevadm settle" call after the lvcreate call. This results in mkfs succeeding on this machine. Eryu, I'm going to commit the test as it stands as it works on all my other test systems - can you write a followup patch that does the udev settle call in a portable manner? i.e. older systems used to have a 'udev-settle' command, do we still care about that? Cheers, Dave. -- Dave Chinner [email protected] -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
