On  2016-05-21[1],  I  began playing with btrfs. I haven't really done
 anything with it since then, except for using it in  all  of  my  Arch
 Linux VMs by default.  (Remember, I use overqemu[2] quite often.)

 Bad news. Sometimes, a VM crashes. That crash is not related to btrfs.
 But after the crash, the  file  system  is  corrupt.  It's  not  being
 recognized  as  corrupt  on  boot  (I'd  expect that to happen and I'd
 expect some kind of fsck to repair it),  the  system  sometimes  still
 boots  and  only  some  file  actions  fail, like running a particular
 program.

 Am I supposed to manually check the FS after each boot?

 Either I'm doing something very wrong here, or btrfs is not yet  ready
 for prime time.

 ____________________

 1. gopher://uninformativ.de/0/twitpher/2016-05/2016-05-21.txt

 2. https://github.com/vain/bin-pub/blob/master/overqemu

You are viewing proxied material from uninformativ.de. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.