On 20 March 2011 04:09, Jonathan Matthews wrote:
> On 20 March 2011 02:24, Jim Green wrote:
>> http://www.gagme.com/greg/linux/raid-lvm.php
>
> That looks like an LVM1 article.
>
> Here's a readable one about LVM2:
> http://www.ibm.com/developerworks/library/l-lvm2/
>
> "With LVM2, there's no lim
On 20 March 2011 02:24, Jim Green wrote:
> http://www.gagme.com/greg/linux/raid-lvm.php
That looks like an LVM1 article.
Here's a readable one about LVM2:
http://www.ibm.com/developerworks/library/l-lvm2/
"With LVM2, there's no limit on the maximum numbers of extents per PV/LV."
Jonathan
--
J
Thank you for the excellent explanation!
http://www.gagme.com/greg/linux/raid-lvm.php
from this link I read
"The maximum number of physical extents is approximately 65k so take
your maximum volume size and divide it by 65k then round it to the
next nice round number. "
looks like I already have
On Sat, Mar 19, 2011 at 10:02:24PM -0400, Jim Green wrote:
> this is what I have from fdisk -l, I have lvm on /dev/md1, md1 is a
> raid10 array with 4x2T drives.
> Disk /dev/md1: 4000.5 GB, 4000525058048 bytes
> 2 heads, 4 sectors/track, 976690688 cylinders
> Units = cylinders of 8 * 512 = 4096 byt
this is what I have from fdisk -l, I have lvm on /dev/md1, md1 is a
raid10 array with 4x2T drives.
Disk /dev/md1: 4000.5 GB, 4000525058048 bytes
2 heads, 4 sectors/track, 976690688 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (mi
Wasn't sure where to raise this.
I used to run a sarge system with root on LVM volume on raid1. ( I
don't think raid is relevant here but mention it for completeness).
When I upgraded to etch the upgrade seemed to go OK but the system
wouldn't reboot. It appeared that the LVM volume wasn't
On Friday 29 December 2006 03:26, Pierguido wrote:
> lvextend -L+962G /dev/mapper/uservg-data
>
> It respond me:
>
> Volume group mapper doesn't exist
lvextend -L+962G uservg/data
--
Wesley J. Landaker <[EMAIL PROTECTED]>
OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2
pgpQ16
On Friday 29 December 2006 02:26, Pierguido wrote:
> I wanted to extend the data volume to the fill all the free space
> (962GB) but when i make:
>
> lvextend -L+962G /dev/mapper/uservg-data
>
> It respond me:
>
> Volume group mapper doesn't exist
>
> But:
>
> [EMAIL PROTECTED]:~# ls -l /dev/mapp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all.
I've installed etch on a file server with a raid array of 3,5 TB.
With the raid system i've created two virtual disk, sda for the OS and
sdb for the user datas shared via samba.
I've installed lvm for the second disk and i created two logical v
On Tue, Mar 07, 2006 at 06:45:06PM -0500, Bernard Fay wrote:
> vgcfgrestore lnxvg
> Incorrect metadata area header checksum
> Restored volume group lnxvg
It said it's restored, but it's still not working? Not good...
> Something else we could try.
Well, I don't know what. Try asking on an
On Tue, 2006-03-07 at 15:21 -0500, Andrew Cady wrote:
> On Sun, Mar 05, 2006 at 06:24:34PM -0500, Bernard Fay wrote:
> > For any LVM commands I run I receive the following message:
> >
> > Incorrect metadata area header checksum
> >
> > and/or
> >
> > Volume group mapper doesn't exist
>
> Eith
On Sun, Mar 05, 2006 at 06:24:34PM -0500, Bernard Fay wrote:
> For any LVM commands I run I receive the following message:
>
> Incorrect metadata area header checksum
>
> and/or
>
> Volume group mapper doesn't exist
Either your metadata has gotten messed up or you're using the wrong
device.
I
For any LVM commands I run I receive the following message:
Incorrect metadata area header checksum
and/or
Volume group mapper doesn't exist
Someone knows why and how it could be fixed? I run Debian etch with
kernel 2.6.12-1-386 and lvm2 version 2.01.04-5.
TIA,
Bernard
--
To UNSUBSCRIB
On Tue, 2004-05-11 at 01:49, Kirill Lapshin wrote:
> Stephan Seitz wrote:
> > But you need lvm2 for kernel 2.6.*. And I don't know if there is an
> > upgrade path to use the old lvm1 with lvm2. It should be
> > backwards-compatible, but it uses different config files.
> >
> > The lvm2 package does
Did you see the LVM 2 faq?
http://www.ibiblio.org/mdw/HOWTO/LVM-HOWTO/lvm2faq.html.
I learned the hard way, that it is not a good idea to convert your meta
data format from lvm1 to 2 till you can boot with at least 1 good kernel
with lvm2 support. It is always best to only change one thing at a
t
On Mon, May 10, 2004 at 08:49:43PM -0400, Kirill Lapshin wrote:
Actually it works automagically, just install lvm2 and you are fine. I
did it just this past weekend -- installed debian sarge from scratch
Here it didn't work. It was a woody installation, upgraded to testing.
lvm10 and lvm2 are ins
Stephan Seitz wrote:
But you need lvm2 for kernel 2.6.*. And I don't know if there is an
upgrade path to use the old lvm1 with lvm2. It should be
backwards-compatible, but it uses different config files.
The lvm2 package doesn't contain any docs for an upgrade (or I didn't
find them).
Actually it w
On Mon, May 10, 2004 at 02:50:29PM +0100, Andrew Ingram wrote:
I did update the lvm-common and lvm10 packages to the latest (I'm
running Sid btw). But this produced the same thing (no mounted lvm),
But you need lvm2 for kernel 2.6.*. And I don't know if there is an
upgrade path to use the old lvm1
On Mon, 2004-05-10 at 11:38, David Cannings wrote:
> On Monday 10 May 2004 10:55, Andrew Ingram wrote:
> > /dev/mapper/control: open failed: No such device
> > Is device-mapper driver missing from kernel?
> > Warning: '/proc/partitions' does not match '/dev' directory structure.
> > Name change
On Monday 10 May 2004 10:55, Andrew Ingram wrote:
> /dev/mapper/control: open failed: No such device
> Is device-mapper driver missing from kernel?
> Warning: '/proc/partitions' does not match '/dev' directory structure.
> Name change: '/dev/lvma' -> '/dev/vg00/mythtvlv'
> Added 2.6.5
> Added 2
I have a box which runs 2.4.22 just fine but wanted to try out 2.6.5 as
some of the extra features from 2.6 would be very welcome. The box has
several "normal" partitions (ReiserFS) and one partition that is
configured with LVM (for future expansion, at the moment it's just one
partition on the mai
21 matches
Mail list logo