All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian McCullough <bdmc@bdmcc-us.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lvm and fstab
Date: Thu, 29 Jun 2006 10:36:19 -0400	[thread overview]
Message-ID: <20060629143619.GA29133@bdmcc-us.com> (raw)
In-Reply-To: <44A3E3FB.901@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]

On Thu, Jun 29, 2006 at 04:30:19PM +0200, ThomasC. wrote:
> Cristian Livadaru wrote:
> >On Thu, Jun 29, 2006 at 04:10:31PM +0200, ThomasC. wrote:
> >>Hi,
> >>
> >>I am using RHEL3.
> >>One LV for /opt and another one for /stage.
> >>
> >enter the mount points manualy in fstab or mount the partitions manualy
> >...
> >you could do a mount /dev/Volume00/LogVol00 /opt and then you should
> >have what you want.
> >
> >Best Regards, Cristian Livadaru
> Thats what i thought but the weird thing is that i can already access 
> /opt so i am not very enthusiastic trying to mount it again....

I agree with your reluctance.

What I would do, being the paranoid person that I am, is create a second
mount point, called /opt-1 or something else that you like, and mount
your LV there, as "mount /dev/Volume00/LogVol00 /opt-1" and compare the
two.  I suspect that you will find that your /opt-1 will be empty, in
which case you can then move all of the files in /opt to /opt-1, unmount
/opt-1, remount it as /opt, fix your /etc/fstab and everything will be
as you expect.

I was about to go on and suggest that you could then add /stage to your
/etc/fstab, but we don't know whether it was actually created.  What
does "lvscan" show?


Brian


[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2229 bytes --]

  parent reply	other threads:[~2006-06-29 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 14:10 [linux-lvm] lvm and fstab ThomasC.
2006-06-29 14:23 ` Cristian Livadaru
2006-06-29 14:30   ` ThomasC.
2006-06-29 14:33     ` Cristian Livadaru
2006-06-29 14:36     ` Brian McCullough [this message]
2006-06-29 15:53 ` Dieter Stüken
2006-06-30  7:33   ` ThomasC.

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=20060629143619.GA29133@bdmcc-us.com \
    --to=bdmc@bdmcc-us.com \
    --cc=linux-lvm@redhat.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.