On Oct 14, 2008, at 10:36 PM, Craig White [EMAIL PROTECTED]
wrote:
I just got a new server with a Dell MD-1000 SAS unit and 6-750
gigabyte
drives which are now initializing in RAID 10 which will give me just
about 2 terabytes.
I vaguely recall reading that fdisk wasn't suitable for
Just pvcreate the whole disk and forgo partitioning it. Then create a
vg out of it and start creating lvs.
Hey Ross,
I thought it was best practice to create an LVM partition such that the
disk could be recognizable under all circumstances such as if the volume
was moved? Is that not really
On Wed, 2008-10-15 at 09:47 -0400, Ross Walker wrote:
On Oct 14, 2008, at 10:36 PM, Craig White [EMAIL PROTECTED]
wrote:
I just got a new server with a Dell MD-1000 SAS unit and 6-750
gigabyte
drives which are now initializing in RAID 10 which will give me just
about 2 terabytes.
On Wed, Oct 15, 2008 at 09:52:03AM -0700, Craig White wrote:
I have done the pgcreate and tested lvcreate but wonder about
'setphysicalextentsize' because in the man page, it states, The default
of 4 MB leads to a maximum logical volume size of around 256GB which
makes me think that if I want
On Wed, 2008-10-15 at 13:34 -0400, Stephen Harris wrote:
On Wed, Oct 15, 2008 at 09:52:03AM -0700, Craig White wrote:
I have done the pgcreate and tested lvcreate but wonder about
'setphysicalextentsize' because in the man page, it states, The default
of 4 MB leads to a maximum logical
I'm not really sure what the difference would
be having the physical extent size as 64 MB versions 4 MB.
It's the smallest allocatable size of any PV you can give to an LV.
Think of it like Allocation Unit Size. Also as pointed out above some
limitations arise in different versions of LVM. RH
On Wed, Oct 15, 2008 at 11:13:08AM -0700, Craig White wrote:
I did run into a snag that I don't fully understand while trying to make
the filesystem though...
# mke2fs -v -j -l 2TbVol /dev/VolGroup10/2TbVol
Were you trying to specify a label? If so, use the -L option, not -l
Were you
On Wed, 2008-10-15 at 14:34 -0400, Stephen Harris wrote:
On Wed, Oct 15, 2008 at 11:13:08AM -0700, Craig White wrote:
I did run into a snag that I don't fully understand while trying to make
the filesystem though...
# mke2fs -v -j -l 2TbVol /dev/VolGroup10/2TbVol
Were you trying to
Just pvcreate the whole disk and forgo partitioning it. Then create a
vg out of it and start creating lvs.
Hey Ross,
I thought it was best practice to create an LVM partition
such that the
disk could be recognizable under all circumstances such as if
the volume
was moved? Is that not
On Oct 15, 2008, at 10:15 AM, Joseph L. Casale [EMAIL PROTECTED]
wrote:
Just pvcreate the whole disk and forgo partitioning it. Then create a
vg out of it and start creating lvs.
Hey Ross,
I thought it was best practice to create an LVM partition such that
the
disk could be
I vaguely recall reading that fdisk wasn't suitable for partitioning and
wonder if I shouldn't be using partd instead. I am also wondering if I
should use lvm or just mkfs to create the filesystem. Anyone have
suggestions before I blunder in?
fdisk can't do GPT which is what you need for
11 matches
Mail list logo
