linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: pent 5971 <pent5971@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Understanding if a disk is partioned with LVM or not
Date: Thu, 10 Sep 2009 11:35:10 +0300	[thread overview]
Message-ID: <352f9c2a0909100135i64ac861awaf7089ea27c1b3b3@mail.gmail.com> (raw)
In-Reply-To: <20090910063511.GA7247@maude.comedia.it>

Hi,
Luca thanks for your answer . the disk seems to be regular one. So for
the new added disk
i have followed the
http://jamesthornton.com/redhat/linux/7.3/Reference-Guide/s1-filesystem-ext3-create.html
 and rebooted the server (edited the fstab ). But the disk doesnt seem
to be
mounted . So what can be the problem?

Regards

2009/9/10, Luca Berra <bluca@comedia.it>:
> On Thu, Sep 10, 2009 at 09:19:29AM +0300, pent 5971 wrote:
>>Hi,
>>Im new to this LVM stuff and still couldnt read and understand enough.
>>But i have a RHEL 5x box (which i didnt installed) and we have
>
> rhel uses lvm by default
>>phsically added a new disk which i have to create a file system to be
>>able to use it.  df -h command gives normal /var /data / partions, but
> first column of df output is the device, if it looks like /dev/sd?? or
> /dev/hd?? it is a normal partition
> if it looks like /dev/mapper/xxxxx-yyyy or /dev/xxxxx/yyyy it is
> probably an lvm
> also the commands vgs, lvs, and pvs help, i.e.
> root@Moskowskaya # vgs
>    VG   #PV #LV #SN Attr  VSize   VFree
>    vg00   1   7   0 wz--n 232.81G 10.81G
> root@Moskowskaya # pvs
>    PV         VG   Fmt  Attr PSize   PFree
>    /dev/sda   vg00 lvm2 a-   232.81G 10.81G
>
>
>>id like ask how can i understand if the first disk/sytem is created
>>with LVM , and if so (any other box can be so in the future) what is
>>best way to add the disk and crete the file system?
> woah, well, the simple answer is: there is no best way, you have to
> evaluate the pros and cons yourself.
>
> you could add the new disk to the existing volume group, which would
> give you the advantage of using avaliable space as a single pool and
> being able to create/extend existing logical volumes/filesystems using
> both disks. with the disadvantage of being more painful to recover in
> case one of the disks fails.
> you could create a new volume group using the new disk, or create a
> partition if you are more confortable, or even use the whole device for
> the new filesystem.
>
> L.
>
> --
> Luca Berra -- bluca@comedia.it
>          Communication Media & Services S.r.l.
>   /"\
>   \ /     ASCII RIBBON CAMPAIGN
>    X        AGAINST HTML MAIL
>   / \
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>

  reply	other threads:[~2009-09-10  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-10  6:19 [linux-lvm] Understanding if a disk is partioned with LVM or not pent 5971
2009-09-10  6:35 ` Luca Berra
2009-09-10  8:35   ` pent 5971 [this message]
2009-09-11 13:39     ` André Gillibert
2009-09-11 19:00       ` pent 5971

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=352f9c2a0909100135i64ac861awaf7089ea27c1b3b3@mail.gmail.com \
    --to=pent5971@gmail.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 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).