All of lore.kernel.org
 help / color / mirror / Atom feed
From: "aluno3@poczta.onet.pl" <aluno3@poczta.onet.pl>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: Calltrace in dm-snapshot in 2.6.27 kernel
Date: Wed, 22 Oct 2008 15:37:21 +0200	[thread overview]
Message-ID: <48FF2C91.4080401@poczta.onet.pl> (raw)
In-Reply-To: <Pine.LNX.4.64.0810211736230.24588@hs20-bc2-1.build.redhat.com>

Hi

I used your patch and I ran test the same workload. After a few hours
test, everything is OK. Is it possible? Test is still running.When I get
something wrong from kernel I write to You again.



Mikulas Patocka wrote:
> Hi
>
> Run the same workload and try this patch (also keep the previous patch 
> applied).
>
> Note, that the patch is not correct (it leaks a little bit of memory when 
> you deactivate a snapshot, also it will cause an error if you rmmod 
> dm-snapshot), I just want to see if you get any more crashes with this.
>
> Mikulas
>
>   
>> My workload in case of 32b involved only one volume and 3 snapshots to
>> this volume. I wrote only to origin volume (with use fstress) and I
>> created and deleted these snapshots from time to time. Snapshots was
>> mount with rw option.
>>
>> In case 64b I had 2 volume and 10 snapshots for each volume.I created
>> and deleted these snapshots from time to time as well. I wrote only to
>> origin volumes (with use dd)
>>
>> I don`t remember exactly but in case test with 1 snapshot per volume all
>> was working correctly through a few hours and I stopped this test but in
>> case my above tests system was working correctly through a few minutes.
>>  
>> Mikulas Patocka wrote:
>>     
>>>> Hi Mikulas
>>>>
>>>> I send to You (in attachment) files from both kernels.Thank You for help
>>>>
>>>> Best
>>>>     
>>>>         
>>> Thanks. Does your workload involve just one snapshot of a given volume, or 
>>> do you have more snapshots of the same volume? Do you write only to origin 
>>> or to both origin and the snapshot or only to the snapshot?
>>>
>>> I will send you some patch with more debug tests soon, just answer these 
>>> questions first, so that I can make it.
>>>
>>> Mikulas
>>>       
>
> ---
>  drivers/md/dm-snap.c |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> Index: linux-2.6.27-clean/drivers/md/dm-snap.c
> ===================================================================
> --- linux-2.6.27-clean.orig/drivers/md/dm-snap.c	2008-10-21 23:38:49.000000000 +0200
> +++ linux-2.6.27-clean/drivers/md/dm-snap.c	2008-10-21 23:39:09.000000000 +0200
> @@ -736,12 +736,12 @@ static void snapshot_dtr(struct dm_targe
>  
>  	__free_exceptions(s);
>  
> -	mempool_destroy(s->pending_pool);
> +	/*mempool_destroy(s->pending_pool);*/
>  
>  	dm_put_device(ti, s->origin);
>  	dm_put_device(ti, s->cow);
>  
> -	kfree(s);
> +	/*kfree(s);*/
>  }
>  
>  /*
>
>   

  reply	other threads:[~2008-10-22 13:37 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
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 [this message]
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=48FF2C91.4080401@poczta.onet.pl \
    --to=aluno3@poczta.onet.pl \
    --cc=dm-devel@redhat.com \
    --cc=mpatocka@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.