[Bug 12272] at random rmmod/insmod corrupts filesystem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



http://bugzilla.kernel.org/show_bug.cgi?id=12272





------- Comment #5 from folkert@xxxxxxxxxxxxxx  2009-01-05 12:11 -------
After that I tried creating a file in each filesystem. When I hit /var I got
the following dmesg error:

[  335.006864] journal_bmap: journal block not found at offset 524 on dm-0
[  335.006927] Aborting journal on device dm-0.
[  353.624981] ext3_abort called.
[  353.625058] EXT3-fs error (device dm-0): ext3_journal_start_sb: Detected
aborted journal
[  353.625211] Remounting filesystem read-only

After that no file was accessible. E.g.:
debian:/home/folkert# umount /var
bash: /bin/umount: cannot execute binary file


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux