From: Jakob Borg <jakob@borg.pp.se>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG with 2.4.1-pre7 reiserfs
Date: Tue, 16 Jan 2001 19:58:37 +0100 [thread overview]
Message-ID: <20010116195837.A707@borg.pp.se> (raw)
In-Reply-To: <20010116192041.A466@borg.pp.se> <9424br$j3h$1@penguin.transmeta.com>
In-Reply-To: <9424br$j3h$1@penguin.transmeta.com>; from torvalds@transmeta.com on Tue, Jan 16, 2001 at 10:36:43AM -0800
On Tue, Jan 16, 2001 at 10:36:43AM -0800, Linus Torvalds wrote:
> >I seem to remember more possibly useful information scrolling by my screen,
> >but it seems to not have made it to the logs, and I will shut down and fsck
> >the filesystem now...
>
> It really needs the stack-trace to debug this sanely (along with
> translations of what the hex numbers are - see the bugreporting
> documentation in the kernel source tree).
Got that in the other mail subjected "More information ... ". In the
meantime it seems the filesystem is unhurt because of this, but reiserfsck
says
uread_super_block: bad block is found at a new superblock location
uread_super_block: bad block is found at an old superblock location
which seems bogus. This is reiserfsck from the same suite that mkreiserfs
came from ("reiserfsprogs 3.x") so they should be talking about the same
sort of filesystem.
Regards,
--
Jakob Borg mailto:jakob@borg.pp.se (personal)
UNIX/network admin mailto:jakob@debian.org (development)
systems programmer mailto:jakob@morotsmedia.se (work)
http://jakob.borg.pp.se/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-16 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 18:20 kernel BUG with 2.4.1-pre7 reiserfs Jakob Borg
2001-01-16 18:36 ` Linus Torvalds
2001-01-16 18:58 ` Jakob Borg [this message]
2001-01-16 19:18 ` Chris Mason
2001-01-16 19:20 ` Jakob Borg
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=20010116195837.A707@borg.pp.se \
--to=jakob@borg.pp.se \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox