On Wed, 2002-10-09 at 04:36, Heinz J . Mauelshagen wrote: > <pickymode> > True, it is not. Manual page says "OriginalLogicalVolumePath". > </pickymode> 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. Thanks again in advance, Gregory -- Gregory K. Ade <gkade@bigbrother.net> http://bigbrother.net/~gkade OpenPGP Key ID: EAF4844B keyserver: pgpkeys.mit.edu
Attachment:
signature.asc
Description: This is a digitally signed message part
