From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] severe problems to remove invalid/full snapshots with debian-etch
Date: Fri, 02 Mar 2007 23:18:29 +0100 [thread overview]
Message-ID: <45E8A2B5.3020103@wpkg.org> (raw)
In-Reply-To: <20070302210230.GA10659@iss.tu-darmstadt.de>
Tom Assmuth schrieb:
> hi,
>
> i gave up using lvm2 with debian sarge cause to a lot of problems
> concerning stability but now i gave it another try with my debian-etch
> box. but here problems with snapshots are still severe.
>
> --
> used system:
> kernel: 2.6.18-3-686 (normal kernel version in etch)
> lvm version
> LVM version: 2.02.07 (2006-07-17)
> Library version: 1.02.08 (2006-07-17)
> Driver version: 4.7.0
> --
>
> problem:
>
> if a snapshot runs full (having attributes like this calling
> lvs: Swi-I- ) I of course try to remove it with lvremove:
>
> this will throw something like this on all consoles:
>
> kernel BUG at mm/slab.c:595!
> invalid opcode: 0000 [#1]
> EIP is at kmem_cache_free+0x29/0x6d
> esi: daa2f28c edi: d9439a88 ebp: 00036c68 esp: c593fdb0
> Process lvremove (pid: 25402, ti=c593e000 task=c533aaa0 task.ti=c593e000)
> Stack: 15f529ae daa2f28c dd08dc68 dc86c94e dbf84220 00006d8d 00008000 daa2f240
> ...
> EIP: [<c0156f55>] kmem_cache_free+0x29/0x6d SS:ESP 0068:c593fdb0
> ...
(...)
Check the answer to my earlier post ("moving logical volumes to another
system *remotely* - how?") by Bryn M. Reeves:
This is a known issue in older kernels that was fixed upstream in
2.6.19. See:
http://www.uwsg.iu.edu/hypermail/linux/kernel/0612.1/2301.html
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=204791
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2007-03-02 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 21:02 [linux-lvm] severe problems to remove invalid/full snapshots with debian-etch Tom Assmuth
2007-03-02 22:18 ` Tomasz Chmielewski [this message]
2007-03-05 18:47 ` Tom Assmuth
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=45E8A2B5.3020103@wpkg.org \
--to=mangoo@wpkg.org \
--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.