From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dennis Yang Subject: Re: Possible data corruption with dm-thin Date: Tue, 6 Sep 2016 12:51:28 +0800 Message-ID: References: <20160624135510.GA13946@roamer.bos.redhat.com> <20160701131856.GB32440@roamer.bos.redhat.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2883992202260472129==" Return-path: In-Reply-To: <20160701131856.GB32440@roamer.bos.redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Dennis Yang , device-mapper development List-Id: dm-devel.ids --===============2883992202260472129== Content-Type: multipart/alternative; boundary=047d7b874df4e85659053bcf8de8 --047d7b874df4e85659053bcf8de8 Content-Type: text/plain; charset=UTF-8 Hi Joe, Sorry for the late reply. We have been fixing bugs and conducting many experiments with heavy I/O to verify the correctness and stability of our storage. This problem I mentioned in this thread cannot be reproduced anymore with these two patches (I applied them back to 3.19.8 and 4.2.8 and both work fine). Thanks for your help. Dennis 2016-07-01 21:18 GMT+08:00 Edward Thornber : > Hi Dennis, > > Sorry to take so long about getting back to you. There was a bug in > the btree library that I mistakenly thought was caused by my fix for > your problem. Anyway, could you try and recreate your problem with > these two patches applied please (patches are against v4.7-rc5 + my > usual thin-dev extras): > > https://github.com/jthornber/linux-2.6/commit/ > ebdd99fc12acd0e9178831549896633171d5af1d > https://github.com/jthornber/linux-2.6/commit/ > c05989b59d091270c2bf7dd05bdb7a3575223529 > > Thanks, > > - Joe > -- Dennis Yang QNAP Systems, Inc. Skype: qnap.dennis.yang Email: dennisyang@qnap.com Tel: (+886)-2-2393-5152 ext. 15018 Address: 13F., No.56, Sec. 1, Xinsheng S. Rd., Zhongzheng Dist., Taipei City, Taiwan --047d7b874df4e85659053bcf8de8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Joe,

Sorry for the late reply. We ha= ve been fixing bugs and conducting many experiments with heavy I/O to verif= y the correctness and stability of our storage. This problem I mentioned in= this thread cannot be reproduced anymore with these two patches (I applied= them back to 3.19.8 and 4.2.8 and both work fine).

Thanks for your help.

Dennis=C2=A0

2016-07-01 21:18 GM= T+08:00 Edward Thornber <thornber@redhat.com>:
Hi Dennis,

Sorry to take so long about getting back to you.=C2=A0 There was a bug in the btree library that I mistakenly thought was caused by my fix for
your problem.=C2=A0 Anyway, could you try and recreate your problem with these two patches applied please (patches are against v4.7-rc5 + my
usual thin-dev extras):

=C2=A0 =C2=A0 = https://github.com/jthornber/linux-2.6/commit/ebdd99fc12acd0e9178= 831549896633171d5af1d
=C2=A0 =C2=A0 = https://github.com/jthornber/linux-2.6/commit/c05989b59d091270c2b= f7dd05bdb7a3575223529

Thanks,

- Joe



--
De= nnis Yang=C2=A0=C2=A0
QNAP Systems, Inc.
Skype:= qnap.dennis.yang
Email:
=C2=A0dennisyang@qnap.com
Tel:=C2=A0= (+886)-2-2393-5152 ext.=C2=A015018
Address:=C2=A013F., No.56, Sec. 1, Xinsheng S. Rd., Zhongzheng Di= st., Taipei City, Taiwan
--047d7b874df4e85659053bcf8de8-- --===============2883992202260472129== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============2883992202260472129==--