SATA trace shows device behaving correctly.
btrfs repair --ignore-errors /dev/sda2 /tmp/ will yield files that are
not verifiable by FIO, and differ from the original files on the
internal drive that they were copied from at the failing offset.
On Wed, Oct 19, 2016 at 3:39 PM, Martin Dev
; On Mon, 10 Oct 2016 10:44:39 +0100
>> Martin Dev <mrturtle...@gmail.com> wrote:
>>
>>> I work for system verification of SSDs and we've recently come up
>>> against an issue with BTRFS on Ubuntu 16.04
>>
>>> This seems to be a recent change
>
After some investigation this seems to follow the discard flag set in fstab.
9 or so reproductions with discard on partition 2 fail
move discard flag to partition 1, then partition 1 fails.
Re-running our tests with no discard options set in fstab
On Mon, Oct 10, 2016 at 1:02 PM, Martin Dev
, Oct 10, 2016 at 10:44 AM, Martin Dev <mrturtle...@gmail.com> wrote:
> Hey everyone,
>
> I work for system verification of SSDs and we've recently come up
> against an issue with BTRFS on Ubuntu 16.04. We have a framework which
> follows the following steps:
>
> Ge
Hey everyone,
I work for system verification of SSDs and we've recently come up
against an issue with BTRFS on Ubuntu 16.04. We have a framework which
follows the following steps:
Generate verifiable 10GB file with FIO on internal drive
Copy 10GB file to 2 target partitions on DUT (using "cp"
