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 11:13:01 2003	[thread overview]
Message-ID: <20030228180716.A9839@sistina.com> (raw)
In-Reply-To: <3E5F5A85.4010903@machturtle.com>; from dcorbin@machturtle.com on Fri, Feb 28, 2003 at 07:48:05AM -0500

David,

try vgscan then which should bring your device node back.

Regards,
Heinz    -- The LVM Guy --


On Fri, Feb 28, 2003 at 07:48:05AM -0500, David Corbin wrote:
> >
> >
> >This all looks ok.
> >
> >Doesn't "vgchange -a y" bring your VG back ?
> >If not so, try "vgscan ; vgchange -ay".
> >  
> >
> piano:/home/dcorbin# vgchange -ay
> vgchange -- volume group "vg0" already active
> 
> So, it appears that the VG IS there.
> ----
>  piano:/home/dcorbin# mount -t reiserfs /dev/vg0/data /data
> mount: special device /dev/vg0/data does not exist
> 
> /dev/vg0/data is the device I used to use to mount it, and the error 
> message is correct if I look at my filesystem (it doesn't exist).
> ----
> piano:/home/dcorbin# mount -t reiserfs /dev/vg0/group  /data
> mount: /dev/vg0/group is not a block device
> 
> I tried this command because /dev/vg0/group is the only device in /dev/vg0
> ----
> Here are some other commands that I tried that may or may not tell you 
> something...
> 
> piano:/home/dcorbin# 
> lvscan                                                                                                                
> lvscan -- no logical volumes found
> piano:/home/dcorbin# ls -ltar /dev/vg0
> total 28
> crw-r-----    1 root     disk     109,   0 Feb 24 06:53 group
> drwxr-xr-x   10 root     root        24576 Feb 24 06:53 ..
> dr-xr-xr-x    2 root     root         4096 Feb 24 06:53 .
> 
> >Regards,
> >Heinz    -- The LVM Guy --
> >  
> >
> 
> 
> 
> 
> _______________________________________________
> 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 11:13 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
2003-02-28  6:48                 ` David Corbin
2003-02-28 11:13                   ` Heinz J . Mauelshagen [this message]
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=20030228180716.A9839@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.