From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgchange -a y /dev/System fails
Date: Thu Jan 31 05:19:02 2002 [thread overview]
Message-ID: <20020131121417.A9764@sistina.com> (raw)
In-Reply-To: <20020131030417.GN8651@merlins.org>; from marc_lvm@merlins.org on Wed, Jan 30, 2002 at 07:04:17PM -0800
On Wed, Jan 30, 2002 at 07:04:17PM -0800, Marc MERLIN wrote:
> On Wed, Jan 30, 2002 at 01:12:05PM +0100, Heinz J . Mauelshagen wrote:
> > > Unfortunately, that doesn't work because I had a cron job that was creating
> > > daily snapshots (in an attempt to emulate ONTAP's snapshot's feature), so my
> > > 10 backups contain snapshot LVs
> >
> > Well, in this case you might still have a consistent backup with snapshots
> > which you can use like mentioned above.
>
> I tried a few and none seemed to work, but I restored one from before I made
> snapshots and recovered from this.
> I now have my system back (/usr, /var)
>
> As for /home, as soon as I tried to access it (e2fsck, tune2fs -O
> ^has_journal, or whatever), the process hung in "wait_o" according to ps.
>
> I tried to restore the VG to its state before I added snapshots, but that
> only made it go away :-(
>
> mechastreisand:/etc/lvmconf# vgchange -a n /dev/BigAssLVMRaid
<SNIP>
> -> My BigAssLVMRaid VG is gone :-(
>
> Did I just lose my data?
If you really tried all your metadata backups unsuccessfully, I am afraid so :-(
Some users reported snapshot problems with the recent 2.4.x kernels.
They are not 100% reliable due to VM issues being sorted out by the
kernel community hopefully which will hopefully be integrated in 2.4.18.
>
> Marc
> --
> Microsoft is to operating systems & security ....
> .... what McDonalds is to gourmet cooking
>
> Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
>
> _______________________________________________
> 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
--
Regards,
Heinz -- The LVM Guy --
*** 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-01-31 5:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 17:36 [linux-lvm] vgchange -a y /dev/System fails Marc MERLIN
2002-01-28 3:47 ` Heinz J . Mauelshagen
2002-01-29 15:58 ` Marc MERLIN
2002-01-30 6:17 ` Heinz J . Mauelshagen
2002-01-30 21:04 ` Marc MERLIN
2002-01-31 5:19 ` Heinz J . Mauelshagen [this message]
2002-02-01 15:10 ` Marc MERLIN
2002-02-11 13:01 ` Marc MERLIN
2002-01-29 18:25 ` Adrian Head
2002-01-30 6:20 ` Heinz J . Mauelshagen
-- strict thread matches above, loose matches on Subject: below --
2002-01-29 16:02 Marc MERLIN
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=20020131121417.A9764@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 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.