All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petro <petro@corp.vendio.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Problems with LVM
Date: Tue Jul 15 20:09:01 2003	[thread overview]
Message-ID: <20030716010804.GJ26404@corp.vendio.com> (raw)
In-Reply-To: <20030715205523.A25876@sistina.com>

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 

  reply	other threads:[~2003-07-15 20:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]
  -- strict thread matches above, loose matches on Subject: below --
2004-12-16 19:22 Mattias Runge
2004-12-21 20:36 ` Alasdair G Kergon
2006-01-26 11:15 C'est Pierre

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=20030716010804.GJ26404@corp.vendio.com \
    --to=petro@corp.vendio.com \
    --cc=linux-lvm@sistina.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.