From: "Gregory K. Ade" <gkade@bigbrother.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] strange behavior with 1.0.5 on Linux 2.4.19?
Date: Sun Oct 27 22:30:02 2002 [thread overview]
Message-ID: <1035782975.3398.128.camel@gopher> (raw)
In-Reply-To: <20021009133650.E23965@sistina.com>
[-- Attachment #1: Type: text/plain, Size: 1733 bytes --]
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 #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-10-27 22:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 12:23 [linux-lvm] strange behavior with 1.0.5 on Linux 2.4.19? Gregory K. Ade
2002-10-04 3:54 ` Heinz J . Mauelshagen
2002-10-08 15:07 ` Gregory Ade
2002-10-09 6:38 ` Heinz J . Mauelshagen
2002-10-27 22:30 ` Gregory K. Ade [this message]
2002-10-28 3:21 ` Heinz J . Mauelshagen
2002-10-28 22:38 ` Gregory K. Ade
2002-10-29 3:15 ` Heinz J . Mauelshagen
2002-10-29 13:54 ` Gregory K. Ade
2002-10-31 6:52 ` Heinz J . Mauelshagen
2002-10-31 16:55 ` Gregory Ade
2002-11-01 9:07 ` Wolfgang Weisselberg
2002-11-05 8:33 ` Heinz J . Mauelshagen
2002-11-07 21:45 ` Gregory Ade
2002-11-09 6:12 ` Heinz J . Mauelshagen
2002-11-11 5:56 ` Jon Bendtsen
2002-11-22 15:51 ` Gregory Ade
2002-12-05 21:35 ` Gregory Ade
2002-10-28 14:36 ` jon+lvm
2002-10-28 16:40 ` Gregory K. Ade
2002-10-29 15:21 ` Luca Berra
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=1035782975.3398.128.camel@gopher \
--to=gkade@bigbrother.net \
--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.