Bug 13876
| Summary: | [x86_32, 2.6.30, reiserfs, reiser3, bug, regression] kernel oopsed while Sarg was running | ||
|---|---|---|---|
| Product: | File System | Reporter: | Igor M Podlesny (for.poige+bugzilla.kernel.org) |
| Component: | ReiserFS | Assignee: | ReiseFS developers team (reiserfs-devel) |
| Status: | RESOLVED CODE_FIX | ||
| Severity: | high | CC: | devzero, torvalds |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.30 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Attachments: |
partial dmesg output
Screen photo taken before hard rebooting the box |
||
Created attachment 22538 [details]
Screen photo taken before hard rebooting the box
Hopefully, it gives the missing info — no log file records regarding that issue survived.
could you please provide the mount options for your reiserfs filesystems ? (In reply to comment #2) (rw,relatime,data=journal) ah, we have possibly a duplicate here - see http://bugzilla.kernel.org/show_bug.cgi?id=13556 can you try if mounting your reiserfs filesystems without data=journal fixes the problem ? (In reply to comment #4) > ah, we have possibly a duplicate here - see Well, quite likely we do, yeah. > can you try if mounting your reiserfs filesystems without data=journal fixes > the problem ? Dunno when... so feel free to mark this bug-entry as a dup. Igor, can you try the patch I just added in that bugzilla entry 13556? you can also try latest .31-rc7 kernel from kernel.org Igor, can you try latest kernel and give some feedback as this ticket would be closed due to missing response? i'm quite sure this/your bug is fixed. if your bug is different, then it`s the last chance to tell about that. > Igor, can you try latest kernel
Roland, that comp. isn't mine; it has been running 2.6.27.something happily for quite a long time now and its users are careless. I don't think it'd be a good idea to tell'em "guys, kernel devs would like to give your box another crash test, wouldn't ya mind, ugh?". :-)
P. S. I tried reproducing this problem inside VirtualBox but failed -- 2.6.30 inside it runs just ok. In case I'll have a chance to meet that bug I'll do my best reporting it. Let me mark this ticket as resolved.
|
Created attachment 22537 [details] partial dmesg output (Sarg is Squid statistic analyzer, giving quite valuable both disk and CPU load.) dmesg is in the attachment. Unfortunately, it's not complete cause the kernel's failure made it impossible to log in to the comp where it occurred. Possibly, it completely remains in the system log files, and I hope since the comp will get rebooted (it's a remote one for me), I'll be able to find the logs and rest of the filesystem... ergh... intact.