On Tue, 2016-01-05 at 15:34 +0000, Duncan wrote: > >What exactly was that bug in 4.1.1 mkfs and how would one notice > > that > > one suffers from it? > > I created a number of personal filesystems that I use > > "productively" and > > I'm not 100% sure during which version I've created them... :/ > > > > Is there some easy way to find out, like a fs creation time stamp?? > > I believe a current btrfs check will flag the errors, but can't fix > them, > as the problem was in the filesystem creation and is simply too deep > to > fix, so the bad filesystems must be wiped and recreated with a > mkfs.btrfs > without the bug, to fix. If I didn't mix things up, there was a post by someone just few days ago, which showed the error that would pop up on fsck.
> the > people volunteering (directly or indirectly) to do that coding > scratch, > or choose not to scratch by spending their time and/or resources > elsewhere, their own itches in the priority they choose. Sure that,'s all clear. And obviously I didn't want to distract anyone from working on it. It's just if those people wouldn't care on which part of btrfs they're working,... than I'd have considered btrfs-convert rather just a nice- to have. > It's the same reason that I as a kde user who finds the gnome "dumb- > down" > approach horribly frustrating, remain extremely glad there's a gnome > project for those who approve of that sort of approach to work on -- I'd rather have wished that all those guys get hired by Apple or MS ;-) Cheers, Chris.
smime.p7s
Description: S/MIME cryptographic signature
