All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J . Mauelshagen" <mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] "umount" LVM stuff
Date: Fri Feb 28 05:26:02 2003	[thread overview]
Message-ID: <20030228122051.A9155@sistina.com> (raw)
In-Reply-To: <3E5CA74E.4030105@machturtle.com>; from dcorbin@machturtle.com on Wed, Feb 26, 2003 at 06:38:54AM -0500

On Wed, Feb 26, 2003 at 06:38:54AM -0500, David Corbin wrote:
> Heinz J . Mauelshagen wrote:
> 
> >Following this thread it kind of looks like you worked around
> >using LVM commands (i.e. removed a VG w/o using lvremove + vgremove).
> >
> >If so, not a good idea :(
> >  
> >
> Well, not to my knowledge I didn't.   But my knowledge of LVM is very 
> tiny.  All I remember doing was "vgchange -a n".
> 
> >What does pvscan list ?
> >  
> >
> pvscan -- reading all physical volumes (this may take a while...)
> pvscan -- ACTIVE   PV "/dev/md0" of VG "vg0" [109.77 GB / 109.77 GB free]
> pvscan -- total: 1 [109.78 GB] / in use: 1 [109.78 GB] / in no VG: 0 [0]
> 
> >What does vgck say ?
> >
> vgck -- VGDA of "vg0" in lvmtab is consistent
> vgck -- VGDA of "vg0" on physical volume is consistent

This all looks ok.

Doesn't "vgchange -a y" bring your VG back ?
If not so, try "vgscan ; vgchange -ay".

Regards,
Heinz    -- The LVM Guy --


> 
> >
> >On Mon, Feb 24, 2003 at 07:00:33AM -0500, David Corbin wrote:
> >  
> >
> >>Goetz Bock wrote:
> >>
> >>    
> >>
<SNIP>
> >>Fundamentally, I'm building a critical data file server.  LVM has caused 
> >>me enough problems and delays, that I'm about ready to bypass it, saying 
> >>it is putting my data at risk.  Feel free to convince me otherwise.
> >>
> >>Thanks
> >>David
> >>
> >>
> >>_______________________________________________
> >>linux-lvm mailing list
> >>linux-lvm@sistina.com
> >>http://lists.sistina.com/mailman/listinfo/linux-lvm
> >>read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> >>    
> >>
> >
> >  
> >
> 
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

*** 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:[~2003-02-28  5:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-23  8:53 [linux-lvm] "umount" LVM stuff David Corbin
2003-02-23 11:13 ` Goetz Bock
2003-02-23 12:58   ` David Corbin
2003-02-23 19:16     ` Goetz Bock
2003-02-23 19:24       ` Goetz Bock
2003-02-24  6:01         ` David Corbin
2003-02-25  9:27           ` Heinz J . Mauelshagen
2003-02-26  5:39             ` David Corbin
2003-02-28  5:26               ` Heinz J . Mauelshagen [this message]
2003-02-28  6:48                 ` David Corbin
2003-02-28 11:13                   ` Heinz J . Mauelshagen
2003-02-28 13:59                     ` David Corbin

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=20030228122051.A9155@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.