On Tue, May 17, 2016 at 07:46:33PM -0700, Martin McClure wrote: > On 05/12/2016 09:36 PM, Kent Overstreet wrote: > > > > Yeah - tiering replaces cache/backing devices > > > > IIRC, > > > > bcache format --tier 0 -C <SSD> --tier 1 -C <spinning rust> > > > > (the -C is going to go away at some point) > > > > Had a chance to play with this some more, but still not getting it to > work... > > Formatting seems to work, and once I do this: > > echo /dev/sdd1 > /sys/fs/bcache/register > echo /dev/nvme0n1 > /sys/fs/bcache/register > echo 1 > /sys/fs/bcache/<set-uuid>/blockdev_volume_create > > a /dev/bcache0 has been created. However, if I try to mount it: > > mount -t bcache /dev/bcache0 /mnt > > it says: > > mount: No such file or directory > > with a return code of 32, which is documented as "mount failure". > > At this point I reach the limit of my current understanding, but would > like to understand more. The intended mount path for multi device filesystems is currently broken... Chris got it working (to my surprise) by - I belive - registering all the devices via /sys/fs/bcache/register, and then mounting just one of the block devices - Chris, is that correct? FYI though: tiering mode is _not_ as well tested currently, and Chris managed to hit a bug when he completely filled up tier 0 and it then wouldn't mount, because the btree updates journal replay was doing wouldn't fit on tier 0 - and I haven't merged the fix I sent him because it was kind of a hack. But I just got back from vacation so I should be able to start working through these issues... -- 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
