Most recent kernel where this bug did not occur: 2.6.13.3 Distribution: modified Mandrake 10.1 Hardware Environment: Laptop. Samsung disk is Ok. Software Environment: amule is the only software using intensive disk ressources. Disk is ~90% full when the problem occurs. Problem Description: The /home filessytem is remounted read only after a problem on the journal. Steps to reproduce: Messages : localhost kernel: journal_bmap: journal block not found at offset 6156 on hda6 localhost kernel: Aborting journal on device hda6. localhost kernel: __journal_remove_journal_head: freeing b_committed_data localhost last message repeated 2 times localhost kernel: journal commit I/O error localhost kernel: ext3_abort called. localhost kernel: EXT3-fs error (device hda6): ext3_journal_start_sb: Detected aborted journal localhost kernel: Remounting filesystem read-only Kernel is linux 2.6.13.3 Filesystem is ext3.
Is this reproducible? Are there no I/O errors or anything like that reported from the IDE driver?
Le mardi 11 Octobre 2005 17:26, vous avez
> Is this reproducible? Yes, it is, using the amule client.
bugzilla-daemon@osdl.org wrote: > > http://bugzilla.kernel.org/show_bug.cgi?id=5416 Stephen, Vincent can reproducibly hit the journal_bmap() failure. I seem to recall a few such reports a year or two ago, and that you might have spent some time looking into the problem?
Stephen can you comment on this issue?
Vincent, is there anything like software/hardware suspend on this laptop, or possibly a "maintenance partition" that the machine is trying to write to that possibly overlaps with the filesystem?
Le Samedi 4 F
For an unknown reason, logical blocks 6156-7179 are not allocated: debugfs: bmap <8> 6156 0 debugfs: stat <8> Inode: 8 Type: regular Mode: 0600 Flags: 0x0 Generation: 0 User: 0 Group: 0 Size: 33554432 File ACL: 0 Directory ACL: 0 Links: 1 Blockcount: 57416 Fragment: Address: 0 Number: 0 Size: 0 ctime: 0x4174081c -- Mon Oct 18 20:14:52 2004 atime: 0x00000000 -- Thu Jan 1 01:00:00 1970 mtime: 0x4174081c -- Mon Oct 18 20:14:52 2004 BLOCKS: (0-11):1033-1044, (IND):1045, (12-1035):1046-2069, (DIND):2070, (IND):2071, (1036-2059):2072-3095, (IND):3096, (2060-3083):3097-4120, (IND):4121, (3084-4107):4122-5145, (IND):5146, (4108-5131):5147-6170, (IND):6171, (5132-6155):6172-7195, (IND):7196, (IND):8221, (7180-8191):8222-9233 TOTAL: 7177
Vincent needed to use the ext3 filesystem, so I removed/added the journal. He has confirmed that the problem is gone away. However, how he got into this situation is still not understood.
Any update on this bug? Has this happen again since time of reported failure? Thanks.
Closing the bug, since everything seems to be OK. Please reopen if the problem re-appears.