On Thu, 2020-07-09 at 13:32 -0700, Davide Cavalca via devel wrote: > On Thu, 2020-07-09 at 16:15 -0400, Simo Sorce wrote: > > However I have had bad kernels, power outages, loss of battery power > > (laptops on too long suspend) and other random reasons to force > > reboot > > a system. That has been the primary case of file system checks > > through > > my Fedora usage. And luckily so far I never had a loss of filesystem > > or > > data that way, fsck always ended up solving most of the issues, and > > whenever I lost file they ended up being temporary files I did not > > care > > for. > > > > I do not think those failures are common in Facebook fleets, so I am > > quite skeptical FB data and failure modes are representative of > > Fedora > > usage as a desktop/laptop OS and therefore of the behavior of btrfs > > in > > those cases. > > As someone on one of the teams at FB that has to deal with that, I can > assure you all the scenarios you listed can and do happen, and they > happen a lot. While we don't have the "laptop's out of battery" issue > on the production side, we have plenty of power events and unplanned > maintenances that can and will hit live machines and cut power off. > Force reboots (triggered by either humans or automation) are also not > at all uncommon. Rebuilding machines from scratch isn't free, even with > all the automation and stuff we have, so if power loss or reboot events > on machines using btrfs caused widespread corruption or other issues > I'm confident we'd have found that out pretty early on. Oh this is really good to know, it is more reassuring! Simo. -- Simo Sorce RHEL Crypto Team Red Hat, Inc _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
