All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: Calltrace in dm-snapshot in 2.6.27 kernel
Date: Mon, 20 Oct 2008 10:43:04 +0200	[thread overview]
Message-ID: <48FC4498.5070706@redhat.com> (raw)
In-Reply-To: <48FC23DE.5040000@poczta.onet.pl>

aluno3@poczta.onet.pl wrote:
> I've got this calltrace from our QA team. They say that they mad few
> snapshots, run several programs like bacula or rsync and that calltrace
> is appearing about 1 hour after starting those programs.

Hi,
if it is reproducible, please can you try if this patch helps?
http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/dm-snapshot-fix-primary_pe-race.patch

Probably the same problem reported here
http://bugzilla.kernel.org/show_bug.cgi?id=11636

(Added Mikulas to CC)

Milan
--
mbroz@redhat.com

  reply	other threads:[~2008-10-20  8:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20  6:23 Calltrace in dm-snapshot in 2.6.27 kernel aluno3
2008-10-20  8:43 ` Milan Broz [this message]
2008-10-21  6:39   ` aluno3
2008-10-21 13:55     ` Mikulas Patocka
     [not found]       ` <48FDFF53.5080007@poczta.onet.pl>
2008-10-21 17:22         ` Mikulas Patocka
2008-10-21 18:42           ` aluno3
2008-10-21 21:43             ` Mikulas Patocka
2008-10-22 13:37               ` aluno3
2008-10-22 15:45                 ` Mikulas Patocka
2008-10-22 16:39                   ` Mikulas Patocka
2008-10-23 11:30                     ` aluno3
2008-10-23 13:40                       ` Mikulas Patocka
2008-11-19  8:31                         ` aluno3
2008-11-24 10:52                           ` Mikulas Patocka
2008-11-26  7:38                             ` aluno3
2008-11-28  7:28                               ` aluno3
2008-12-02  2:10                                 ` Mikulas Patocka

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=48FC4498.5070706@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-devel@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.