I thought this was fixed, but apparently only on Ubuntu. See [1]; the state is still “NEW" Regards, Hans [1] https://patchwork.kernel.org/patch/9600121/ > On Nov 7, 2017, at 3:37 AM, Campbell Steven <casteven@xxxxxxxxx> wrote: > > Hi, > > I've been doing some testing so that we can move from a 4.7 kernel up > to 4.14 at some point in the future. > > One thing I've noticed is that the numbering of the bcache devices is > quite different, is there a reason it's going 0,16,32 etc.? > > [Tue Nov 7 13:41:54 2017] bcache: bch_cached_dev_attach() Caching > sdb1 as bcache0 on set 030a5f1b-b314-482f-ba91-be1d712a4a33 > [Tue Nov 7 14:32:45 2017] bcache: bch_cached_dev_attach() Caching > sda1 as bcache16 on set 07cd8359-1427-4446-9688-d67ceb4f4b4c > [Tue Nov 7 14:36:36 2017] bcache: bch_cached_dev_attach() Caching > sdc1 as bcache32 on set 030a5f1b-b314-482f-ba91-be1d712a4a33 > > Thanks > > Campbell > -- > 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 -- 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
