|
From: Anton A. <ai...@ca...> - 2007-09-14 19:34:27
|
Hi, On 14 Sep 2007, at 20:12, mar...@es... wrote: >>> escabot CAD # ls -ltrh >>> total 49G >>> -r-------- 1 root root 2.0G Oct 7 2004 RTC26001.GHS >>> -r-------- 1 root root 2.0G Oct 7 2004 RTC26002.GHS >>> -r-------- 1 root root 2.0G Oct 7 2004 RTC2604.GHO >>> -r-------- 1 root root 620M Oct 7 2004 RTC26003.GHS >>> -r-------- 1 root root 4 Sep 14 09:32 asdf.txt >>> -r-------- 1 root root 8 Sep 14 09:33 rty.txt >>> -r-------- 1 root root 42G Sep 14 10:36 bigfile.gho >>> escabot CAD # cp bigfile.gho /dev/null > > Whoops! Sorry, it still causes the kernel to panic when I copy to / > dev/null. Hm. There goes my theory. Either it must be NTFS itself that is at fault or it is a bug in the VFS/VM. Could you now try the following two things and let me know whether they work/panic? 1) Reboot and place "mem=2G" on the kernel command line (this makes the kernel use only 2G of your RAM instead of all 12G). Then try the copy of bigfile.gho to /dev/null again. Does it now work or panic again? 2) Given you are compiling your own kernels already, could you please try the recompiling the kernel but this time disable high memory support completely. This causes the kernel to only use less than 1G of RAM and memory is then used differently. Then try to copy of bigfile.gho to /dev/null again. Does it now work or panic again? Thanks a lot for doing all this! Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ |
