From: "Stephan Austermühle" <au@hcsd.de>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Kernel bug with snapshots
Date: Sat, 15 Jan 2005 14:20:55 +0100 [thread overview]
Message-ID: <20050115132055.GA18967@hcsd.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 4222 bytes --]
Hi,
in the last days I played around with Kernel 2.6.9, LVM2, and multiple
snapshots of the Logical Volume leading to some system freezes. The
Volume Group is setup on top of a mirrored device (md). I decided to
switch to kernel 2.6.11-rc1 with Device Mapper patches 2.6.10-udm1
(without patch 29) and test again.
What I did was:
1. created a 2 GByte LV (lv_test) with XFS and mounted the filesystem.
2. Wrote some data to lv_test.
3. Created snapshot using
lvcreate -L 200M -p r -n lv_snap_01 /dev/vg00/lv_test
4. Mounted lv_snap_01 (read only, no uuid)
5. Removed some files and wrote some data to lv_test
6. Created snapshot lv_snap_02 and mounted it (read only, no uuid)
7. Repeated step 5 and created snapshot lv_snap_03
8. Wrote some data (about 30 MByte) to lv_test
9. While kcopyd(?) was running I tried to remove lv_snap_01:
lvremove -f /dev/vg00/lv_snap_01
The lvremove instruction terminated with
Segmentation fault
and I received the following kernel messages on console:
------------[ cut here ]------------
kernel BUG at drivers/md/kcopyd.c:145!
invalid operand: 0000 [#1]
Modules linked in: nfs lockd sunrpc autofs4 8250 serial_core md5 ipv6 uhci_hcd usbcore 3c59x mii unix
CPU: 0
EIP: 0060:[<c0281989>] Not tainted VLI
EFLAGS: 00010287 (2.6.11-rc1-udm1)
EIP is at client_free_pages+0x39/0x50
eax: 00000100 ebx: d1b6eb20 ecx: d9ad1820 edx: 00000000
esi: e19a4040 edi: 00000000 ebp: cec0defc esp: cec0def4
ds: 007b es: 007b ss: 0068
Process lvremove (pid: 1926, threadinfo=cec0c000 task=d98e4060)
Stack: d1b6eb20 d1b6eb20 cec0df0c c028237f d1b6eb20 da370b60 cec0df24 c0282db4
d1b6eb20 d1b6ed40 e19a4040 d98cac20 cec0df40 c027c846 e19a4040 00000000
dd529940 e085b000 00000004 cec0df54 c027e81d d98cac20 00000000 c0373fa0
Call Trace:
[<c010325f>] show_stack+0x7f/0xa0
[<c01033fa>] show_registers+0x15a/0x1c0
[<c01035ce>] die+0xce/0x150
[<c0103a69>] do_invalid_op+0xb9/0xd0
[<c0102eeb>] error_code+0x2b/0x30
[<c028237f>] kcopyd_client_destroy+0x1f/0x38
[<c0282db4>] snapshot_dtr+0x74/0x90
[<c027c846>] table_destroy+0xa6/0xc0
[<c027e81d>] __hash_remove+0x5d/0x80
[<c027f040>] dev_remove+0x50/0xd0
[<c028066e>] ctl_ioctl+0xde/0x140
[<c015ed05>] sys_ioctl+0xa5/0x220
[<c01024d7>] syscall_call+0x7/0xb
Code: 0c 39 43 10 75 25 8b 43 08 89 04 24 e8 51 ff ff ff c7 43 08 00 00 00 00 c7 43 0c 00 00 00 00 c7 43 10 00 00 00 00 8b 5d fc c9 c3 <0f> 0b 91 00 6c f4 2f c0 eb d1 8d b6 00 00 00 00 8d bc 27 00 00
<1>Unable to handle kernel paging request at virtual address e19a74b0
printing eip:
c0283fae
*pde = 0152e067
*pte = 00000000
Oops: 0002 [#2]
Modules linked in: nfs lockd sunrpc autofs4 8250 serial_core md5 ipv6 uhci_hcd usbcore 3c59x mii unix
CPU: 0
EIP: 0060:[<c0283fae>] Not tainted VLI
EFLAGS: 00010282 (2.6.11-rc1-udm1)
EIP is at write_exception+0x2e/0x50
eax: 000064a6 ebx: d94e9ebc ecx: e19a74b0 edx: 00000000
esi: 00000000 edi: cedb73bc ebp: d94e9ea8 esp: d94e9e9c
ds: 007b es: 007b ss: 0068
Process kcopyd (pid: 1749, threadinfo=d94e8000 task=da066590)
Stack: d4360da0 0000014b d4360da0 d94e9ed8 c02842c5 d4360da0 0000014b d94e9ebc
000064a6 00000000 0000505b 00000000 cedba944 00000000 cedb73bc d94e9ef0
c0283122 da370bac cedb73bc c02830d0 cedb73bc d94e9f18 c0281b10 00000000
Call Trace:
[<c010325f>] show_stack+0x7f/0xa0
[<c01033fa>] show_registers+0x15a/0x1c0
[<c01035ce>] die+0xce/0x150
[<c0111fdb>] do_page_fault+0x31b/0x66f
[<c0102eeb>] error_code+0x2b/0x30
[<c02842c5>] persistent_commit+0x45/0x100
[<c0283122>] copy_callback+0x42/0x50
[<c0281b10>] run_complete_job+0x60/0x70
[<c0281d14>] process_jobs+0x44/0xb0
[<c0281d9a>] do_work+0x1a/0x50
[<c0125513>] worker_thread+0x183/0x220
[<c0128f5a>] kthread+0xaa/0xb0
[<c0100881>] kernel_thread_helper+0x5/0x14
Code: 83 ec 0c 8b 45 0c 89 5d fc 8b 5d 10 89 44 24 04 8b 45 08 89 04 24 e8 72 ff ff ff 89 c1 b8 ea ff ff ff 85 c9 74 18 8b 03 8b 53 04 <89> 01 89 51 04 8b 43 08 8b 53 0c 89 41 08 31 c0 89 51 0c 8b 5d
Looks likes a bug...
Kind regards,
Stephan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-01-15 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-15 13:20 Stephan Austermühle [this message]
2005-01-16 10:30 ` [linux-lvm] Re: Kernel bug with snapshots Bruno Bonfils
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=20050115132055.GA18967@hcsd.de \
--to=au@hcsd.de \
--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.