Am Dienstag, 5. Januar 2016, 15:34:35 CET schrieb Duncan: > Christoph Anton Mitterer posted on Sat, 02 Jan 2016 06:12:46 +0100 as > > excerpted: > > On Fri, 2015-12-25 at 08:06 +0000, Duncan wrote: > >> I wasn't personally sure if 4.1 itself was affected or not, but the > >> wiki says don't use 4.1.1 as it's broken with this bug, with the > >> quick-fix in 4.1.2, so I /think/ 4.1 itself is fine. A scan with a > >> current btrfs check should tell you for sure. But if you meant 4.1.1 > >> and only typed 4.1, then yes, better redo. > > > > 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.
btrfs check from btrfs tools 4.3.1 on kernel 4.4-rc6 has not been able to fix these errors and I recreated the filesystem that had the errors. I think I mentioned it also in this thread. Thanks, -- Martin -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
