Bug 35562
| Summary: | ext4 regression in 2.6.39 | ||
|---|---|---|---|
| Product: | File System | Reporter: | zless (arthur.titeica) |
| Component: | ext4 | Assignee: | fs_ext4 (fs_ext4) |
| Status: | RESOLVED INSUFFICIENT_DATA | ||
| Severity: | blocking | CC: | alan, ht990332, tytso |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.39 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Attachments: | kernel.log | ||
1) Can you reproduce this problem reliably? 2) What were you doing at the time of that you saw these messages? 3) Did the system recover eventually, or did it completely hang? The fact that you were able to pull this out of kernel.log afterwards tends to indicate that the system eventually recovered, but I don't want to make that assumption. Or did you eventually have to reboot or reset the machine? 1) Can you reproduce this problem reliably? Re: No, I've tried to replicate the conditions but nothing unusual happened. 2) What were you doing at the time of that you saw these messages? Re: I noticed that all apps got stuck. They looked normal but didn't react to any commands. I tried to su in a terminal emulator I had open but that didn't work either (no error but no login also). 3) Did the system recover eventually, or did it completely hang? Re: I managed to reboot using magic sysrq (REISUB) Some other thing I forgot to mention: the whole system (except /boot) is LVM2 encrypted (crypto_luks). |
Created attachment 58932 [details] kernel.log System is Archlinux x64 which just received kernel 2.6.39 in testing repos. The attached call traces are recorded in kernel.log while I was downloading with ktorrent (max speed 2.5 MB/s). I have little to no experience in producing a good bugzilla report but if more info is needed just ask and I'll do my best.