* [linux-lvm] Problems with LVM
2003-07-11 18:28 [linux-lvm] Re: Safely removing a phantom disc-wide PV Chip McArtor
@ 2003-07-11 19:02 ` Petro
2003-07-13 5:14 ` Heinz J . Mauelshagen
0 siblings, 1 reply; 11+ messages in thread
From: Petro @ 2003-07-11 19:02 UTC (permalink / raw)
To: linux-lvm
Hello again.
I'm having a problem with LVM, and I'm really, really hoping you won't
tell me it's because of:
# CONFIG_NOHIGHMEM is not set
CONFIG_HIGHMEM4G=y
# CONFIG_HIGHMEM64G is not set
CONFIG_HIGHMEM=y
CONFIG_HIGHIO=y
(linux kernel 2.4.21, lvm 1.0.7 stuff installed)
I've got 8 boxes with 4 gig of memory, and 6 200 gig drives in a raid 0
setup, and I need to use LVM+Snapshots.
I can setup and create a 1.09T logical volume, but when I go to create a
snaphot, I get:
lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/vg0/test"
lvcreate -- ERROR "Cannot allocate memory" creating VGDA for "/dev/vg0/test" in kernel
Now, in reading past posts there is some talk of how having "high
memory" turned on will cause problems with snapshots.
The problem is that on these machines I *need* 4 gig of memory, and I
*need* snapshots.
Help?
--- Physical volume ---
PV Name /dev/sda
VG Name vg0
PV Size 1.09 TB [2344319232 secs] / NOT usable 32.31 MB [LVM: 267 KB]
PV# 1
PV Status available
Allocatable yes
Cur LV 1
PE Size (KByte) 32768
Total PE 35770
Free PE 570
Allocated PE 35200
PV UUID LyEPH1-pq2I-D022-v5c9-98rp-n7Ff-4LnNKL
--- Volume group ---
VG Name vg0
VG Access read/write
VG Status available/resizable
VG # 0
MAX LV 256
Cur LV 1
Open LV 1
MAX LV Size 2 TB
Max PV 256
Cur PV 1
Act PV 1
VG Size 1.09 TB
PE Size 32 MB
Total PE 35770
Alloc PE / Size 36032 / 1.10 TB
Free PE / Size 4294967034 / 131071.99 TB
VG UUID KciSkB-xbr8-22RM-zmke-6A69-6BEM-xLWMzv
--- Logical volume ---
LV Name /dev/vg0/lv0
VG Name vg0
LV Write Access read/write
LV Status available
LV # 1
# open 1
LV Size 1.07 TB
Current LE 35200
Allocated LE 35200
Allocation next free
Read ahead sectors 1024
Block device 58:0
procs memory swap io system cpu
r b w swpd free buff cache si so bi bo in cs us sy id
0 0 0 0 3949704 1648 26104 0 0 3 2 27 5 0 0 100
--
"On two occasions, I have been asked [by members of Parliament], 'Pray,
Mr. Babbage, if you put into the machine wrong figures, will the right
answers come out?' I am not able to rightly apprehend the kind of confusion
of ideas that could provoke such a question." -- Charles Babbage
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] Problems with LVM
2003-07-11 19:02 ` [linux-lvm] Problems with LVM Petro
@ 2003-07-13 5:14 ` Heinz J . Mauelshagen
2003-07-13 13:29 ` Petro
0 siblings, 1 reply; 11+ messages in thread
From: Heinz J . Mauelshagen @ 2003-07-13 5:14 UTC (permalink / raw)
To: linux-lvm
Petro,
what's the lvcreate command line ?
(highmem may cause problems if you use the snapsho9t, creation should
work fine)
Regards,
Heinz -- The LVM Guy --
On Fri, Jul 11, 2003 at 05:01:27PM -0700, Petro wrote:
> Hello again.
>
> I'm having a problem with LVM, and I'm really, really hoping you won't
> tell me it's because of:
>
> # CONFIG_NOHIGHMEM is not set
> CONFIG_HIGHMEM4G=y
> # CONFIG_HIGHMEM64G is not set
> CONFIG_HIGHMEM=y
> CONFIG_HIGHIO=y
>
> (linux kernel 2.4.21, lvm 1.0.7 stuff installed)
>
> I've got 8 boxes with 4 gig of memory, and 6 200 gig drives in a raid 0
> setup, and I need to use LVM+Snapshots.
>
> I can setup and create a 1.09T logical volume, but when I go to create a
> snaphot, I get:
>
> lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/vg0/test"
> lvcreate -- ERROR "Cannot allocate memory" creating VGDA for "/dev/vg0/test" in kernel
>
> Now, in reading past posts there is some talk of how having "high
> memory" turned on will cause problems with snapshots.
>
> The problem is that on these machines I *need* 4 gig of memory, and I
> *need* snapshots.
>
> Help?
>
>
> --- Physical volume ---
> PV Name /dev/sda
> VG Name vg0
> PV Size 1.09 TB [2344319232 secs] / NOT usable 32.31 MB [LVM: 267 KB]
> PV# 1
> PV Status available
> Allocatable yes
> Cur LV 1
> PE Size (KByte) 32768
> Total PE 35770
> Free PE 570
> Allocated PE 35200
> PV UUID LyEPH1-pq2I-D022-v5c9-98rp-n7Ff-4LnNKL
>
> --- Volume group ---
> VG Name vg0
> VG Access read/write
> VG Status available/resizable
> VG # 0
> MAX LV 256
> Cur LV 1
> Open LV 1
> MAX LV Size 2 TB
> Max PV 256
> Cur PV 1
> Act PV 1
> VG Size 1.09 TB
> PE Size 32 MB
> Total PE 35770
> Alloc PE / Size 36032 / 1.10 TB
> Free PE / Size 4294967034 / 131071.99 TB
> VG UUID KciSkB-xbr8-22RM-zmke-6A69-6BEM-xLWMzv
>
> --- Logical volume ---
> LV Name /dev/vg0/lv0
> VG Name vg0
> LV Write Access read/write
> LV Status available
> LV # 1
> # open 1
> LV Size 1.07 TB
> Current LE 35200
> Allocated LE 35200
> Allocation next free
> Read ahead sectors 1024
> Block device 58:0
>
>
> procs memory swap io system cpu
> r b w swpd free buff cache si so bi bo in cs us sy id
> 0 0 0 0 3949704 1648 26104 0 0 3 2 27 5 0 0 100
>
>
> --
> "On two occasions, I have been asked [by members of Parliament], 'Pray,
> Mr. Babbage, if you put into the machine wrong figures, will the right
> answers come out?' I am not able to rightly apprehend the kind of confusion
> of ideas that could provoke such a question." -- Charles Babbage
>
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] Problems with LVM
2003-07-13 5:14 ` Heinz J . Mauelshagen
@ 2003-07-13 13:29 ` Petro
2003-07-13 15:26 ` Heinz J . Mauelshagen
0 siblings, 1 reply; 11+ messages in thread
From: Petro @ 2003-07-13 13:29 UTC (permalink / raw)
To: linux-lvm
On Sun, Jul 13, 2003 at 12:11:51PM +0200, Heinz J . Mauelshagen wrote:
> Petro,
> what's the lvcreate command line ?
lvcreate -L10G -n snap000 -s /dev/vg0
> (highmem may cause problems if you use the snapsho9t, creation should
> work fine)
Is this highmem problem across all 2.4 kernels, or just 2.4.19+? The
first report I've seen of it is with a 2.4.19 kernel.
>
> Regards,
> Heinz -- The LVM Guy --
>
> On Fri, Jul 11, 2003 at 05:01:27PM -0700, Petro wrote:
> > Hello again.
> >
> > I'm having a problem with LVM, and I'm really, really hoping you won't
> > tell me it's because of:
> >
> > # CONFIG_NOHIGHMEM is not set
> > CONFIG_HIGHMEM4G=y
> > # CONFIG_HIGHMEM64G is not set
> > CONFIG_HIGHMEM=y
> > CONFIG_HIGHIO=y
> >
> > (linux kernel 2.4.21, lvm 1.0.7 stuff installed)
> >
> > I've got 8 boxes with 4 gig of memory, and 6 200 gig drives in a raid 0
> > setup, and I need to use LVM+Snapshots.
> >
> > I can setup and create a 1.09T logical volume, but when I go to create a
> > snaphot, I get:
> >
> > lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/vg0/test"
> > lvcreate -- ERROR "Cannot allocate memory" creating VGDA for "/dev/vg0/test" in kernel
> >
> > Now, in reading past posts there is some talk of how having "high
> > memory" turned on will cause problems with snapshots.
> >
> > The problem is that on these machines I *need* 4 gig of memory, and I
> > *need* snapshots.
> >
> > Help?
> >
> >
> > --- Physical volume ---
> > PV Name /dev/sda
> > VG Name vg0
> > PV Size 1.09 TB [2344319232 secs] / NOT usable 32.31 MB [LVM: 267 KB]
> > PV# 1
> > PV Status available
> > Allocatable yes
> > Cur LV 1
> > PE Size (KByte) 32768
> > Total PE 35770
> > Free PE 570
> > Allocated PE 35200
> > PV UUID LyEPH1-pq2I-D022-v5c9-98rp-n7Ff-4LnNKL
> >
> > --- Volume group ---
> > VG Name vg0
> > VG Access read/write
> > VG Status available/resizable
> > VG # 0
> > MAX LV 256
> > Cur LV 1
> > Open LV 1
> > MAX LV Size 2 TB
> > Max PV 256
> > Cur PV 1
> > Act PV 1
> > VG Size 1.09 TB
> > PE Size 32 MB
> > Total PE 35770
> > Alloc PE / Size 36032 / 1.10 TB
> > Free PE / Size 4294967034 / 131071.99 TB
> > VG UUID KciSkB-xbr8-22RM-zmke-6A69-6BEM-xLWMzv
> >
> > --- Logical volume ---
> > LV Name /dev/vg0/lv0
> > VG Name vg0
> > LV Write Access read/write
> > LV Status available
> > LV # 1
> > # open 1
> > LV Size 1.07 TB
> > Current LE 35200
> > Allocated LE 35200
> > Allocation next free
> > Read ahead sectors 1024
> > Block device 58:0
> >
> >
> > procs memory swap io system cpu
> > r b w swpd free buff cache si so bi bo in cs us sy id
> > 0 0 0 0 3949704 1648 26104 0 0 3 2 27 5 0 0 100
> >
> >
> > --
> > "On two occasions, I have been asked [by members of Parliament], 'Pray,
> > Mr. Babbage, if you put into the machine wrong figures, will the right
> > answers come out?' I am not able to rightly apprehend the kind of confusion
> > of ideas that could provoke such a question." -- Charles Babbage
> >
> > _______________________________________________
> > 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
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> _______________________________________________
> 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/
--
"On two occasions, I have been asked [by members of Parliament], 'Pray,
Mr. Babbage, if you put into the machine wrong figures, will the right
answers come out?' I am not able to rightly apprehend the kind of confusion
of ideas that could provoke such a question." -- Charles Babbage
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] Problems with LVM
2003-07-13 13:29 ` Petro
@ 2003-07-13 15:26 ` Heinz J . Mauelshagen
2003-07-13 19:35 ` Petro
0 siblings, 1 reply; 11+ messages in thread
From: Heinz J . Mauelshagen @ 2003-07-13 15:26 UTC (permalink / raw)
To: linux-lvm
On Sun, Jul 13, 2003 at 11:27:43AM -0700, Petro wrote:
> On Sun, Jul 13, 2003 at 12:11:51PM +0200, Heinz J . Mauelshagen wrote:
> > Petro,
> > what's the lvcreate command line ?
>
> lvcreate -L10G -n snap000 -s /dev/vg0
Looks like another vmalloc bug :(
Kernel memory for snapshot exception tables gets allocated with vmalloc()
which shouldn't fail (presumably there's enough memory free,
which I assume in your case).
>
> > (highmem may cause problems if you use the snapsho9t, creation should
> > work fine)
>
> Is this highmem problem across all 2.4 kernels, or just 2.4.19+? The
> first report I've seen of it is with a 2.4.19 kernel.
Didn't retest with kernel 2.4.21 yet.
The ones before had it AFAIK.
Regards,
Heinz -- The LVM Guy --
>
> >
> > Regards,
> > Heinz -- The LVM Guy --
> >
> > On Fri, Jul 11, 2003 at 05:01:27PM -0700, Petro wrote:
> > > Hello again.
> > >
> > > I'm having a problem with LVM, and I'm really, really hoping you won't
> > > tell me it's because of:
> > >
> > > # CONFIG_NOHIGHMEM is not set
> > > CONFIG_HIGHMEM4G=y
> > > # CONFIG_HIGHMEM64G is not set
> > > CONFIG_HIGHMEM=y
> > > CONFIG_HIGHIO=y
> > >
> > > (linux kernel 2.4.21, lvm 1.0.7 stuff installed)
> > >
> > > I've got 8 boxes with 4 gig of memory, and 6 200 gig drives in a raid 0
> > > setup, and I need to use LVM+Snapshots.
> > >
> > > I can setup and create a 1.09T logical volume, but when I go to create a
> > > snaphot, I get:
> > >
> > > lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/vg0/test"
> > > lvcreate -- ERROR "Cannot allocate memory" creating VGDA for "/dev/vg0/test" in kernel
> > >
> > > Now, in reading past posts there is some talk of how having "high
> > > memory" turned on will cause problems with snapshots.
> > >
> > > The problem is that on these machines I *need* 4 gig of memory, and I
> > > *need* snapshots.
> > >
> > > Help?
> > >
> > >
> > > --- Physical volume ---
> > > PV Name /dev/sda
> > > VG Name vg0
> > > PV Size 1.09 TB [2344319232 secs] / NOT usable 32.31 MB [LVM: 267 KB]
> > > PV# 1
> > > PV Status available
> > > Allocatable yes
> > > Cur LV 1
> > > PE Size (KByte) 32768
> > > Total PE 35770
> > > Free PE 570
> > > Allocated PE 35200
> > > PV UUID LyEPH1-pq2I-D022-v5c9-98rp-n7Ff-4LnNKL
> > >
> > > --- Volume group ---
> > > VG Name vg0
> > > VG Access read/write
> > > VG Status available/resizable
> > > VG # 0
> > > MAX LV 256
> > > Cur LV 1
> > > Open LV 1
> > > MAX LV Size 2 TB
> > > Max PV 256
> > > Cur PV 1
> > > Act PV 1
> > > VG Size 1.09 TB
> > > PE Size 32 MB
> > > Total PE 35770
> > > Alloc PE / Size 36032 / 1.10 TB
> > > Free PE / Size 4294967034 / 131071.99 TB
> > > VG UUID KciSkB-xbr8-22RM-zmke-6A69-6BEM-xLWMzv
> > >
> > > --- Logical volume ---
> > > LV Name /dev/vg0/lv0
> > > VG Name vg0
> > > LV Write Access read/write
> > > LV Status available
> > > LV # 1
> > > # open 1
> > > LV Size 1.07 TB
> > > Current LE 35200
> > > Allocated LE 35200
> > > Allocation next free
> > > Read ahead sectors 1024
> > > Block device 58:0
> > >
> > >
> > > procs memory swap io system cpu
> > > r b w swpd free buff cache si so bi bo in cs us sy id
> > > 0 0 0 0 3949704 1648 26104 0 0 3 2 27 5 0 0 100
> > >
> > >
> > > --
> > > "On two occasions, I have been asked [by members of Parliament], 'Pray,
> > > Mr. Babbage, if you put into the machine wrong figures, will the right
> > > answers come out?' I am not able to rightly apprehend the kind of confusion
> > > of ideas that could provoke such a question." -- Charles Babbage
> > >
> > > _______________________________________________
> > > 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 ***
> >
> > _______________________________________________
> > 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/
>
> --
> "On two occasions, I have been asked [by members of Parliament], 'Pray,
> Mr. Babbage, if you put into the machine wrong figures, will the right
> answers come out?' I am not able to rightly apprehend the kind of confusion
> of ideas that could provoke such a question." -- Charles Babbage
>
> _______________________________________________
> 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] Problems with LVM
2003-07-13 15:26 ` Heinz J . Mauelshagen
@ 2003-07-13 19:35 ` Petro
2003-07-13 22:43 ` Petro
2003-07-15 13:58 ` Heinz J . Mauelshagen
0 siblings, 2 replies; 11+ messages in thread
From: Petro @ 2003-07-13 19:35 UTC (permalink / raw)
To: linux-lvm
On Sun, Jul 13, 2003 at 10:24:15PM +0200, Heinz J . Mauelshagen wrote:
> On Sun, Jul 13, 2003 at 11:27:43AM -0700, Petro wrote:
> > On Sun, Jul 13, 2003 at 12:11:51PM +0200, Heinz J . Mauelshagen wrote:
> > > Petro,
> > > what's the lvcreate command line ?
> >
> > lvcreate -L10G -n snap000 -s /dev/vg0
> Looks like another vmalloc bug :(
You mean like this one:
Jul 13 13:11:55 back03-gig kernel: kernel BUG at vmalloc.c:236!
Jul 13 13:11:55 back03-gig kernel: invalid operand: 0000
Jul 13 13:11:55 back03-gig kernel: CPU: 2
Jul 13 13:11:55 back03-gig kernel: EIP: 0010:[__vmalloc+53/512]
Not tainted
> Kernel memory for snapshot exception tables gets allocated with vmalloc()
> which shouldn't fail (presumably there's enough memory free,
> which I assume in your case).
Freshly rebooted machine with 4 gig of physical memory, and nothing else
running.
> > > (highmem may cause problems if you use the snapsho9t, creation should
> > > work fine)
> > Is this highmem problem across all 2.4 kernels, or just 2.4.19+? The
> > first report I've seen of it is with a 2.4.19 kernel.
> Didn't retest with kernel 2.4.21 yet.
> The ones before had it AFAIK.
Starting when? the dawn of time?
Also, would switching to LVM2 sidestep this issue?
> Regards,
> Heinz -- The LVM Guy --
>
> >
> > >
> > > Regards,
> > > Heinz -- The LVM Guy --
> > >
> > > On Fri, Jul 11, 2003 at 05:01:27PM -0700, Petro wrote:
> > > > Hello again.
> > > >
> > > > I'm having a problem with LVM, and I'm really, really hoping you won't
> > > > tell me it's because of:
> > > >
> > > > # CONFIG_NOHIGHMEM is not set
> > > > CONFIG_HIGHMEM4G=y
> > > > # CONFIG_HIGHMEM64G is not set
> > > > CONFIG_HIGHMEM=y
> > > > CONFIG_HIGHIO=y
> > > >
> > > > (linux kernel 2.4.21, lvm 1.0.7 stuff installed)
> > > >
> > > > I've got 8 boxes with 4 gig of memory, and 6 200 gig drives in a raid 0
> > > > setup, and I need to use LVM+Snapshots.
> > > >
> > > > I can setup and create a 1.09T logical volume, but when I go to create a
> > > > snaphot, I get:
> > > >
> > > > lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/vg0/test"
> > > > lvcreate -- ERROR "Cannot allocate memory" creating VGDA for "/dev/vg0/test" in kernel
> > > >
> > > > Now, in reading past posts there is some talk of how having "high
> > > > memory" turned on will cause problems with snapshots.
> > > >
> > > > The problem is that on these machines I *need* 4 gig of memory, and I
> > > > *need* snapshots.
> > > >
> > > > Help?
> > > >
> > > >
> > > > --- Physical volume ---
> > > > PV Name /dev/sda
> > > > VG Name vg0
> > > > PV Size 1.09 TB [2344319232 secs] / NOT usable 32.31 MB [LVM: 267 KB]
> > > > PV# 1
> > > > PV Status available
> > > > Allocatable yes
> > > > Cur LV 1
> > > > PE Size (KByte) 32768
> > > > Total PE 35770
> > > > Free PE 570
> > > > Allocated PE 35200
> > > > PV UUID LyEPH1-pq2I-D022-v5c9-98rp-n7Ff-4LnNKL
> > > >
> > > > --- Volume group ---
> > > > VG Name vg0
> > > > VG Access read/write
> > > > VG Status available/resizable
> > > > VG # 0
> > > > MAX LV 256
> > > > Cur LV 1
> > > > Open LV 1
> > > > MAX LV Size 2 TB
> > > > Max PV 256
> > > > Cur PV 1
> > > > Act PV 1
> > > > VG Size 1.09 TB
> > > > PE Size 32 MB
> > > > Total PE 35770
> > > > Alloc PE / Size 36032 / 1.10 TB
> > > > Free PE / Size 4294967034 / 131071.99 TB
> > > > VG UUID KciSkB-xbr8-22RM-zmke-6A69-6BEM-xLWMzv
> > > >
> > > > --- Logical volume ---
> > > > LV Name /dev/vg0/lv0
> > > > VG Name vg0
> > > > LV Write Access read/write
> > > > LV Status available
> > > > LV # 1
> > > > # open 1
> > > > LV Size 1.07 TB
> > > > Current LE 35200
> > > > Allocated LE 35200
> > > > Allocation next free
> > > > Read ahead sectors 1024
> > > > Block device 58:0
> > > >
> > > >
> > > > procs memory swap io system cpu
> > > > r b w swpd free buff cache si so bi bo in cs us sy id
> > > > 0 0 0 0 3949704 1648 26104 0 0 3 2 27 5 0 0 100
> > > >
> > > >
> > > > --
> > > > "On two occasions, I have been asked [by members of Parliament], 'Pray,
> > > > Mr. Babbage, if you put into the machine wrong figures, will the right
> > > > answers come out?' I am not able to rightly apprehend the kind of confusion
> > > > of ideas that could provoke such a question." -- Charles Babbage
> > > >
> > > > _______________________________________________
> > > > 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 ***
> > >
> > > _______________________________________________
> > > 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/
> >
> > --
> > "On two occasions, I have been asked [by members of Parliament], 'Pray,
> > Mr. Babbage, if you put into the machine wrong figures, will the right
> > answers come out?' I am not able to rightly apprehend the kind of confusion
> > of ideas that could provoke such a question." -- Charles Babbage
> >
> > _______________________________________________
> > 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
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> _______________________________________________
> 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/
--
"On two occasions, I have been asked [by members of Parliament], 'Pray,
Mr. Babbage, if you put into the machine wrong figures, will the right
answers come out?' I am not able to rightly apprehend the kind of confusion
of ideas that could provoke such a question." -- Charles Babbage
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] Problems with LVM
2003-07-13 19:35 ` Petro
@ 2003-07-13 22:43 ` Petro
2003-07-15 13:58 ` Heinz J . Mauelshagen
1 sibling, 0 replies; 11+ messages in thread
From: Petro @ 2003-07-13 22:43 UTC (permalink / raw)
To: linux-lvm
On Sun, Jul 13, 2003 at 05:34:08PM -0700, Petro wrote:
> On Sun, Jul 13, 2003 at 10:24:15PM +0200, Heinz J . Mauelshagen wrote:
> > On Sun, Jul 13, 2003 at 11:27:43AM -0700, Petro wrote:
> > > On Sun, Jul 13, 2003 at 12:11:51PM +0200, Heinz J . Mauelshagen wrote:
> > > > Petro,
> > > > what's the lvcreate command line ?
> > >
> > > lvcreate -L10G -n snap000 -s /dev/vg0
> > Looks like another vmalloc bug :(
> You mean like this one:
> Jul 13 13:11:55 back03-gig kernel: kernel BUG at vmalloc.c:236!
> Jul 13 13:11:55 back03-gig kernel: invalid operand: 0000
> Jul 13 13:11:55 back03-gig kernel: CPU: 2
> Jul 13 13:11:55 back03-gig kernel: EIP: 0010:[__vmalloc+53/512]
> Not tainted
Note that this is on the 2.4.18 kernel, not the 2.4.21 kernel.
> > Kernel memory for snapshot exception tables gets allocated with vmalloc()
> > which shouldn't fail (presumably there's enough memory free,
> > which I assume in your case).
>
> Freshly rebooted machine with 4 gig of physical memory, and nothing else
> running.
>
> > > > (highmem may cause problems if you use the snapsho9t, creation should
> > > > work fine)
> > > Is this highmem problem across all 2.4 kernels, or just 2.4.19+? The
> > > first report I've seen of it is with a 2.4.19 kernel.
> > Didn't retest with kernel 2.4.21 yet.
> > The ones before had it AFAIK.
>
> Starting when? the dawn of time?
>
> Also, would switching to LVM2 sidestep this issue?
>
> > Regards,
> > Heinz -- The LVM Guy --
> >
> > >
> > > >
> > > > Regards,
> > > > Heinz -- The LVM Guy --
> > > >
> > > > On Fri, Jul 11, 2003 at 05:01:27PM -0700, Petro wrote:
> > > > > Hello again.
> > > > >
> > > > > I'm having a problem with LVM, and I'm really, really hoping you won't
> > > > > tell me it's because of:
> > > > >
> > > > > # CONFIG_NOHIGHMEM is not set
> > > > > CONFIG_HIGHMEM4G=y
> > > > > # CONFIG_HIGHMEM64G is not set
> > > > > CONFIG_HIGHMEM=y
> > > > > CONFIG_HIGHIO=y
> > > > >
> > > > > (linux kernel 2.4.21, lvm 1.0.7 stuff installed)
> > > > >
> > > > > I've got 8 boxes with 4 gig of memory, and 6 200 gig drives in a raid 0
> > > > > setup, and I need to use LVM+Snapshots.
> > > > >
> > > > > I can setup and create a 1.09T logical volume, but when I go to create a
> > > > > snaphot, I get:
> > > > >
> > > > > lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/vg0/test"
> > > > > lvcreate -- ERROR "Cannot allocate memory" creating VGDA for "/dev/vg0/test" in kernel
> > > > >
> > > > > Now, in reading past posts there is some talk of how having "high
> > > > > memory" turned on will cause problems with snapshots.
> > > > >
> > > > > The problem is that on these machines I *need* 4 gig of memory, and I
> > > > > *need* snapshots.
> > > > >
> > > > > Help?
> > > > >
> > > > >
> > > > > --- Physical volume ---
> > > > > PV Name /dev/sda
> > > > > VG Name vg0
> > > > > PV Size 1.09 TB [2344319232 secs] / NOT usable 32.31 MB [LVM: 267 KB]
> > > > > PV# 1
> > > > > PV Status available
> > > > > Allocatable yes
> > > > > Cur LV 1
> > > > > PE Size (KByte) 32768
> > > > > Total PE 35770
> > > > > Free PE 570
> > > > > Allocated PE 35200
> > > > > PV UUID LyEPH1-pq2I-D022-v5c9-98rp-n7Ff-4LnNKL
> > > > >
> > > > > --- Volume group ---
> > > > > VG Name vg0
> > > > > VG Access read/write
> > > > > VG Status available/resizable
> > > > > VG # 0
> > > > > MAX LV 256
> > > > > Cur LV 1
> > > > > Open LV 1
> > > > > MAX LV Size 2 TB
> > > > > Max PV 256
> > > > > Cur PV 1
> > > > > Act PV 1
> > > > > VG Size 1.09 TB
> > > > > PE Size 32 MB
> > > > > Total PE 35770
> > > > > Alloc PE / Size 36032 / 1.10 TB
> > > > > Free PE / Size 4294967034 / 131071.99 TB
> > > > > VG UUID KciSkB-xbr8-22RM-zmke-6A69-6BEM-xLWMzv
> > > > >
> > > > > --- Logical volume ---
> > > > > LV Name /dev/vg0/lv0
> > > > > VG Name vg0
> > > > > LV Write Access read/write
> > > > > LV Status available
> > > > > LV # 1
> > > > > # open 1
> > > > > LV Size 1.07 TB
> > > > > Current LE 35200
> > > > > Allocated LE 35200
> > > > > Allocation next free
> > > > > Read ahead sectors 1024
> > > > > Block device 58:0
> > > > >
> > > > >
> > > > > procs memory swap io system cpu
> > > > > r b w swpd free buff cache si so bi bo in cs us sy id
> > > > > 0 0 0 0 3949704 1648 26104 0 0 3 2 27 5 0 0 100
> > > > >
> > > > >
> > > > > --
> > > > > "On two occasions, I have been asked [by members of Parliament], 'Pray,
> > > > > Mr. Babbage, if you put into the machine wrong figures, will the right
> > > > > answers come out?' I am not able to rightly apprehend the kind of confusion
> > > > > of ideas that could provoke such a question." -- Charles Babbage
> > > > >
> > > > > _______________________________________________
> > > > > 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 ***
> > > >
> > > > _______________________________________________
> > > > 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/
> > >
> > > --
> > > "On two occasions, I have been asked [by members of Parliament], 'Pray,
> > > Mr. Babbage, if you put into the machine wrong figures, will the right
> > > answers come out?' I am not able to rightly apprehend the kind of confusion
> > > of ideas that could provoke such a question." -- Charles Babbage
> > >
> > > _______________________________________________
> > > 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
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
> > _______________________________________________
> > 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/
>
> --
> "On two occasions, I have been asked [by members of Parliament], 'Pray,
> Mr. Babbage, if you put into the machine wrong figures, will the right
> answers come out?' I am not able to rightly apprehend the kind of confusion
> of ideas that could provoke such a question." -- Charles Babbage
>
> _______________________________________________
> 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/
--
"On two occasions, I have been asked [by members of Parliament], 'Pray,
Mr. Babbage, if you put into the machine wrong figures, will the right
answers come out?' I am not able to rightly apprehend the kind of confusion
of ideas that could provoke such a question." -- Charles Babbage
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] Problems with LVM
2003-07-13 19:35 ` Petro
2003-07-13 22:43 ` Petro
@ 2003-07-15 13:58 ` Heinz J . Mauelshagen
2003-07-15 20:09 ` Petro
1 sibling, 1 reply; 11+ messages in thread
From: Heinz J . Mauelshagen @ 2003-07-15 13:58 UTC (permalink / raw)
To: linux-lvm
On Sun, Jul 13, 2003 at 05:34:08PM -0700, Petro wrote:
> On Sun, Jul 13, 2003 at 10:24:15PM +0200, Heinz J . Mauelshagen wrote:
> > On Sun, Jul 13, 2003 at 11:27:43AM -0700, Petro wrote:
> > > On Sun, Jul 13, 2003 at 12:11:51PM +0200, Heinz J . Mauelshagen wrote:
> > > > Petro,
> > > > what's the lvcreate command line ?
> > >
> > > lvcreate -L10G -n snap000 -s /dev/vg0
> > Looks like another vmalloc bug :(
Yes.
> Jul 13 13:11:55 back03-gig kernel: kernel BUG at vmalloc.c:236!
> Jul 13 13:11:55 back03-gig kernel: invalid operand: 0000
> Jul 13 13:11:55 back03-gig kernel: CPU: 2
> Jul 13 13:11:55 back03-gig kernel: EIP: 0010:[__vmalloc+53/512]
> Not tainted
>
> > Kernel memory for snapshot exception tables gets allocated with vmalloc()
> > which shouldn't fail (presumably there's enough memory free,
> > which I assume in your case).
>
> Freshly rebooted machine with 4 gig of physical memory, and nothing else
> running.
Which should happilly work in that case.
>
> > > > (highmem may cause problems if you use the snapsho9t, creation should
> > > > work fine)
> > > Is this highmem problem across all 2.4 kernels, or just 2.4.19+? The
> > > first report I've seen of it is with a 2.4.19 kernel.
> > Didn't retest with kernel 2.4.21 yet.
> > The ones before had it AFAIK.
>
> Starting when? the dawn of time?
:-)
We realized it in 2.4.19 for the first time but you prove that it was in 2.4.18
as well.
Anyone ?
>
> Also, would switching to LVM2 sidestep this issue?
Not that we can tell because it's a general vm problem.
Regards,
Heinz -- The LVM Guy --
> > > >
> > > > On Fri, Jul 11, 2003 at 05:01:27PM -0700, Petro wrote:
> > > > > Hello again.
> > > > >
> > > > > I'm having a problem with LVM, and I'm really, really hoping you won't
> > > > > tell me it's because of:
> > > > >
> > > > > # CONFIG_NOHIGHMEM is not set
> > > > > CONFIG_HIGHMEM4G=y
> > > > > # CONFIG_HIGHMEM64G is not set
> > > > > CONFIG_HIGHMEM=y
> > > > > CONFIG_HIGHIO=y
> > > > >
> > > > > (linux kernel 2.4.21, lvm 1.0.7 stuff installed)
> > > > >
> > > > > I've got 8 boxes with 4 gig of memory, and 6 200 gig drives in a raid 0
> > > > > setup, and I need to use LVM+Snapshots.
> > > > >
> > > > > I can setup and create a 1.09T logical volume, but when I go to create a
> > > > > snaphot, I get:
> > > > >
> > > > > lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/vg0/test"
> > > > > lvcreate -- ERROR "Cannot allocate memory" creating VGDA for "/dev/vg0/test" in kernel
> > > > >
> > > > > Now, in reading past posts there is some talk of how having "high
> > > > > memory" turned on will cause problems with snapshots.
> > > > >
> > > > > The problem is that on these machines I *need* 4 gig of memory, and I
> > > > > *need* snapshots.
> > > > >
> > > > > Help?
> > > > >
> > > > >
> > > > > --- Physical volume ---
> > > > > PV Name /dev/sda
> > > > > VG Name vg0
> > > > > PV Size 1.09 TB [2344319232 secs] / NOT usable 32.31 MB [LVM: 267 KB]
> > > > > PV# 1
> > > > > PV Status available
> > > > > Allocatable yes
> > > > > Cur LV 1
> > > > > PE Size (KByte) 32768
> > > > > Total PE 35770
> > > > > Free PE 570
> > > > > Allocated PE 35200
> > > > > PV UUID LyEPH1-pq2I-D022-v5c9-98rp-n7Ff-4LnNKL
> > > > >
> > > > > --- Volume group ---
> > > > > VG Name vg0
> > > > > VG Access read/write
> > > > > VG Status available/resizable
> > > > > VG # 0
> > > > > MAX LV 256
> > > > > Cur LV 1
> > > > > Open LV 1
> > > > > MAX LV Size 2 TB
> > > > > Max PV 256
> > > > > Cur PV 1
> > > > > Act PV 1
> > > > > VG Size 1.09 TB
> > > > > PE Size 32 MB
> > > > > Total PE 35770
> > > > > Alloc PE / Size 36032 / 1.10 TB
> > > > > Free PE / Size 4294967034 / 131071.99 TB
> > > > > VG UUID KciSkB-xbr8-22RM-zmke-6A69-6BEM-xLWMzv
> > > > >
> > > > > --- Logical volume ---
> > > > > LV Name /dev/vg0/lv0
> > > > > VG Name vg0
> > > > > LV Write Access read/write
> > > > > LV Status available
> > > > > LV # 1
> > > > > # open 1
> > > > > LV Size 1.07 TB
> > > > > Current LE 35200
> > > > > Allocated LE 35200
> > > > > Allocation next free
> > > > > Read ahead sectors 1024
> > > > > Block device 58:0
> > > > >
> > > > >
> > > > > procs memory swap io system cpu
> > > > > r b w swpd free buff cache si so bi bo in cs us sy id
> > > > > 0 0 0 0 3949704 1648 26104 0 0 3 2 27 5 0 0 100
> > > > >
> > > > >
> > > > > --
> > > > > "On two occasions, I have been asked [by members of Parliament], 'Pray,
> > > > > Mr. Babbage, if you put into the machine wrong figures, will the right
> > > > > answers come out?' I am not able to rightly apprehend the kind of confusion
> > > > > of ideas that could provoke such a question." -- Charles Babbage
> > > > >
> > > > > _______________________________________________
> > > > > 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 ***
> > > >
> > > > _______________________________________________
> > > > 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/
> > >
> > > --
> > > "On two occasions, I have been asked [by members of Parliament], 'Pray,
> > > Mr. Babbage, if you put into the machine wrong figures, will the right
> > > answers come out?' I am not able to rightly apprehend the kind of confusion
> > > of ideas that could provoke such a question." -- Charles Babbage
> > >
> > > _______________________________________________
> > > 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
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> >
> > _______________________________________________
> > 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/
>
> --
> "On two occasions, I have been asked [by members of Parliament], 'Pray,
> Mr. Babbage, if you put into the machine wrong figures, will the right
> answers come out?' I am not able to rightly apprehend the kind of confusion
> of ideas that could provoke such a question." -- Charles Babbage
>
> _______________________________________________
> 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/
--
Regards,
Heinz -- The LVM Guy --
*** 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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] Problems with LVM
2003-07-15 13:58 ` Heinz J . Mauelshagen
@ 2003-07-15 20:09 ` Petro
0 siblings, 0 replies; 11+ messages in thread
From: Petro @ 2003-07-15 20:09 UTC (permalink / raw)
To: linux-lvm
On Tue, Jul 15, 2003 at 08:55:23PM +0200, Heinz J . Mauelshagen wrote:
> On Sun, Jul 13, 2003 at 05:34:08PM -0700, Petro wrote:
> > On Sun, Jul 13, 2003 at 10:24:15PM +0200, Heinz J . Mauelshagen wrote:
> > > On Sun, Jul 13, 2003 at 11:27:43AM -0700, Petro wrote:
> > > > On Sun, Jul 13, 2003 at 12:11:51PM +0200, Heinz J . Mauelshagen wrote:
> > > > > Petro,
> > > > > what's the lvcreate command line ?
> > > > lvcreate -L10G -n snap000 -s /dev/vg0
> > > Looks like another vmalloc bug :(
> Yes.
> > Jul 13 13:11:55 back03-gig kernel: kernel BUG at vmalloc.c:236!
> > Jul 13 13:11:55 back03-gig kernel: invalid operand: 0000
> > Jul 13 13:11:55 back03-gig kernel: CPU: 2
> > Jul 13 13:11:55 back03-gig kernel: EIP: 0010:[__vmalloc+53/512]
> > Not tainted
> > > Kernel memory for snapshot exception tables gets allocated with vmalloc()
> > > which shouldn't fail (presumably there's enough memory free,
> > > which I assume in your case).
> > Freshly rebooted machine with 4 gig of physical memory, and nothing else
> > running.
> Which should happilly work in that case.
It doesn't.
> > > > > (highmem may cause problems if you use the snapsho9t, creation should
> > > > > work fine)
> > > > Is this highmem problem across all 2.4 kernels, or just 2.4.19+? The
> > > > first report I've seen of it is with a 2.4.19 kernel.
> > > Didn't retest with kernel 2.4.21 yet.
> > > The ones before had it AFAIK.
> > Starting when? the dawn of time?
> :-)
> We realized it in 2.4.19 for the first time but you prove that it was in 2.4.18
> as well.
> Anyone ?
The funny thing is that I've got some 2.4.18 boxes with *IDENTICAL*
configurations except for the disk sizes that work just fine.
These (the working boxes) have 6 80 gig disks attached to a 3ware
card in a stripe, and have been running fine since Feburary.
This is why I blew off the "doesn't work with highmem" stuff when it
was posted earlier--it was working for me on PV of 447.17 GB, with a
VG of 447.16 GB, and an LV of 435.00 GB.
These (we've got 5 of them) are are main database servers (2
clusters, one spare).
I've also had "lesser" machines running 2.4.18 doing the same thing.
(4x80 drives instead of 6x80).
> > Also, would switching to LVM2 sidestep this issue?
> Not that we can tell because it's a general vm problem.
This is what makes my boss curse Linux.
<sigh>
Time to start reading the help wanted adds.
> Regards,
> Heinz -- The LVM Guy --
>
> > > > >
> > > > > On Fri, Jul 11, 2003 at 05:01:27PM -0700, Petro wrote:
> > > > > > Hello again.
> > > > > >
> > > > > > I'm having a problem with LVM, and I'm really, really hoping you won't
> > > > > > tell me it's because of:
> > > > > >
> > > > > > # CONFIG_NOHIGHMEM is not set
> > > > > > CONFIG_HIGHMEM4G=y
> > > > > > # CONFIG_HIGHMEM64G is not set
> > > > > > CONFIG_HIGHMEM=y
> > > > > > CONFIG_HIGHIO=y
> > > > > >
> > > > > > (linux kernel 2.4.21, lvm 1.0.7 stuff installed)
> > > > > >
> > > > > > I've got 8 boxes with 4 gig of memory, and 6 200 gig drives in a raid 0
> > > > > > setup, and I need to use LVM+Snapshots.
> > > > > >
> > > > > > I can setup and create a 1.09T logical volume, but when I go to create a
> > > > > > snaphot, I get:
> > > > > >
> > > > > > lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/vg0/test"
> > > > > > lvcreate -- ERROR "Cannot allocate memory" creating VGDA for "/dev/vg0/test" in kernel
> > > > > >
> > > > > > Now, in reading past posts there is some talk of how having "high
> > > > > > memory" turned on will cause problems with snapshots.
> > > > > >
> > > > > > The problem is that on these machines I *need* 4 gig of memory, and I
> > > > > > *need* snapshots.
> > > > > >
> > > > > > Help?
> > > > > >
> > > > > >
> > > > > > --- Physical volume ---
> > > > > > PV Name /dev/sda
> > > > > > VG Name vg0
> > > > > > PV Size 1.09 TB [2344319232 secs] / NOT usable 32.31 MB [LVM: 267 KB]
> > > > > > PV# 1
> > > > > > PV Status available
> > > > > > Allocatable yes
> > > > > > Cur LV 1
> > > > > > PE Size (KByte) 32768
> > > > > > Total PE 35770
> > > > > > Free PE 570
> > > > > > Allocated PE 35200
> > > > > > PV UUID LyEPH1-pq2I-D022-v5c9-98rp-n7Ff-4LnNKL
> > > > > >
> > > > > > --- Volume group ---
> > > > > > VG Name vg0
> > > > > > VG Access read/write
> > > > > > VG Status available/resizable
> > > > > > VG # 0
> > > > > > MAX LV 256
> > > > > > Cur LV 1
> > > > > > Open LV 1
> > > > > > MAX LV Size 2 TB
> > > > > > Max PV 256
> > > > > > Cur PV 1
> > > > > > Act PV 1
> > > > > > VG Size 1.09 TB
> > > > > > PE Size 32 MB
> > > > > > Total PE 35770
> > > > > > Alloc PE / Size 36032 / 1.10 TB
> > > > > > Free PE / Size 4294967034 / 131071.99 TB
> > > > > > VG UUID KciSkB-xbr8-22RM-zmke-6A69-6BEM-xLWMzv
> > > > > >
> > > > > > --- Logical volume ---
> > > > > > LV Name /dev/vg0/lv0
> > > > > > VG Name vg0
> > > > > > LV Write Access read/write
> > > > > > LV Status available
> > > > > > LV # 1
> > > > > > # open 1
> > > > > > LV Size 1.07 TB
> > > > > > Current LE 35200
> > > > > > Allocated LE 35200
> > > > > > Allocation next free
> > > > > > Read ahead sectors 1024
> > > > > > Block device 58:0
> > > > > >
> > > > > >
> > > > > > procs memory swap io system cpu
> > > > > > r b w swpd free buff cache si so bi bo in cs us sy id
> > > > > > 0 0 0 0 3949704 1648 26104 0 0 3 2 27 5 0 0 100
> > > > > >
> > > > > >
> > > > > > --
> > > > > > "On two occasions, I have been asked [by members of Parliament], 'Pray,
> > > > > > Mr. Babbage, if you put into the machine wrong figures, will the right
> > > > > > answers come out?' I am not able to rightly apprehend the kind of confusion
> > > > > > of ideas that could provoke such a question." -- Charles Babbage
> > > > > >
> > > > > > _______________________________________________
> > > > > > 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 ***
> > > > >
> > > > > _______________________________________________
> > > > > 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/
> > > >
> > > > --
> > > > "On two occasions, I have been asked [by members of Parliament], 'Pray,
> > > > Mr. Babbage, if you put into the machine wrong figures, will the right
> > > > answers come out?' I am not able to rightly apprehend the kind of confusion
> > > > of ideas that could provoke such a question." -- Charles Babbage
> > > >
> > > > _______________________________________________
> > > > 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
> > > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> > >
> > > _______________________________________________
> > > 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/
> >
> > --
> > "On two occasions, I have been asked [by members of Parliament], 'Pray,
> > Mr. Babbage, if you put into the machine wrong figures, will the right
> > answers come out?' I am not able to rightly apprehend the kind of confusion
> > of ideas that could provoke such a question." -- Charles Babbage
> >
> > _______________________________________________
> > 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/
>
> --
>
> Regards,
> Heinz -- The LVM Guy --
>
> *** 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
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> _______________________________________________
> 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/
--
"On two occasions, I have been asked [by members of Parliament], 'Pray,
Mr. Babbage, if you put into the machine wrong figures, will the right
answers come out?' I am not able to rightly apprehend the kind of confusion
of ideas that could provoke such a question." -- Charles Babbage
^ permalink raw reply [flat|nested] 11+ messages in thread
* [linux-lvm] Problems with LVM
@ 2004-12-16 19:22 Mattias Runge
2004-12-21 20:36 ` Alasdair G Kergon
0 siblings, 1 reply; 11+ messages in thread
From: Mattias Runge @ 2004-12-16 19:22 UTC (permalink / raw)
To: LVM general discussion and development
Hi
I had a lvm-array with 3 disks � 120gb. One failed and then I could not
bring the array online. I had one partition spanning the whole array.
Finaly I tried vgreduce --removemissing, this got rid of the errors, but
unfortunatly it now seems that the whole lvm-array of the two remaing
disks is unallocated. My problem is that I would like to get the data of
the two remaining disks. Is there any way of doing this or did I !@"#�
up when i did vgreduce --removemissing?
I am using reiserfs on the disk.
Thanks
Mattias
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [linux-lvm] Problems with LVM
2004-12-16 19:22 Mattias Runge
@ 2004-12-21 20:36 ` Alasdair G Kergon
0 siblings, 0 replies; 11+ messages in thread
From: Alasdair G Kergon @ 2004-12-21 20:36 UTC (permalink / raw)
To: LVM general discussion and development
On Thu, Dec 16, 2004 at 08:22:00PM +0100, Mattias Runge wrote:
> up when i did vgreduce --removemissing?
vgcfgrestore should undo that operation
You can activate with -P to replace the missing disk with zeros
(see 'man lvm').
> I am using reiserfs on the disk.
I've never heard of anyone having much success recovering data
from reiserfs in such circumstances.
ext2 is much easier.
Alasdair
--
agk@redhat.com
^ permalink raw reply [flat|nested] 11+ messages in thread
* [linux-lvm] Problems with LVM
@ 2006-01-26 11:15 C'est Pierre
0 siblings, 0 replies; 11+ messages in thread
From: C'est Pierre @ 2006-01-26 11:15 UTC (permalink / raw)
To: linux-lvm
Hello,
I've been trying to compile Linux 2.6.14-3 on my RHEL-AS-4 instalation
and I can't seem to get it to boot. I've /, /home & /tmp as LVs of
only one VG (surprisingly called vg). My hdds are all IDE and the
distro boots with the generic kernel normally. However, with my
compiled kernel and the initrd image (the I created afterwards
installing the kernel's modules), I can't boot.
The error is the following:
Mounting root file system
mount : error 6 mounting ext3
mount: error 2 mounting none
switching to new root
switchroot: mount failed 22
umount /initrd/dev failed: 2
I am sure you know how to fix, I just can't seem to though. I do have
ext3 as module right now, but I did tests with ext3 built-in, so I
don't think that all I need is to have ext3 built-in to fix my
problem as I was able to find online through google.
Thanks very much for any sugestions/solutions!
Pierre
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2006-01-26 11:15 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-01-26 11:15 [linux-lvm] Problems with LVM C'est Pierre
-- strict thread matches above, loose matches on Subject: below --
2004-12-16 19:22 Mattias Runge
2004-12-21 20:36 ` Alasdair G Kergon
2003-07-11 18:28 [linux-lvm] Re: Safely removing a phantom disc-wide PV Chip McArtor
2003-07-11 19:02 ` [linux-lvm] Problems with LVM Petro
2003-07-13 5:14 ` Heinz J . Mauelshagen
2003-07-13 13:29 ` Petro
2003-07-13 15:26 ` Heinz J . Mauelshagen
2003-07-13 19:35 ` Petro
2003-07-13 22:43 ` Petro
2003-07-15 13:58 ` Heinz J . Mauelshagen
2003-07-15 20:09 ` Petro
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).