On Sat, Jan 9, 2021 at 7:34 AM Chris Murphy <li...@colorremedies.com> wrote: > > Strong likelihood that it can be fixed. But if the user data is > important we should do a btrfs restore first. That's a safe read-only > operation, does not change the file system like fsck which always has > risk. >
Doesn't it make more sense to use ddrescue and make a filesystem image ? I mean if the fsck makes things worse then I can restore with ddrescue. Rather than taking a btrfs restore it's better I take an image right ? > > > Also is the fix for my particular problem being worked on by the devs > > at the particular moment ? > > Yes. > That's pretty cool. But what happens when BTRFS crashes on me again ? I mean, this is the reason I keep complaining that BTRFS is not stable enough. I can't keep complaining to you or the devs each time the filesystem crashes on me, can I. > > It's actually an unusual failure, so it is an edge case. I'm happy to > discuss this part later. Priority is to get your data backed up, and > fix the file system. > So is this a problem of my machine/firmware or a problem in BTRFS itself ? I am either extremely lucky or extremely unlucky if I have spotted an error in the filesystem itself. > > I saw your message today on IRC and replied about 15 seconds later but > didn't get a reply. Anyway, next email I'll write up a procedure. Apologies, I must have missed it. I think you message me around 1 in the morning in Indian Standard Time. -- Regards, Sreyan Chakravarty _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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/users@lists.fedoraproject.org
