* [linux-lvm] Snapshot segfaults lvremove + bug kernel
@ 2006-05-02 9:32 Gabriel Barazer
2006-05-08 22:19 ` [linux-lvm] " Robin Bowes
2006-05-09 9:41 ` [linux-lvm] " Heinz Mauelshagen
0 siblings, 2 replies; 8+ messages in thread
From: Gabriel Barazer @ 2006-05-02 9:32 UTC (permalink / raw)
To: linux-lvm
Hello,
I recently posted a LVM freeze while deleting snapshot, which could be workaround-ed by issuing a dmsetup resume command.
I was replied on the list that my tools weren't up to date (i had the stable versions, the up to date are devel), so I retried the whole thing (adding/deleting snapshot) with the new tools
Versions are :
Kernel 2.6.16.1
LVM 2.02.05
Livdevmapper 1.02.05
Driver 4.5.0
The lvcreate has been successfully created , but the lvremove after gave me a segfault. Then the whole LVM system froze. After hard-rebooting, the snapshot is still here. Anyone got the same , or found a solution ?
Here is the kernel bug detail :
May 2 11:01:19 filer1 kernel: ----------- [cut here ] --------- [please bite here ] ---------
May 2 11:01:19 filer1 kernel: Kernel BUG at drivers/md/kcopyd.c:146
May 2 11:01:19 filer1 kernel: invalid opcode: 0000 [1] SMP
May 2 11:01:19 filer1 kernel: CPU 2
May 2 11:01:19 filer1 kernel: Modules linked in:
May 2 11:01:19 filer1 kernel: Pid: 22328, comm: lvremove Not tainted 2.6.16.1 #1
May 2 11:01:19 filer1 kernel: RIP: 0010:[<ffffffff80378628>] <ffffffff80378628>{client_free_pages+12}
May 2 11:01:19 filer1 kernel: RSP: 0000:ffff810056effcb8 EFLAGS: 00010287
May 2 11:01:19 filer1 kernel: RAX: 0000000000000100 RBX: ffff810011a46cc0 RCX: 000000000000004c
May 2 11:01:19 filer1 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff810011a46cc0
May 2 11:01:19 filer1 kernel: RBP: ffffc20000029080 R08: ffff810002f97c18 R09: 0000000000000000
May 2 11:01:19 filer1 kernel: R10: ffff81007b489200 R11: ffff8100474d13c0 R12: 0000000000000000
May 2 11:01:19 filer1 kernel: R13: 00000000c138fd04 R14: 00000000005a81f0 R15: ffffffff80377031
May 2 11:01:19 filer1 kernel: FS: 00002b71ca6386e0(0000) GS:ffff81007ff11340(0000) knlGS:0000000000000000
May 2 11:01:19 filer1 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
May 2 11:01:19 filer1 kernel: CR2: 000000000043c3c0 CR3: 0000000050ee8000 CR4: 00000000000006e0
May 2 11:01:19 filer1 kernel: Process lvremove (pid: 22328, threadinfo ffff810056efe000, task ffff81007f0c37a0)
May 2 11:01:19 filer1 kernel: Stack: ffff810011a46cc0 ffffffff80378fe3 ffff81001b976bc0 ffffffff8037cd87
May 2 11:01:19 filer1 kernel: ffff8100641ef8c8 ffffc20000029080 ffff81007f381e00 ffffffff803750b9
May 2 11:01:19 filer1 kernel: ffff81007f381e00 ffff8100474d11c0
May 2 11:01:19 filer1 kernel: Call Trace: <ffffffff80378fe3>{kcopyd_client_destroy+20}
May 2 11:01:19 filer1 kernel: <ffffffff8037cd87>{snapshot_dtr+217} <ffffffff803750b9>{dm_table_put+95}
May 2 11:01:19 filer1 kernel: <ffffffff8037685e>{__hash_remove+124} <ffffffff80377077>{dev_remove+70}
May 2 11:01:19 filer1 kernel: <ffffffff80377d6b>{ctl_ioctl+600} <ffffffff80451bc1>{__sched_text_start+1473}
May 2 11:01:19 filer1 kernel: <ffffffff80180865>{do_ioctl+93} <ffffffff80180ae1>{vfs_ioctl+618}
May 2 11:01:19 filer1 kernel: <ffffffff80180b2e>{sys_ioctl+60} <ffffffff8010a9a6>{system_call+126}
May 2 11:01:19 filer1 kernel:
May 2 11:01:19 filer1 kernel: Code: 0f 0b 68 06 93 4b 80 c2 92 00 48 8b 7b 18 e8 b6 ff ff ff 48
May 2 11:01:19 filer1 kernel: RIP <ffffffff80378628>{client_free_pages+12} RSP <ffff810056effcb8>
May 2 11:01:19 filer1 kernel: <1>Unable to handle kernel NULL pointer dereference at 0000000000000040 RIP:
May 2 11:01:19 filer1 kernel: <ffffffff80174ca6>{bio_add_page+22}
May 2 11:01:19 filer1 kernel: PGD 0
May 2 11:01:19 filer1 kernel: Oops: 0000 [2] SMP
May 2 11:01:19 filer1 kernel: CPU 0
May 2 11:01:19 filer1 kernel: Modules linked in:
May 2 11:01:19 filer1 kernel: Pid: 2775, comm: kcopyd Not tainted 2.6.16.1 #1
May 2 11:01:19 filer1 kernel: RIP: 0010:[<ffffffff80174ca6>] <ffffffff80174ca6>{bio_add_page+22}
May 2 11:01:19 filer1 kernel: RSP: 0018:ffff81007af9bcf0 EFLAGS: 00010206
May 2 11:01:19 filer1 kernel: RAX: 0000000000000000 RBX: ffff810078152d00 RCX: 0000000000001000
May 2 11:01:19 filer1 kernel: RDX: ffff810002284bc8 RSI: ffff810002284bc8 RDI: ffff810078152d00
May 2 11:01:19 filer1 kernel: RBP: 0000000000000010 R08: 0000000000000000 R09: ffff81007fbd68e0
May 2 11:01:19 filer1 kernel: R10: ffff810078152d00 R11: ffff81007f837958 R12: ffff81007af9bdc8
May 2 11:01:19 filer1 kernel: R13: ffff81007af96380 R14: ffff81005bb73500 R15: 0000000000000001
May 2 11:01:19 filer1 kernel: FS: 0000000000000000(0000) GS:ffffffff80600000(0000) knlGS:0000000000000000
May 2 11:01:19 filer1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
May 2 11:01:19 filer1 kernel: CR2: 0000000000000040 CR3: 000000007b1d2000 CR4: 00000000000006e0
May 2 11:01:19 filer1 kernel: Process kcopyd (pid: 2775, threadinfo ffff81007af9a000, task ffff81007fbd68e0)
May 2 11:01:19 filer1 kernel: Stack: ffffffff803781ef 0000000000000246 ffff81007af96380 000000017fafb6c0
May 2 11:01:19 filer1 kernel: ffff810002284bc8 0000000000001000 0000000080150ab2 ffffffff80377f95
May 2 11:01:19 filer1 kernel: ffffffff80377fb6 ffff810000000000
May 2 11:01:19 filer1 kernel: Call Trace: <ffffffff803781ef>{dispatch_io+344} <ffffffff80377f95>{list_get_page+0}
May 2 11:01:19 filer1 kernel: <ffffffff80377fb6>{list_next_page+0} <ffffffff80378722>{complete_io+0}
May 2 11:01:19 filer1 kernel: <ffffffff803783e5>{async_io+172} <ffffffff80378722>{complete_io+0}
May 2 11:01:19 filer1 kernel: <ffffffff80378508>{dm_io_async+64} <ffffffff80377f95>{list_get_page+0}
May 2 11:01:19 filer1 kernel: <ffffffff80377fb6>{list_next_page+0} <ffffffff80378800>{run_io_job+0}
May 2 11:01:19 filer1 kernel: <ffffffff803789f6>{do_work+0} <ffffffff80378844>{run_io_job+68}
May 2 11:01:19 filer1 kernel: <ffffffff8037891c>{process_jobs+28} <ffffffff8013fdfa>{run_workqueue+155}
May 2 11:01:19 filer1 kernel: <ffffffff8013fe41>{worker_thread+0} <ffffffff80143248>{keventd_create_kthread+0}
May 2 11:01:19 filer1 kernel: <ffffffff8013ff46>{worker_thread+261} <ffffffff8012a872>{default_wake_function+0}
May 2 11:01:19 filer1 kernel: <ffffffff80143248>{keventd_create_kthread+0} <ffffffff8012a872>{default_wake_function+0}
May 2 11:01:19 filer1 kernel: <ffffffff80143248>{keventd_create_kthread+0} <ffffffff8014321f>{kthread+200}
May 2 11:01:19 filer1 kernel: <ffffffff8010b89e>{child_rip+8} <ffffffff80143248>{keventd_create_kthread+0}
May 2 11:01:19 filer1 kernel: <ffffffff80143157>{kthread+0} <ffffffff8010b896>{child_rip+0}
May 2 11:01:19 filer1 kernel:
May 2 11:01:19 filer1 kernel: Code: 48 8b 78 40 4c 89 d6 44 0f b7 8f 54 02 00 00 e9 e6 fd ff ff
May 2 11:01:19 filer1 kernel: RIP <ffffffff80174ca6>{bio_add_page+22} RSP <ffff81007af9bcf0>
May 2 11:01:19 filer1 kernel: CR2: 0000000000000040
----
Hardware is dual xeon em64t on 64bit fedora3-based distro.
--
Gabriel Barazer <gabriel@oxeva.fr>
OXEVA
Tel: +33 (0) 478 37 12 05
Fax: +33 (0) 472 56 50 49
^ permalink raw reply [flat|nested] 8+ messages in thread
* [linux-lvm] Re: Snapshot segfaults lvremove + bug kernel
2006-05-02 9:32 [linux-lvm] Snapshot segfaults lvremove + bug kernel Gabriel Barazer
@ 2006-05-08 22:19 ` Robin Bowes
2006-05-09 9:41 ` [linux-lvm] " Heinz Mauelshagen
1 sibling, 0 replies; 8+ messages in thread
From: Robin Bowes @ 2006-05-08 22:19 UTC (permalink / raw)
To: linux-lvm
Gabriel Barazer wrote:
> > Hello,
> >
> > I recently posted a LVM freeze while deleting snapshot, which could
> > be workaround-ed by issuing a dmsetup resume command.
> >
> > I was replied on the list that my tools weren't up to date (i had the
> > stable versions, the up to date are devel), so I retried the whole
> > thing (adding/deleting snapshot) with the new tools
> >
> > Versions are :
> > Kernel 2.6.16.1
> > LVM 2.02.05
> > Livdevmapper 1.02.05
> > Driver 4.5.0
> >
> > The lvcreate has been successfully created , but the lvremove after
> > gave me a segfault. Then the whole LVM system froze. After
> > hard-rebooting, the snapshot is still here. Anyone got the same , or
> > found a solution ?
I'm seeing a similar thing.
I've just started using snapshots as part of my backup process. I create
a snapshot, mount it, and take the backup from the snapshot then umount
and lvremove the snapshot when the backup has finished.
This seemed to be working but the server hung and required rebooting.
Now when I try and use lvremove to remove the snapshots the server hangs.
This is the output of lvs:
LV VG Attr LSize Origin Snap% Move Copy%
lv_home VolGroup00 owi-ao 5.00G
lv_home.snap VolGroup00 swi-a- 512.00M lv_home 5.35
lv_root VolGroup00 owi-ao 1.00G
lv_root.snap VolGroup00 swi-a- 512.00M lv_root 9.14
lv_scratch VolGroup00 -wi-ao 50.00G
lv_swap_01 VolGroup00 -wi-ao 4.00G
lv_usr VolGroup00 owi-ao 5.00G
lv_usr.snap VolGroup00 swi-a- 512.00M lv_usr 5.86
lv_var VolGroup00 owi-ao 54.09G
lv_var.snap VolGroup00 swi-a- 512.00M lv_var 40.77
This is on an x86_64 Fedora Core 4 system:
Kernel: kernel-2.6.16-1.2096_FC4
LVM version: 2.01.08 (2005-03-22)
Library version: 1.01.02 (2005-05-17)
Driver version: 4.5.0
Any idea what might be causing this?
Any idea how to clean up the system, i.e. remove the
snapshots?
R.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] Snapshot segfaults lvremove + bug kernel
2006-05-02 9:32 [linux-lvm] Snapshot segfaults lvremove + bug kernel Gabriel Barazer
2006-05-08 22:19 ` [linux-lvm] " Robin Bowes
@ 2006-05-09 9:41 ` Heinz Mauelshagen
2006-05-09 18:15 ` Robin Bowes
1 sibling, 1 reply; 8+ messages in thread
From: Heinz Mauelshagen @ 2006-05-09 9:41 UTC (permalink / raw)
To: Gabriel Barazer; +Cc: linux-lvm
Gabriel,
this is a known issue with tearing down kcopyd jobs we're working on.
Heinz
On Tue, May 02, 2006 at 11:32:23AM +0200, Gabriel Barazer wrote:
> Hello,
>
> I recently posted a LVM freeze while deleting snapshot, which could be workaround-ed by issuing a dmsetup resume command.
>
> I was replied on the list that my tools weren't up to date (i had the stable versions, the up to date are devel), so I retried the whole thing (adding/deleting snapshot) with the new tools
> Versions are :
> Kernel 2.6.16.1
> LVM 2.02.05
> Livdevmapper 1.02.05
> Driver 4.5.0
>
> The lvcreate has been successfully created , but the lvremove after gave me a segfault. Then the whole LVM system froze. After hard-rebooting, the snapshot is still here. Anyone got the same , or found a solution ?
>
> Here is the kernel bug detail :
>
> May 2 11:01:19 filer1 kernel: ----------- [cut here ] --------- [please bite here ] ---------
> May 2 11:01:19 filer1 kernel: Kernel BUG at drivers/md/kcopyd.c:146
> May 2 11:01:19 filer1 kernel: invalid opcode: 0000 [1] SMP
> May 2 11:01:19 filer1 kernel: CPU 2
> May 2 11:01:19 filer1 kernel: Modules linked in:
> May 2 11:01:19 filer1 kernel: Pid: 22328, comm: lvremove Not tainted 2.6.16.1 #1
> May 2 11:01:19 filer1 kernel: RIP: 0010:[<ffffffff80378628>] <ffffffff80378628>{client_free_pages+12}
> May 2 11:01:19 filer1 kernel: RSP: 0000:ffff810056effcb8 EFLAGS: 00010287
> May 2 11:01:19 filer1 kernel: RAX: 0000000000000100 RBX: ffff810011a46cc0 RCX: 000000000000004c
> May 2 11:01:19 filer1 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff810011a46cc0
> May 2 11:01:19 filer1 kernel: RBP: ffffc20000029080 R08: ffff810002f97c18 R09: 0000000000000000
> May 2 11:01:19 filer1 kernel: R10: ffff81007b489200 R11: ffff8100474d13c0 R12: 0000000000000000
> May 2 11:01:19 filer1 kernel: R13: 00000000c138fd04 R14: 00000000005a81f0 R15: ffffffff80377031
> May 2 11:01:19 filer1 kernel: FS: 00002b71ca6386e0(0000) GS:ffff81007ff11340(0000) knlGS:0000000000000000
> May 2 11:01:19 filer1 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> May 2 11:01:19 filer1 kernel: CR2: 000000000043c3c0 CR3: 0000000050ee8000 CR4: 00000000000006e0
> May 2 11:01:19 filer1 kernel: Process lvremove (pid: 22328, threadinfo ffff810056efe000, task ffff81007f0c37a0)
> May 2 11:01:19 filer1 kernel: Stack: ffff810011a46cc0 ffffffff80378fe3 ffff81001b976bc0 ffffffff8037cd87
> May 2 11:01:19 filer1 kernel: ffff8100641ef8c8 ffffc20000029080 ffff81007f381e00 ffffffff803750b9
> May 2 11:01:19 filer1 kernel: ffff81007f381e00 ffff8100474d11c0
> May 2 11:01:19 filer1 kernel: Call Trace: <ffffffff80378fe3>{kcopyd_client_destroy+20}
> May 2 11:01:19 filer1 kernel: <ffffffff8037cd87>{snapshot_dtr+217} <ffffffff803750b9>{dm_table_put+95}
> May 2 11:01:19 filer1 kernel: <ffffffff8037685e>{__hash_remove+124} <ffffffff80377077>{dev_remove+70}
> May 2 11:01:19 filer1 kernel: <ffffffff80377d6b>{ctl_ioctl+600} <ffffffff80451bc1>{__sched_text_start+1473}
> May 2 11:01:19 filer1 kernel: <ffffffff80180865>{do_ioctl+93} <ffffffff80180ae1>{vfs_ioctl+618}
> May 2 11:01:19 filer1 kernel: <ffffffff80180b2e>{sys_ioctl+60} <ffffffff8010a9a6>{system_call+126}
> May 2 11:01:19 filer1 kernel:
> May 2 11:01:19 filer1 kernel: Code: 0f 0b 68 06 93 4b 80 c2 92 00 48 8b 7b 18 e8 b6 ff ff ff 48
> May 2 11:01:19 filer1 kernel: RIP <ffffffff80378628>{client_free_pages+12} RSP <ffff810056effcb8>
> May 2 11:01:19 filer1 kernel: <1>Unable to handle kernel NULL pointer dereference at 0000000000000040 RIP:
> May 2 11:01:19 filer1 kernel: <ffffffff80174ca6>{bio_add_page+22}
> May 2 11:01:19 filer1 kernel: PGD 0
> May 2 11:01:19 filer1 kernel: Oops: 0000 [2] SMP
> May 2 11:01:19 filer1 kernel: CPU 0
> May 2 11:01:19 filer1 kernel: Modules linked in:
> May 2 11:01:19 filer1 kernel: Pid: 2775, comm: kcopyd Not tainted 2.6.16.1 #1
> May 2 11:01:19 filer1 kernel: RIP: 0010:[<ffffffff80174ca6>] <ffffffff80174ca6>{bio_add_page+22}
> May 2 11:01:19 filer1 kernel: RSP: 0018:ffff81007af9bcf0 EFLAGS: 00010206
> May 2 11:01:19 filer1 kernel: RAX: 0000000000000000 RBX: ffff810078152d00 RCX: 0000000000001000
> May 2 11:01:19 filer1 kernel: RDX: ffff810002284bc8 RSI: ffff810002284bc8 RDI: ffff810078152d00
> May 2 11:01:19 filer1 kernel: RBP: 0000000000000010 R08: 0000000000000000 R09: ffff81007fbd68e0
> May 2 11:01:19 filer1 kernel: R10: ffff810078152d00 R11: ffff81007f837958 R12: ffff81007af9bdc8
> May 2 11:01:19 filer1 kernel: R13: ffff81007af96380 R14: ffff81005bb73500 R15: 0000000000000001
> May 2 11:01:19 filer1 kernel: FS: 0000000000000000(0000) GS:ffffffff80600000(0000) knlGS:0000000000000000
> May 2 11:01:19 filer1 kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
> May 2 11:01:19 filer1 kernel: CR2: 0000000000000040 CR3: 000000007b1d2000 CR4: 00000000000006e0
> May 2 11:01:19 filer1 kernel: Process kcopyd (pid: 2775, threadinfo ffff81007af9a000, task ffff81007fbd68e0)
> May 2 11:01:19 filer1 kernel: Stack: ffffffff803781ef 0000000000000246 ffff81007af96380 000000017fafb6c0
> May 2 11:01:19 filer1 kernel: ffff810002284bc8 0000000000001000 0000000080150ab2 ffffffff80377f95
> May 2 11:01:19 filer1 kernel: ffffffff80377fb6 ffff810000000000
> May 2 11:01:19 filer1 kernel: Call Trace: <ffffffff803781ef>{dispatch_io+344} <ffffffff80377f95>{list_get_page+0}
> May 2 11:01:19 filer1 kernel: <ffffffff80377fb6>{list_next_page+0} <ffffffff80378722>{complete_io+0}
> May 2 11:01:19 filer1 kernel: <ffffffff803783e5>{async_io+172} <ffffffff80378722>{complete_io+0}
> May 2 11:01:19 filer1 kernel: <ffffffff80378508>{dm_io_async+64} <ffffffff80377f95>{list_get_page+0}
> May 2 11:01:19 filer1 kernel: <ffffffff80377fb6>{list_next_page+0} <ffffffff80378800>{run_io_job+0}
> May 2 11:01:19 filer1 kernel: <ffffffff803789f6>{do_work+0} <ffffffff80378844>{run_io_job+68}
> May 2 11:01:19 filer1 kernel: <ffffffff8037891c>{process_jobs+28} <ffffffff8013fdfa>{run_workqueue+155}
> May 2 11:01:19 filer1 kernel: <ffffffff8013fe41>{worker_thread+0} <ffffffff80143248>{keventd_create_kthread+0}
> May 2 11:01:19 filer1 kernel: <ffffffff8013ff46>{worker_thread+261} <ffffffff8012a872>{default_wake_function+0}
> May 2 11:01:19 filer1 kernel: <ffffffff80143248>{keventd_create_kthread+0} <ffffffff8012a872>{default_wake_function+0}
> May 2 11:01:19 filer1 kernel: <ffffffff80143248>{keventd_create_kthread+0} <ffffffff8014321f>{kthread+200}
> May 2 11:01:19 filer1 kernel: <ffffffff8010b89e>{child_rip+8} <ffffffff80143248>{keventd_create_kthread+0}
> May 2 11:01:19 filer1 kernel: <ffffffff80143157>{kthread+0} <ffffffff8010b896>{child_rip+0}
> May 2 11:01:19 filer1 kernel:
> May 2 11:01:19 filer1 kernel: Code: 48 8b 78 40 4c 89 d6 44 0f b7 8f 54 02 00 00 e9 e6 fd ff ff
> May 2 11:01:19 filer1 kernel: RIP <ffffffff80174ca6>{bio_add_page+22} RSP <ffff81007af9bcf0>
> May 2 11:01:19 filer1 kernel: CR2: 0000000000000040
> ----
>
> Hardware is dual xeon em64t on 64bit fedora3-based distro.
>
> --
> Gabriel Barazer <gabriel@oxeva.fr>
> OXEVA
> Tel: +33 (0) 478 37 12 05
> Fax: +33 (0) 472 56 50 49
>
>
> _______________________________________________
> 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/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Red Hat GmbH
Consulting Development Engineer Am Sonnenhang 11
Storage Development 56242 Marienrachdorf
Germany
Mauelshagen@RedHat.com PHONE +49 171 7803392
FAX +49 2626 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] Snapshot segfaults lvremove + bug kernel
2006-05-09 9:41 ` [linux-lvm] " Heinz Mauelshagen
@ 2006-05-09 18:15 ` Robin Bowes
2006-05-10 10:48 ` Heinz Mauelshagen
0 siblings, 1 reply; 8+ messages in thread
From: Robin Bowes @ 2006-05-09 18:15 UTC (permalink / raw)
To: mauelshagen, LVM general discussion and development
Heinz Mauelshagen wrote:
>
> this is a known issue with tearing down kcopyd jobs we're working on.
>
Heinz,
Do you have any idea when we might see a fix for this? Is the bug
present in later versions?
For example, I've got a box running FC4 that has this problem. If I
upgrade to FC5 am I likely to still see the problem?
Also, what's the best way to get rid of the snapshot volumes? I'm
currently planning to boot from a recovery disk that supports lvm and
run lvremove from there.
Thanks for any suggestions/advice,
R.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] Snapshot segfaults lvremove + bug kernel
2006-05-09 18:15 ` Robin Bowes
@ 2006-05-10 10:48 ` Heinz Mauelshagen
2006-05-10 11:10 ` Robin Bowes
2006-05-18 22:44 ` Robin Bowes
0 siblings, 2 replies; 8+ messages in thread
From: Heinz Mauelshagen @ 2006-05-10 10:48 UTC (permalink / raw)
To: Robin Bowes; +Cc: LVM general discussion and development, mauelshagen
On Tue, May 09, 2006 at 07:15:25PM +0100, Robin Bowes wrote:
> Heinz Mauelshagen wrote:
> >
> > this is a known issue with tearing down kcopyd jobs we're working on.
> >
>
> Heinz,
>
> Do you have any idea when we might see a fix for this? Is the bug
> present in later versions?
A fix has been provided ~2 weeks ago to lkml and was tested ok.
It is in the recent stable kernels.
>
> For example, I've got a box running FC4 that has this problem. If I
> upgrade to FC5 am I likely to still see the problem?
Yes.
>
> Also, what's the best way to get rid of the snapshot volumes? I'm
> currently planning to boot from a recovery disk that supports lvm and
> run lvremove from there.
That or using a n actual stable kernel *should* work,
because tearing down kcopyd jobs dies with the bug under load.
>
> Thanks for any suggestions/advice,
>
> R.
Regards,
Heinz -- The LVM Guy --
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Red Hat GmbH
Consulting Development Engineer Am Sonnenhang 11
Storage Development 56242 Marienrachdorf
Germany
Mauelshagen@RedHat.com PHONE +49 171 7803392
FAX +49 2626 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [linux-lvm] Snapshot segfaults lvremove + bug kernel
2006-05-10 10:48 ` Heinz Mauelshagen
@ 2006-05-10 11:10 ` Robin Bowes
2006-05-13 0:07 ` [linux-lvm] " Robin Bowes
2006-05-18 22:44 ` Robin Bowes
1 sibling, 1 reply; 8+ messages in thread
From: Robin Bowes @ 2006-05-10 11:10 UTC (permalink / raw)
To: LVM general discussion and development
Heinz Mauelshagen wrote:
> On Tue, May 09, 2006 at 07:15:25PM +0100, Robin Bowes wrote:
>> Do you have any idea when we might see a fix for this? Is the bug
>> present in later versions?
>
> A fix has been provided ~2 weeks ago to lkml and was tested ok.
> It is in the recent stable kernels.
Can you define "recent" so I know which to install.
>> For example, I've got a box running FC4 that has this problem. If I
>> upgrade to FC5 am I likely to still see the problem?
>
> Yes.
So, the FC5 kernels don't have the fix? Even in the Testing repos?
>> Also, what's the best way to get rid of the snapshot volumes? I'm
>> currently planning to boot from a recovery disk that supports lvm and
>> run lvremove from there.
>
> That or using a n actual stable kernel *should* work,
> because tearing down kcopyd jobs dies with the bug under load.
OK, thanks.
R.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [linux-lvm] Re: Snapshot segfaults lvremove + bug kernel
2006-05-10 11:10 ` Robin Bowes
@ 2006-05-13 0:07 ` Robin Bowes
0 siblings, 0 replies; 8+ messages in thread
From: Robin Bowes @ 2006-05-13 0:07 UTC (permalink / raw)
To: linux-lvm
Robin Bowes wrote:
> Heinz Mauelshagen wrote:
>> On Tue, May 09, 2006 at 07:15:25PM +0100, Robin Bowes wrote:
>>> Do you have any idea when we might see a fix for this? Is the bug
>>> present in later versions?
>> A fix has been provided ~2 weeks ago to lkml and was tested ok.
>> It is in the recent stable kernels.
>
> Can you define "recent" so I know which to install.
Heinz,
Any chance you can tell me which kernel versions contain the fix?
Thanks,
R.
^ permalink raw reply [flat|nested] 8+ messages in thread
* [linux-lvm] Re: Snapshot segfaults lvremove + bug kernel
2006-05-10 10:48 ` Heinz Mauelshagen
2006-05-10 11:10 ` Robin Bowes
@ 2006-05-18 22:44 ` Robin Bowes
1 sibling, 0 replies; 8+ messages in thread
From: Robin Bowes @ 2006-05-18 22:44 UTC (permalink / raw)
To: mauelshagen, LVM general discussion and development
Heinz Mauelshagen wrote:
> On Tue, May 09, 2006 at 07:15:25PM +0100, Robin Bowes wrote:
>> Heinz Mauelshagen wrote:
>>> this is a known issue with tearing down kcopyd jobs we're working on.
>>>
>> Heinz,
>>
>> Do you have any idea when we might see a fix for this? Is the bug
>> present in later versions?
>
> A fix has been provided ~2 weeks ago to lkml and was tested ok.
> It is in the recent stable kernels.
Heinz,
Can you point me at the bugzilla for this problem so I can track which
kernels have the fix?
Thanks,
R.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2006-05-18 22:44 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-02 9:32 [linux-lvm] Snapshot segfaults lvremove + bug kernel Gabriel Barazer
2006-05-08 22:19 ` [linux-lvm] " Robin Bowes
2006-05-09 9:41 ` [linux-lvm] " Heinz Mauelshagen
2006-05-09 18:15 ` Robin Bowes
2006-05-10 10:48 ` Heinz Mauelshagen
2006-05-10 11:10 ` Robin Bowes
2006-05-13 0:07 ` [linux-lvm] " Robin Bowes
2006-05-18 22:44 ` Robin Bowes
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).