Am Mon, 12 Sep 2016 04:36:07 + (UTC)
schrieb Duncan <1i5t5.dun...@cox.net>:
> Again, I once thought all this was just the stage at which btrfs was,
> until I found out that it doesn't seem to happen if btrfs compression
> isn't being used. Something about the way it recovers from checksum
Hans van Kranenburg posted on Sun, 11 Sep 2016 22:49:58 +0200 as
excerpted:
> So, you can use a lot of compress without problems for years.
>
> Only if your hardware is starting to break in a specific way, causing
> lots and lots of checksum errors, the kernel might not be able to handle
> all
On 2016-09-12 05:48, Martin Steigerwald wrote:
Am Sonntag, 26. Juni 2016, 13:13:04 CEST schrieb Steven Haigh:
On 26/06/16 12:30, Duncan wrote:
> Steven Haigh posted on Sun, 26 Jun 2016 02:39:23 +1000 as excerpted:
>> In every case, it was a flurry of csum error messages, then instant
>> death.
On 09/11/2016 09:48 PM, Martin Steigerwald wrote:
> Am Sonntag, 26. Juni 2016, 13:13:04 CEST schrieb Steven Haigh:
>> On 26/06/16 12:30, Duncan wrote:
>>> Steven Haigh posted on Sun, 26 Jun 2016 02:39:23 +1000 as excerpted:
In every case, it was a flurry of csum error messages, then instant
On Sun, Sep 11, 2016 at 2:06 PM, Adam Borowski wrote:
> On Sun, Sep 11, 2016 at 09:48:35PM +0200, Martin Steigerwald wrote:
>> Hmm… I found this from being referred to by reading Debian wiki page on
>> BTRFS¹.
>>
>> I use compress=lzo on BTRFS RAID 1 since April 2014 and I
On Sun, Sep 11, 2016 at 09:48:35PM +0200, Martin Steigerwald wrote:
> Hmm… I found this from being referred to by reading Debian wiki page on
> BTRFS¹.
>
> I use compress=lzo on BTRFS RAID 1 since April 2014 and I never found an
> issue. Steven, your filesystem wasn´t RAID 1 but RAID 5 or 6?
>
Am Sonntag, 26. Juni 2016, 13:13:04 CEST schrieb Steven Haigh:
> On 26/06/16 12:30, Duncan wrote:
> > Steven Haigh posted on Sun, 26 Jun 2016 02:39:23 +1000 as excerpted:
> >> In every case, it was a flurry of csum error messages, then instant
> >> death.
> >
> > This is very possibly a known bug