Date: Wed, 15 May 2013 08:26:09 +0100 From: "Steven Hartland" <killing@multiplay.co.uk> To: "Ajit Jain" <ajit.jain@cloudbyte.com> Cc: freebsd-fs <freebsd-fs@freebsd.org> Subject: Re: seeing data corruption with zfs trim functionality Message-ID: <9681E07546D348168052D4FC5365B4CD@multiplay.co.uk> References: <CAA71u6Y5dKZ9O0rqxCpx-9t7DYgTnPZSoNy-iHOnmzrOUYp%2Bvw@mail.gmail.com> <60316751643743738AB83DABC6A5934B@multiplay.co.uk> <20130429105143.GA1492@icarus.home.lan> <3AD1AB31003D49B2BF2EA7DD411B38A2@multiplay.co.uk> <C6AA4D0A7C49469ABB3C7440B1BCC108@multiplay.co.uk> <CAA71u6Zh7BbbdC=utqfR2MD1Nn=9euUDXHKqqu9NyBG-Jx%2B=Ow@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Could you provide us with details on the tests your using so we can
run them here on current sources and see if we see any issues?
Regards
Steve
----- Original Message -----
From: "Ajit Jain" <ajit.jain@cloudbyte.com>
To: "Steven Hartland" <killing@multiplay.co.uk>
Cc: "freebsd-fs" <freebsd-fs@freebsd.org>
Sent: Wednesday, May 15, 2013 6:47 AM
Subject: Re: seeing data corruption with zfs trim functionality
> Hi Steven,
>
> Thanks for the follow-up.
> The code where I pulled in zfs trim patches is not updated to 9 stable
> specially the cam directory.
> I pulled in many dependent patches in order to apply the patches that you
> gave. After that all da devices
> CAM_PERIPH_INVALID in dadone() because read capability was returning a very
> big number (bigger than MAXPHYS)
> for the block size. I think this is because I have not update the code to 9
> stable (only pulled in required patches and miss
> some patches).
>
> So, I am planning to first update my code to 9stable and then try the same
> test again. That might take some time.
>
>
> thanks again,
> ajit
>
>
> On Wed, May 15, 2013 at 2:40 AM, Steven Hartland <killing@multiplay.co.uk>wrote:
>
>> ----- Original Message ----- From: "Steven Hartland"
>>
>> What version are you porting the changes to?
>>>>>
>>>>> What SSD are you using?
>>>>>
>>>>> What LSI controller are you using?
>>>>>
>>>>
>>>> I'd also like to see "zpool status" (for every pool that involves this
>>>> SSD) and "gpart show" against the disk itself.
>>>>
>>>
>>> Also:
>>> 1. What FW version is your LSI? You can get this from dmesg.
>>> 2. The exact command line your running iotest with?
>>>
>>
>> Any update on this? I'd like to try and replicate your test here so
>> would appreciate as much information as possible.
>>
>>
>> Regards
>> Steve
>>
>> ==============================**==================
>> This e.mail is private and confidential between Multiplay (UK) Ltd. and
>> the person or entity to whom it is addressed. In the event of misdirection,
>> the recipient is prohibited from using, copying, printing or otherwise
>> disseminating it or any information contained in it.
>> In the event of misdirection, illegible or incomplete transmission please
>> telephone +44 845 868 1337
>> or return the E.mail to postmaster@multiplay.co.uk.
>>
>>
>
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postmaster@multiplay.co.uk.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9681E07546D348168052D4FC5365B4CD>