linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] vgchange -a y /dev/System fails
Date: Wed Jan 30 06:20:02 2002	[thread overview]
Message-ID: <20020130131530.B3769@sistina.com> (raw)
In-Reply-To: <E16ViXz-0001vP-00@hermes.sistina.com>; from ahead@bigpond.net.au on Wed, Jan 30, 2002 at 10:24:35AM +1000

On Wed, Jan 30, 2002 at 10:24:35AM +1000, Adrian Head wrote:
> 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.

Well, as linux-kernel reports there's still problems with 2.4 up to .17 in
the vm subsystem which show up on heavier load or on long running systems.
Andrea Arcangeli has some fixes but I don't know if they already have been
ported to 2.4.18-pre jet.

> 
> 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.)
> 
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2002-01-30  6:20 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
2002-01-30  6:20   ` Heinz J . Mauelshagen [this message]
  -- 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=20020130131530.B3769@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;
as well as URLs for NNTP newsgroup(s).