From: Heinz Mauelshagen <mauelshagen@redhat.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] LVM 1: Snapshot causes seg fault of lvdisplay and crashes system
Date: Mon Feb 16 04:29:01 2004 [thread overview]
Message-ID: <20040216092955.GC13581@redhat.com> (raw)
In-Reply-To: <200402140615.i1E6Fbr03401@ecstasy.winternet.com>
On Sat, Feb 14, 2004 at 12:15:37AM -0600, Ken Fuchs wrote:
> I did the following to create a snapshot of an active filesystem to try
> to make a consistent copy of it:
>
> # lvcreate --extents 30 --snapshot --name home2snap /dev/sys/home2gb
> ...
> lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/sys/home\
> 2snap"
> lvcreate -- doing automatic backup of "sys"
> lvcreate -- logical volume "/dev/sys/home2snap" successfully created
>
> # lvdisplay /dev/sys/home2gb
> --- Logical volume ---
> LV Name /dev/sys/home2gb
> VG Name sys
> LV Write Access read/write
> LV snapshot status source of
> /dev/sys/home2snap [active]
> Segmentation fault
> # lvdisplay /dev/sys/home2gb
> --- Logical volume ---
> LV Name /dev/sys/home2gb
> VG Name sys
> LV Write Access read/write
> LV snapshot status source of
> /dev/sys/home2snap [active]
> Segmentation fault
> ecstasy:/#
>
> <At this point I lost my remote connection to the machine and presume it
> crashed; it probably didn't reboot, since subsequent attempts to
> reconnect via ssh failed and ping failed as well.>
>
> The kernel is probably 1.0.3 (Debian SPARC sun4u 2.4.21 up) and the lvm
> tools are 1.0.8.
>
> Any suggestions for avoiding these seg faults and the system crash?
Upgrade to an actual driver LVM version. You hit a list bug IRT snapshots.
>
> Sincerely,
>
> Ken Fuchs <kfuchs@winternet.com>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.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 Red Hat, Inc.
Consulting Development Engineer Am Sonnenhang 11
56242 Marienrachdorf
Germany
Mauelshagen@RedHat.com +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2004-02-16 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 1:05 [linux-lvm] LVM 1: Snapshot causes seg fault of lvdisplay and crashes system Ken Fuchs
2004-02-16 4:29 ` Heinz Mauelshagen [this message]
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=20040216092955.GC13581@redhat.com \
--to=mauelshagen@redhat.com \
--cc=linux-lvm@redhat.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.