From mboxrd@z Thu Jan 1 00:00:00 1970 From: aluno3 Subject: Re: Calltrace in dm-snapshot in 2.6.27 kernel Date: Tue, 21 Oct 2008 20:42:40 +0200 Message-ID: <48FE22A0.30005@poczta.onet.pl> References: <48FC23DE.5040000@poczta.onet.pl> <48FC4498.5070706@redhat.com> <48FD7911.1000705@poczta.onet.pl> <48FDFF53.5080007@poczta.onet.pl> Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Mikulas Patocka Cc: device-mapper development List-Id: dm-devel.ids 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 > >