I disabled ntfs and as you suspected my problem went away. This worked
for both 2.4.16 and 2.4.17pre4aa1.
Thanks a lot,
Andrea Arcangeli wrote:
| Even better would be to change fs/ntfs/* to avoid using vmalloc for tons
| of little pieces. It's not only a matter of wasting direct mapped
| address space, but it's also a matter of running fast, mainly on SMP
| with the IPI for the tlb flushes...
| attr.c:233: new = ntfs_vmalloc(new_size);
| attr.c:235: ntfs_error("ntfs_insert_run:
| ntfs_vmalloc(new_size = "
| attr.c:458: rlt = ntfs_vmalloc(rl_size);
| inode.c:1297: rl = ntfs_vmalloc(rlen << sizeof(ntfs_runlist));
| inode.c:1638: rlt =
| inode.c:1942: rl2 = ntfs_vmalloc(rl2_size);
| inode.c:2006: rlt = ntfs_vmalloc(rl_size);
| super.c:810: rlt = ntfs_vmalloc(rlsize);
| super.c:1335: buf = ntfs_vmalloc(buf_size);
| support.h:29:#include <linux/vmalloc.h>
| support.h:35:#define ntfs_vmalloc(size) vmalloc_32(size)
| In short there are three solutions avaialble:
| 1) don't use ntfs
| 2) fix ntfs
| 3) enlarge vmalloc address space with the above patch, but this won't be
| a final solution because you'll overflow again the vmalloc address
| space by adding the double of files in your fs
| So I'd redirect this report to Anton Altaparmakov <firstname.lastname@example.org> and
| I still have no VM bugreport pending from my part.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 15 2001 - 21:00:23 EST