Bug 35562 - ext4 regression in 2.6.39
Summary: ext4 regression in 2.6.39
Status: RESOLVED INSUFFICIENT_DATA
Alias: None
Product: File System
Classification: Unclassified
Component: ext4 (show other bugs)
Hardware: All Linux
: P1 blocking
Assignee: fs_ext4@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-21 20:05 UTC by zless
Modified: 2012-08-24 13:35 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.39
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
kernel.log (46.91 KB, text/plain)
2011-05-21 20:05 UTC, zless
Details

Description zless 2011-05-21 20:05:11 UTC
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.
Comment 1 Theodore Tso 2011-05-23 14:52:15 UTC
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?
Comment 2 zless 2011-05-23 16:15:27 UTC
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).

Note You need to log in before you can comment on or make changes to this bug.