From: Adrian Head <ahead@bigpond.net.au>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgchange -a y /dev/System fails
Date: Tue Jan 29 18:25:01 2002 [thread overview]
Message-ID: <E16ViXz-0001vP-00@hermes.sistina.com> (raw)
In-Reply-To: <20020125233533.GK26045@merlins.org>
A little while ago I had the same problems - the only way i could get around
it was using 2.4.16-xfs. I was using 2.4.17-xfs+lvm (1.0.1) and when a
snapshot failed I couldn't remove it and when I rebooted the system would
hang. By having a 2.4.16-xfs kernel with lvm-1.0.1rc4(ish) it would fix the
problems on the fly during bootup and all was happy. YMMV At the time I did
ask the mailling list why 2.4.16-xfs was more robust than 2.4.17-xfs+lvm;
however, I never recieved an answer.
Heady
On Sat, 26 Jan 2002 09:35, you wrote:
> It fails and says:
> parameter error setting up snapshot copy on write exception
>
> So yes, I have snapshots in there, but I can't delete the snapshots if
> the volume isn't active, and I can't activate the volume because of a
> snapshot.
>
> To make things worse, /dev/System contains /usr and /var.
>
> The snapshots were created with 1.0.1rc4 on 2.4.14 and I now run 2.4.17
> with 1.0.1rc4-ish
>
> What's the magic override I need to use to make the volume active again?
>
> Thanks
> Marc
--
Adrian Head
(Public Key available on request.)
next prev parent reply other threads:[~2002-01-29 18:25 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
2002-02-01 15:10 ` Marc MERLIN
2002-02-11 13:01 ` Marc MERLIN
2002-01-29 18:25 ` Adrian Head [this message]
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=E16ViXz-0001vP-00@hermes.sistina.com \
--to=ahead@bigpond.net.au \
--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;
as well as URLs for NNTP newsgroup(s).