From: "Theodore Ts'o" <tytso@mit.edu>
To: Jeff Schaller <schaller@freeshell.org>
Cc: sct@redhat.com, akpm@zip.com.au, adilger@clusterfs.com,
mingo@redhat.com, neilb@cse.unsw.edu.au, ext3-users@redhat.com,
linux-raid@vger.kernel.org
Subject: Re: Assertion failure, BUG at journal.c:1732
Date: Sun, 24 Nov 2002 18:42:21 -0500 [thread overview]
Message-ID: <20021124234220.GA17874@think.thunk.org> (raw)
In-Reply-To: <Pine.NEB.4.44.0211232017520.8377-200000@iceland.freeshell.org>
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
next prev parent reply other threads:[~2002-11-24 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 19:43 Assertion failure, BUG at journal.c:1732 Jeff Schaller
2002-11-23 20:18 ` Jeff Schaller
2002-11-24 23:42 ` Theodore Ts'o [this message]
2002-12-02 11:15 ` Jeff Schaller
2002-11-25 15:08 ` Stephen C. Tweedie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021124234220.GA17874@think.thunk.org \
--to=tytso@mit.edu \
--cc=adilger@clusterfs.com \
--cc=akpm@zip.com.au \
--cc=ext3-users@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@cse.unsw.edu.au \
--cc=schaller@freeshell.org \
--cc=sct@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.