On Mon, Dec 09, 2013 at 10:28:07AM +0100, Steinar H. Gunderson wrote: > On Sun, Dec 08, 2013 at 10:13:05PM -0500, Mike Snitzer wrote: > > This was fixed with this commit: > > http://git.kernel.org/cgit/linux/kernel/git/device-mapper/linux-dm.git/commit/?h=for-next&id=47821767d26af4073fcfdfb3b96704f24a23416f > > > > I'll be sending it to Linus at some point this coming week (along with > > other DM fixes that are staged in the 'for-next' branch of > > linux-dm.git). > > OK. Will applying this actually make my machine boot again, too? check_cache > says there's nothing wrong with it, just like last time; dump-cache says > everything's clean, just like last time. But I'm not nuking it once more, > the backup restore process was too painful last time :-) My gut feel is you're running out of metadata space for some reason. How big is your metadata device? (Obviously this is no excuse for the crashing). I'm really surprised that cache_dump is giving wrong information; saying everything is clean, saying you were using the cleaner policy etc. Are you sure you're passing it the right metadata dev? - Joe -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
