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: Wed, 13 Apr 2005 00:48:04 +0400 [thread overview]
Message-ID: <425C3404.1090609@namesys.com> (raw)
In-Reply-To: <1113246505.4614.9.camel@localhost>
Hello.
Joachim Zobel wrote:
>Am Montag, den 11.04.2005, 22:04 +0400 schrieb E.Gryaznova:
>
>
>
>>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)
>>
>>
>>
>
>See the attached file reiserfs.log
>
>The devices
>volg2-logv4: 1 dependencies : (22, 3)
>volg2-logv3: 1 dependencies : (22, 3)
>volg2-logv2: 1 dependencies : (22, 3)
>where created after the incident.
>One of them had a successful (some files lost) reiserfsck --rebuild-tree
>after dd-ing the bad /dev/volg-raid1/logv1 on it.
>
>lvdisplay --map -v did some stderr output, which is attached as
>lvdisplay.err
>
>#cat /proc/mdstat
>Personalities : [raid1]
>md0 : active raid1 hda2[0] hdc2[1]
> 3903680 blocks [2/2] [UU]
>
>Sincerely,
>Joachim
>
>
I have checked lvm, it looks ok. Probably this is hardware problem.
If you need our assistance in further investigation, please visit our
support page http://www.namesys.com/support.html .
Thanks,
Lena
next prev parent reply other threads:[~2005-04-12 20:48 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
[not found] ` <1113246505.4614.9.camel@localhost>
2005-04-12 20:48 ` E.Gryaznova [this message]
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=425C3404.1090609@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.