Linux LVM users
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Oops ...
Date: Fri, 13 Jul 2001 13:07:33 +0200	[thread overview]
Message-ID: <20010713130733.B32198@sistina.com> (raw)
In-Reply-To: <20010713093946.C1563@btconnect.com>; from thornber@btconnect.com on Fri, Jul 13, 2001 at 09:39:46AM +0100

On Fri, Jul 13, 2001 at 09:39:46AM +0100, Joe Thornber wrote:
> All,
> 
> Do not use the current CVS code on existing VG's, and certainly not on
> production systems.  I thought this had been mentioned on the list
> before.

Yes it has!

Please be aware, that actual CVS represent the project under construction
and that you are on your own if you retrieve LVM from there.

There's rare cases in which we'll recommend to use it in order to address
paricular problems you face.

Rule is: get CVS on your own risk unless told by us.

Thanks for your understanding :-)

Regards,
Heinz    -- The LVM Guy --



> 
> Changes have been made to the PE locations !
> 
> Bas: you need to roll back your tools to beta7, the CVS kernel driver
> should be ok.
> 
> - Joe
> 
> On Thu, Jul 12, 2001 at 07:06:59PM +0200, Bas wrote:
> > Hi,
> > 
> > I'm afraid I'm not able to get more details right now, if necessary I'll get
> > 'm later on, but I don't like playing with my filesystems ...
> > 
> > Kernel 2.4.6
> > CVS LVM of 11 July 2001
> > an XFS enabled kernel
> > devfs 1.82.
> > 
> > Boots fine, loads the LVM driver, but after it oopses after running
> > vgchange -a y (line 4, linuxrc).
> > 
> > What can I do ?
> > 
> > Thanks,
> > Bas.
> > 
> > _______________________________________________
> > 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

      reply	other threads:[~2001-07-13 11:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-12 17:06 [linux-lvm] Oops Bas
2001-07-13  8:39 ` Joe Thornber
2001-07-13 11:07   ` Heinz J. Mauelshagen [this message]

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=20010713130733.B32198@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