When I copy a BIG file, locally (using cp) or from the network (by ftp, using gftp) and the partition becomes full, the system crashes. There is no error message on the console. After the reboot, the partition is full (cp says : no space left...) so the came copy cannot start and it doesn't crash. Reproducible: Always Steps to Reproduce: 1. 2. 3.
I forgot to say that the kernel was compiled with gcc-3.2.2. Note : I think it comes from the kernel because if i boot on the livecd, the same copy on the same partition normally ends with "no space left on device"
its a known xfs problem, ill be releasing new xfs-sources soon, has latest xfs patchset.
I confirm this bug, already reported as #14487. After two days of testing the new (unstable) xfs-sources-2.4.20-r3 I have successfuly compiled a kernel with my usual configuration which doesn't crash both on my computer and in VMWare. However, this unstable release doesn't contain the "gcc31-compile-optimalizations" patch, so I set the Processor family option to "Pentium-III/Celeron(Coppermine)". After applying the gcc31 patch myself and compiling the kernel with my original option "Athlon-XP(gcc>31)" the bug appeared again. This could probably signalize a possible bug in GCC. I will do additional tests in the following days, but for now I can describe in more detail what is happening during the crash: Kernel processes kupdated, bdflush and the process creating the file which fills the filesystem take 100% of the CPU time (100% is indicated in "system"). The system doesn't freeze, processes which don't do any disk I/O remain running (i.e. bash, top), but every process freezes in kernel-space if it tries to access any filesystem. Software configuration: gcc version 3.2.2 glibc 2.3.1-r4 Hardware configuration: Athlon XP 2000+ motherboard Soltek 75DRV (VIA KT266)
