From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Heinz J . Mauelshagen" Subject: Re: [linux-lvm] strange behavior with 1.0.5 on Linux 2.4.19? Message-ID: <20021028101739.F16452@sistina.com> References: <1033579350.6468.61.camel@gopher> <20021004105057.B8575@sistina.com> <1034107599.28928.105.camel@pslgregory> <20021009133650.E23965@sistina.com> <1035782975.3398.128.camel@gopher> Mime-Version: 1.0 In-Reply-To: <1035782975.3398.128.camel@gopher>; from gkade@bigbrother.net on Sun, Oct 27, 2002 at 09:29:35PM -0800 Sender: linux-lvm-admin@sistina.com Errors-To: linux-lvm-admin@sistina.com Reply-To: linux-lvm@sistina.com List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: Date: Mon Oct 28 03:21:02 2002 List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-lvm@sistina.com On Sun, Oct 27, 2002 at 09:29:35PM -0800, Gregory K. Ade wrote: > On Wed, 2002-10-09 at 04:36, Heinz J . Mauelshagen wrote: > > > > True, it is not. Manual page says "OriginalLogicalVolumePath". > > > > root@burpr(pts/0):~ 24 # lvcreate --snapshot --extents 512 --name tmp_snap /dev/vg00/tmp > lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/vg00/tmp_snap" > Segmentation fault > root@burpr(pts/0):~ 25 # > > This is not good. This is a system that has been recently rebooted, and > come up clean. This i sthe very first LVM command I have run by hand > since the boot. > > In terms of the other problems I was having, I think I _may_ have gotten > those fixed (i.e., things like `find /` killing the system) by some > friendly souls in the linux-kernel mailing list with a VM patch. There > seemed to be a bug in largemem systems that was being exercised. > > Now, I just rebooted the system with that patch on a fresh kernel: > Linux Kernel 2.4.19, patched with the VM patch, LVM 1.0.5 and Broadcom > Gigabit Ethernet patches. > > I left for dinner, during which time nobody did anything to the > machine. I came back and decided to try creating a snapshot volume of > /dev/vg00/tmp, and lvcreate segfaulted. lvscan also segfaults, vgscan > hangs, and vgdisplay and lvdisplay seem to still work. > > trying to create a test volume after that (`lvcreate --extents 512 > --name testvol vg00`) simply hangs. > > So, who do I give what information to so that we can trace down the base > of this problem, and get a fix? Ask me for whatever you need from the > system, and I'll provide it if I can. Run the kernel oops you probably got for "lvcreate --snapshot ..." through ksymoops, please. After that oops the LVM driver is in no sane state anyway which is the reason for other LVM commands to behave strangely. > > Thanks again in advance, > > Gregory > > > > -- > Gregory K. Ade > http://bigbrother.net/~gkade > OpenPGP Key ID: EAF4844B keyserver: pgpkeys.mit.edu -- 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 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-