[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [dm-devel] Calltrace in dm-snapshot in 2.6.27 kernel
- From: aluno3 <aluno3 poczta onet pl>
- To: Mikulas Patocka <mpatocka redhat com>
- Cc: device-mapper development <dm-devel redhat com>
- Subject: Re: [dm-devel] Calltrace in dm-snapshot in 2.6.27 kernel
- Date: Tue, 21 Oct 2008 20:42:40 +0200
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
>
>
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]