On Sat, 1 Aug 2009 at 12:56, David Rientjes wrote: > This is a different issue than bug 13666, this is in the ext4 mount code > (which can also probably happen with other filesystems as well). OK, thanks for clarifying this. > What are your mount options? It appears that they are causing the parser > to allocate far more memory than it should ever need. This was the first time I mounted this ext4 fileystem since the reboot with the new kernel: /dev/mapper/wdc0 /mnt/disk0 ext4 rw,nosuid,nodev,noexec,relatime,barrier=1,data=ordered 0 0 Christian. /proc/meminfo now looks like this, I don't have the output what it loooked like right after the WARNING though: bkp:~$ cat /proc/meminfo MemTotal: 1024968 kB MemFree: 14164 kB Buffers: 24800 kB Cached: 864356 kB SwapCached: 852 kB Active: 472728 kB Inactive: 506644 kB Active(anon): 42780 kB Inactive(anon): 48164 kB Active(file): 429948 kB Inactive(file): 458480 kB Unevictable: 0 kB Mlocked: 0 kB HighTotal: 129864 kB HighFree: 252 kB LowTotal: 895104 kB LowFree: 13912 kB SwapTotal: 1048568 kB SwapFree: 1046780 kB Dirty: 89408 kB Writeback: 100 kB AnonPages: 89592 kB Mapped: 7664 kB Slab: 20476 kB SReclaimable: 12368 kB SUnreclaim: 8108 kB PageTables: 1496 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 1561052 kB Committed_AS: 1043668 kB VmallocTotal: 122880 kB VmallocUsed: 3436 kB VmallocChunk: 108664 kB DirectMap4k: 12280 kB DirectMap4M: 897024 kB -- BOFH excuse #159: Stubborn processes -- 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
