On Wed, 21 Jun 2017, Nix wrote: > On 20 Jun 2017, Eric Wheeler uttered the following: > > > On Mon, 5 Jun 2017, Igor Pavlenko wrote: > > > >> [ 45.941155] bcache: register_bdev() registered backing device sda3 > >> [ 46.138238] bcache: error on 471776aa-1b34-4eff-ba7d-509a9554b43d: > >> inconsistent ptrs: mark = 3, level = 0, disabling caching > > > > ^^^ > > > > This is the reason, something was inconsistent enough that it couldn't > > continue. Kent, do you know what this means in detail, and can you guess what might have caused it? > I'm rather worried about this sort of thing, given that I got it after > my first cache population and less than a week using bcache in anger. Do you have a difference between `blockdev --getpbsz /dev/cache` vs /dev/bdev (or whatever your devices are named) ? The physical blocksize must be the same as the cachedev IIRC. If 4k, use -w 4k in make-bcache. There's a thread somewhere discussing those details. -- Eric Wheeler > > The system in question is an oldie that restarts by mounting as much as > it can readonly and then doing a reboot (when bcache would routinely > whine about timeouts): the things it manages to remount readonly does > not usually include / is bcache usually unhappy about this sort of > thing? Would it prefer it if I was able to unmount it properly? If so, > it's time to upgrade that machine... it's only that I've had an oops > before now when stopping bcaches (early in test, not preserved because I > thought I'd made a mistake), so I thought it might be unhappy about > *that*, as well. > > -- > NULL && (void) > -- 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
