On Thu, Mar 16, 2017 at 04:16:29PM +0100, Marcin wrote: > Hi! > It's good to hear that silence on mailinglist doesn't mean that there is no > changes in developing bcachefs! Join the irc channel! It's pretty active. > I found some problems with bcache tools. > bcache fsck errors: > > a) if I creat4e filesystem and run fsck before first mount I'm getting: > # bcache fsck /dev/sdd1 > initializing new filesystem > error opening /dev/sdd1: cannot allocate new btree root > > b) After first mount%umount fsck still doesn't work: > # bcache fsck /dev/sdd1 > no journal entries found > filesystem contains errors, but repair impossible > error opening /dev/sdd1: fsck error Man, you have a talent for finding bugs :) I've reproduced it, working on it now. > Is bcache fsck able to do fsck on tiered devices? Yes - just pass it all the devices, e.g. bcache fsck /dev/sdb /dev/sdc Also, keep in mind fsck is still run by default at mount time, there's normally no need to use userspace fsck (and running fsck in userspace and then mounting will be slower than just mounting and running fsck then, due to mount still having to scan all the metadata which will be cache cold). > I know that there is some stability problem with tiered devices because when > I mounted tiered fs and started to copy files on it the host rebooted after > some time. I have to run netconsole to catch what kernel says, then I post > it on ML. You might have been hitting a bug in a recent patch to improve readpages performance - I backed it out last night after I discovered it. > And I'm still missing compression saves free space on disk:) Yeah, that's something I've been wanting to get to, but people have been badgering me for replication more :) -- To unsubscribe from this list: send the line "unsubscribe linux-bcache" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
