From: Joachim Zobel <jzobel@heute-morgen.de>
To: reiserfs-list@namesys.com
Subject: Yet another reiserfs<dm<md corruption
Date: Sun, 10 Apr 2005 20:04:45 +0200 [thread overview]
Message-ID: <1113156285.4681.7.camel@localhost> (raw)
Hi.
After upgrading to the latest sarge (on x86 withe ide) I found a lvm2
logical partition with reiserf 3.6 on a software raid1 corrupted. Trying
to reiserfsck --rebuild-tree it I got:
-------
The problem has occurred looks like a hardware problem (perhaps
memory). Send us the bug report only if the second run dies at
the same place with the same block number.
build_the_tree: Nothing but leaves are expected. Block 9746 - unknown
-------
Actually the block number changes when I rerun the fsck, however there
are no syslog entries abot drive problems. So probably the "hardware
problem" is in fact a device mapper problem, right?
Sincerely,
Joachim
next reply other threads:[~2005-04-10 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 18:04 Joachim Zobel [this message]
2005-04-11 18:04 ` Yet another reiserfs<dm<md corruption E.Gryaznova
[not found] ` <1113246505.4614.9.camel@localhost>
2005-04-12 20:48 ` E.Gryaznova
2005-04-13 1:48 ` David Masover
2005-04-13 17:20 ` E.Gryaznova
-- strict thread matches above, loose matches on Subject: below --
2005-04-11 19:14 Joachim Zobel
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=1113156285.4681.7.camel@localhost \
--to=jzobel@heute-morgen.de \
--cc=reiserfs-list@namesys.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.