Once more -- running "lvremove" on a snapshot volume causes a kernel BUG (see attached file). - vgck reports no corruption of lvm meta-data - vgscan (without -D option) crashes as well (though not in the kernel) What other information can I provide for someone to make sense of this? I *have* to bring the vg into a consistent state and I urgently need to drop the snapshot volume -- is there any tool to manipulate lvm purely in userspace that can simply delete the snapshot volume? Regards -- Helge Bahmann <hcb@chaoticmind.net> /| \__ The past: Smart users in front of dumb terminals /_|____\ _/\ | __) $ ./configure \\ \|__/__| checking whether build environment is sane... yes \\/___/ | checking for AIX... no (we already did this) |
ksymoops 2.4.5 on i686 2.4.21-241-smp. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.21-241-smp/ (default) -m /boot/System.map-2.4.21-241-smp (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. kernel BUG at memory.c:531! invalid operand: 0000 2.4.21-241-smp #1 SMP Tue Aug 10 15:55:34 UTC 2004 CPU: 0 EIP: 0010:[<c0139ebb>] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010246 eax: 00000000 ebx: c10bfa50 ecx: 0000000b edx: c27fe840 esi: c27ffd10 edi: 00000000 ebp: 00000012 esp: cdd03d68 ds: 0018 es: 0018 ss: 0018 Process lvremove (pid: 1804, stackpage=cdd03000) Stack: c10bfa50 f541fea0 c013a358 c10bfa50 f5480000 f5480000 f5484a00 f54a5f76 f541fea0 f5480000 f54f8000 f54a3b7f f5480000 f595adc0 f5484b70 00000000 4004fe21 f54f8000 bfffed00 f54a084b 00000000 f54aafe0 ffffffff ccb19190 Call Trace: [<c013a358>] (20) [<f54a5f76>] (16) [<f54a3b7f>] (32) [<f54a084b>] (08) [<f54aafe0>] (12) [<c028bc44>] (68) [<c025d26d>] (20) [<c028ea96>] (08) [<c01421d5>] (48) [<c013b9cc>] (100) [<c013c078>] (52) [<c0170f20>] (16) [<c0156b05>] (56) [<c0156d01>] (28) [<c01550ea>] (28) [<c0154f68>] (28) [<c016b776>] (28) [<c0155382>] (24) [<c0109717>] (60) Code: 0f 0b 13 02 86 eb 2e c0 eb c2 8d 74 26 00 8d bc 27 00 00 00 >>EIP; c0139ebb <unpin_pte_page+5b/70> <===== >>ebx; c10bfa50 <_end+c1bd78/2d9c388> >>edx; c27fe840 <_end+235ab68/2d9c388> >>esi; c27ffd10 <_end+235c038/2d9c388> >>esp; cdd03d68 <[ide-cd].data.end+424009/1b20301> Trace; c013a358 <unmap_kiobuf+38/60> Trace; f54a5f76 <[lvm-mod]lvm_snapshot_release+96/100> Trace; f54a3b7f <[lvm-mod]lvm_do_lv_remove+13f/300> Trace; f54a084b <[lvm-mod]lvm_chr_ioctl+39b/6d0> Trace; f54aafe0 <[lvm-mod]lv_req+0/a0> Trace; c028bc44 <tcp_clean_rtx_queue+334/340> Trace; c025d26d <__kfree_skb+10d/170> Trace; c028ea96 <tcp_rcv_established+4a6/880> Trace; c01421d5 <filemap_nopage+1c5/240> Trace; c013b9cc <do_no_page+dc/4c0> Trace; c013c078 <handle_mm_fault+c8/200> Trace; c0170f20 <dput+30/150> Trace; c0156b05 <get_chrfops+155/170> Trace; c0156d01 <chrdev_open+71/b0> Trace; c01550ea <dentry_open+17a/1d0> Trace; c0154f68 <filp_open+68/70> Trace; c016b776 <sys_ioctl+f6/2d2> Trace; c0155382 <sys_open+a2/c0> Trace; c0109717 <system_call+33/38> Code; c0139ebb <unpin_pte_page+5b/70> 00000000 <_EIP>: Code; c0139ebb <unpin_pte_page+5b/70> <===== 0: 0f 0b ud2a <===== Code; c0139ebd <unpin_pte_page+5d/70> 2: 13 02 adc (%edx),%eax Code; c0139ebf <unpin_pte_page+5f/70> 4: 86 eb xchg %ch,%bl Code; c0139ec1 <unpin_pte_page+61/70> 6: 2e cs Code; c0139ec2 <unpin_pte_page+62/70> 7: c0 eb c2 shr $0xc2,%bl Code; c0139ec5 <unpin_pte_page+65/70> a: 8d 74 26 00 lea 0x0(%esi,1),%esi Code; c0139ec9 <unpin_pte_page+69/70> e: 8d bc 27 00 00 00 00 lea 0x0(%edi,1),%edi 1 warning issued. Results may not be reliable.
_______________________________________________ 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/