Talk:Status

From btrfs Wiki
(Difference between revisions)
Jump to: navigation, search
(→‎Degraded mount fixes in 4.14)
(→‎could some one update or mark as obsolete)
Line 3: Line 3:
  
 
: 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. --[[User:Kdave|Kdave]] ([[User talk:Kdave|talk]]) 21:26, 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. --[[User:Kdave|Kdave]] ([[User talk:Kdave|talk]]) 21:26, 26 April 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. [[User:Kdave|Kdave]] ([[User talk:Kdave|talk]]) 12:20, 26 March 2019 (UTC)
 

Revision as of 14:27, 13 May 2022

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)
Retrieved from "https://btrfs.wiki.kernel.org/index.php?title=Talk:Status&oldid=33657"
Personal tools