From: Alasdair G Kergon <agk@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: BUG at drivers/md/kcopyd.c:146 (was: [PATCH 1/9] device-mapper snapshot: load metadata on creation)
Date: Thu, 20 Apr 2006 18:05:35 +0100 [thread overview]
Message-ID: <20060420170535.GA24524@agk.surrey.redhat.com> (raw)
In-Reply-To: <87odz3f5m0.fsf@blackdown.de>
On Sat, Apr 15, 2006 at 01:19:51PM +0200, Juergen Kreileder wrote:
> I'm using devmapper 1.02.03 and lvm2 2.02.02 with 2.6.16.2,
> nevertheless my logical volumes locked up three time when removing
> snapshots so far. Twice I got BUG at drivers/md/kcopyd.c:146, the
> third time logging stopped at the first lvremove.
> 2.6.15 and earlier kernels in combination with older tools worked fine
> over the last year.
I found several bugs in the snapshot code when I reviewed it,
including (thankfully hard-to-trigger) silent data corruption.
Patches went into 2.6.17-rc1. [There's one unfinished patch
outstanding for a theoretical race that I've only been able to
reproduce under artificial conditions.]
> kernel BUG at drivers/md/kcopyd.c:146!
Probably needs this patch (12th March):
dm snapshot: fix kcopyd destructor
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2006-04-20 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 21:11 [PATCH 1/9] device-mapper snapshot: load metadata on creation Alasdair G Kergon
2006-01-23 5:33 ` Andrew Morton
2006-01-23 15:34 ` Alasdair G Kergon
2006-04-15 11:19 ` BUG at drivers/md/kcopyd.c:146 (was: [PATCH 1/9] device-mapper snapshot: load metadata on creation) Juergen Kreileder
2006-04-20 17:05 ` Alasdair G Kergon [this message]
2006-04-20 19:48 ` Andrew Morton
2006-04-21 15:12 ` BUG at drivers/md/kcopyd.c:146 Juergen Kreileder
2006-04-24 18:31 ` Juergen Kreileder
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=20060420170535.GA24524@agk.surrey.redhat.com \
--to=agk@redhat.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®