From: "E.Gryaznova" <grev@namesys.com>
To: jzobel@heute-morgen.de
Cc: reiserfs-list@namesys.com
Subject: Re: Yet another reiserfs<dm<md corruption
Date: Mon, 11 Apr 2005 22:04:12 +0400 [thread overview]
Message-ID: <425ABC1C.2030001@namesys.com> (raw)
In-Reply-To: <1113156285.4681.7.camel@localhost>
Joachim Zobel wrote:
>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?
>
>
Would you please send the following commands outputs?:
# dmsetup deps
# dmsetup status
# dmsetup info
# pvdisplay --map
# lvdisplay --map -vv
# ls -l /dev/vg (and /dev/mapper)
Thanks,
Lena
>Sincerely,
>Joachim
>
>
>
>
>
next prev parent reply other threads:[~2005-04-11 18:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 18:04 Yet another reiserfs<dm<md corruption Joachim Zobel
2005-04-11 18:04 ` E.Gryaznova [this message]
[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=425ABC1C.2030001@namesys.com \
--to=grev@namesys.com \
--cc=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.