Bug 19212
Summary: | kernel BUG at /build/buildd/linux-2.6.32/fs/ext4/extents.c:1716 | ||
---|---|---|---|
Product: | File System | Reporter: | Steve Mushero (kernel_sm) |
Component: | ext4 | Assignee: | fs_ext4 (fs_ext4) |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | alan, mikhail.vorozhtsov |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.32 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Steve Mushero
2010-09-28 01:56:24 UTC
Seems like it hit me. A few days ago a regular fsck run detected multiply-claimed blocks on my /home and asked me to clone them. I answered "yes". After that my kernel started oopsing 3-4 times a day. The process is either transmission-gtk or flush-XYZ (with slightly different call traces, but with the same code location). The message is (transmission-gtk variant, the exact message is not in the logs, I'm posting the lines I wrote down on a paper): kernel BUG at fs/ext4/extents.c:1784 RIP: ext4_ext_insert_extent Call trace: ext4_ext_map_blocks ? pagevec_lookup_tag ext4_map_blocks mpage_da_map_and_submit ? jbd2_journal_start ? ext4_da_writepages __filemap_fdatawrite_range filemap_write_and_wait_range vfs_fsync_range vfs_fsync sys_fsync system_call_fastpath After rebooting fsck -f doesn't find any errors. Kernel version is 2.6.39.1, e2fsprogs version is 1.41.14. |