These messages tend to indicate that the filesystem is probably corrupted. For some reason the kernel is triggering a BUG before marking the filesystem as containing an error, so fsck isn't being run on the filesystem. If you run e2fsck on the filesystem manually, before it is mounted (or remounted read-write, if it the root filesystem), it should correct the problem. I am curious what was the specific form of filesystem corruption which was triggerring your problem. If you could save a transcript of the e2fsck run (say, by running it under the script program, assuming you have a writeable filesystem available to you when you rune2fsck), I would be much obliged. - Ted > Nov 20 18:35:39 debian kernel: attempt to access beyond end of device > Nov 20 18:35:39 debian kernel: 09:00: rw=1, want=39121472, limit=39121408 > Nov 20 18:35:39 debian kernel: attempt to access beyond end of device > Nov 20 18:35:39 debian kernel: 09:00: rw=1, want=39121476, limit=39121408 > Nov 20 18:35:39 debian kernel: attempt to access beyond end of device > Nov 20 18:35:39 debian kernel: 09:00: rw=1, want=39121480, limit=39121408 > Nov 20 18:35:39 debian kernel: attempt to access beyond end of device > Nov 20 18:35:39 debian kernel: 09:00: rw=1, want=39121484, limit=39121408 > Nov 20 18:35:39 debian kernel: attempt to access beyond end of device > Nov 20 18:35:39 debian kernel: 09:00: rw=1, want=39121488, limit=39121408 > Nov 20 18:35:48 debian kernel: Assertion failure in __journal_remove_journal_head() at journal.c:1732: "buffer_jbd(bh)" > Nov 20 18:35:48 debian kernel: kernel BUG at journal.c:1732! > Nov 20 18:35:48 debian kernel: invalid operand: 0000 _______________________________________________ Ext3-users@redhat.com https://listman.redhat.com/mailman/listinfo/ext3-users
