Some LTP filesystem test cases fail when XFS is tested with a 300M block device. The device size appears to be too small or unsuitable for the XFS test scenario, causing mkfs.xfs, mount, or follow-up filesystem operations to fail.
https://github.com/linux-test-project/ltp/blob/master/lib/tst_device.c#L34
And also observed that umount does not seem to take effect immediately in this scenario. If mount is executed right after umount, the next mount may fail. Is this expected behavior, or should umount returning imply that the filesystem/device state is already ready for a subsequent mount?
Some LTP filesystem test cases fail when XFS is tested with a 300M block device. The device size appears to be too small or unsuitable for the XFS test scenario, causing mkfs.xfs, mount, or follow-up filesystem operations to fail.
https://github.com/linux-test-project/ltp/blob/master/lib/tst_device.c#L34
And also observed that umount does not seem to take effect immediately in this scenario. If mount is executed right after umount, the next mount may fail. Is this expected behavior, or should umount returning imply that the filesystem/device state is already ready for a subsequent mount?