From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Help! unable to mount lv's - can't see why!
Date: Thu Sep 19 05:05:23 2002 [thread overview]
Message-ID: <20020919120453.C32578@sistina.com> (raw)
In-Reply-To: <011401c25f21$b15f7da0$1c01a8c0@internal.tripnet.int>; from red@tripany.com on Wed, Sep 18, 2002 at 04:42:54PM +0200
On Wed, Sep 18, 2002 at 04:42:54PM +0200, Robin Edgar - Tripany wrote:
> Doing the lvdisplay -v shows that pv /dev/hde1 had bits of all of the lv's
> on it (including the docu lv, which I *can* mount).
Then it is most likely, that all filesystems will have errors.
Regards,
Heinz -- The LVM Guy --
>
> ----- Original Message -----
> From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
> To: <linux-lvm@sistina.com>
> Sent: Wednesday, September 18, 2002 3:59 PM
> Subject: Re: [linux-lvm] Help! unable to mount lv's - can't see why!
>
>
> > On Wed, Sep 18, 2002 at 03:56:36PM +0200, Robin Edgar - Tripany wrote:
> > > I've discovered that there is a problem with /all/ the superblocks
> except for those of the /docu lv (see below). It does lead me to another
> question though - only one of the HDs crashed: is it possible that LVM wrote
> all the superblocks on 1 HD?! If so this seems like a pretty serious bug in
<SNIP>
> > linux-lvm mailing list
> > linux-lvm@sistina.com
> > http://lists.sistina.com/mailman/listinfo/linux-lvm
> > read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
> >
> >
>
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@Sistina.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2002-09-19 5:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-18 6:37 [linux-lvm] Help! unable to mount lv's - can't see why! Robin Edgar - Tripany
2002-09-18 8:20 ` Heinz J . Mauelshagen
2002-09-18 9:07 ` Robin Edgar - Tripany
2002-09-19 5:10 ` Heinz J . Mauelshagen
2002-09-18 8:27 ` Robin Edgar - Tripany
2002-09-18 9:01 ` Heinz J . Mauelshagen
2002-09-18 9:17 ` Robin Edgar - Tripany
2002-09-19 5:05 ` Heinz J . Mauelshagen [this message]
2002-09-19 5:17 ` Robin Edgar - Tripany
2002-09-19 8:55 ` Heinz J . Mauelshagen
2002-09-19 9:36 ` Robin Edgar - Tripany
2002-09-19 14:09 ` Heinz J . Mauelshagen
2002-09-20 4:29 ` Robin Edgar - Tripany
2002-09-20 4:51 ` Heinz J . Mauelshagen
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=20020919120453.C32578@sistina.com \
--to=mauelshagen@sistina.com \
--cc=linux-lvm@sistina.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