Talk:Status

From btrfs Wiki
(Difference between revisions)
Jump to: navigation, search
(could some one update or mark as obsolete: new section)
(could some one update or mark as obsolete)
Line 13: Line 13:
 
At least up to 5.1, there was still the silent data corruption issue with compression found by Zygo...
 
At least up to 5.1, there was still the silent data corruption issue with compression found by Zygo...
 
Could some (as it was already asked for on the mailing list) upgrade this page that compression *is not stable* at all. Or at least mark the whole page as apparently not being properly updated anymore?
 
Could some (as it was already asked for on the mailing list) upgrade this page that compression *is not stable* at all. Or at least mark the whole page as apparently not being properly updated anymore?
 +
 +
What do you mean by not updated anymore? Check the logs. And 'not at all' is an overstatement. Zygo finds corner cases, that nobody else hits.

Revision as of 12:19, 26 March 2019

parity not checksummed removed

On Feb 27, kdave removed the "parity not checksummed" note for RAID56. Was this change made in Kernel 4.16? I don't see the word parity in Dave's pull request for that kernel. Is this just hiding in there under a different name? Or was it fixed earlier? Thanks Bobpaul (talk) 20:05, 26 April 2018 (UTC)

We had some discussions how to move forward with raid56, the parity checksum was found to be not necessary so I removed it from the list as a problem to fix. --Kdave (talk) 21:26, 26 April 2018 (UTC)

Degraded mount fixes in 4.14

The page mentions an issue with degraded mounts where you can get stuck in irreversible read-only mode. If I am not mistaken, the issue has been fixed by the commits 21634a19 & 4330e183 which have been included in the 4.14 kernel. Isn't this the case? Marios Titas (talk) 01:10, 16 November 2018 (UTC)

Good point, I'll update the status, thanks! Kdave (talk) 14:11, 16 November 2018 (UTC)

could some one update or mark as obsolete

At least up to 5.1, there was still the silent data corruption issue with compression found by Zygo... Could some (as it was already asked for on the mailing list) upgrade this page that compression *is not stable* at all. Or at least mark the whole page as apparently not being properly updated anymore?

What do you mean by not updated anymore? Check the logs. And 'not at all' is an overstatement. Zygo finds corner cases, that nobody else hits.

Personal tools