On Wed, Feb 10, 2016 at 05:00:58PM +1100, Dave Chinner wrote: > > + tmpfs) > > + export MOUNT_OPTIONS="-o size=$fssize $TMPFS_MOUNT_OPTIONS" > > So what happens when the test asks for 10GB of device space, and you > only have 4GB of RAM? The largest amount of storage space requested by shared/generic tests via _scratch_mkfs_sized is 2G, and that's from generic/27[345]. We currently could run into problems today if the storage device only had 3G of space, and some test, such as f2fs/001, called _scratch_mkfs_sized requesting 4G of space. We currently aren't checking error returns from the mkfs command; we just assume that it will succeed. Because of the someone interesting behavior of tmpfs assuming inode space is free, we already have problems where even with 8G of memory, generic/269 and generic/273 will result in the test getting OOM killed, and if you use less than 4G, there are a more tests that end up getting OOM killed as a result. So I think it would be fair to simply document that if you are testing tmpfs, you need a VM or or a memory container with at least 8G of memory. If we start limiting the number of inodes in a tmpfs mount, we could probably bring that requirement down to 4G, which is certainly fair. We do document minimum requirements for the size of the TEST_DEV and SCRATCH_DEV, don't we? (Minimum requirements certainly do exist in practice, in any case.) Cheers, - Ted -- 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
