On 2011-06-18, at 11:39 AM, Stephan Boettcher wrote: > Andreas Dilger <adilger@xxxxxxxxx> writes: >> There are a few places in the ext4 mount that are doing large >> allocations. In some places they fall back to vmalloc, so they should >> really be done with GFP_NOWARN. >> >> A few places don't yet fall back to vmalloc(), which is a problem >> with fragmented memory or very large filesystems. We were trying to >> test a 192TB ext4 filesystem, but were unable to mount it without >> patching the kernel. > > :-O ... my puny 20TB ext4 filesystem did not do something like > this, yet. What sort of experience do you have with using a filesystem > 20TB? I don't think there are many users out there yet that are doing this today, so it would be great if you could share some data with us. So far, we've only been doing testing and benchmarking (mke2fs, e2fsck times, IO and metadata load tests, etc) and I don't know that all of the "real world" corner cases have been tested yet. Cheers, Andreas -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
