Franziska Näpelt posted on Thu, 26 Jun 2014 13:06:35 +0200 as excerpted: > There are a lot of following messages: > btrfs free space inode generation (0) did not match free space cache > generation Well, set of messages at least is somewhat expected after a hard shutdown, and shouldn't be a problem as the filesystem should rebuild the cache. In fact, that space_cache rebuild might be why you were seeing such high I/O after the reboot and fresh mount. If the space-cache rebuild is all the problems you see, you may be lucky, and the hard-terminated delete and reboot might not have resulted in any permanent damage. OTOH, if it seems the space_cache rebuild is interfering with further activity for too long and you end up doing another hard reset anyway, there's the nospace_cache mount option to turn it off. (Just a user and list regular with that single comment... I'll let you get back to the expert help now.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
