On Thu, May 08, 2014 at 04:22:13PM +0200, Tomáš Pružina wrote: > I ran into some troubles with inode-cache rebuilding on root fs after > filesystem was mounted without inode_cache, which stalls boot of my > box by several minutes. > > I boot from commandline like: > root=/dev/sda4 rootfstype=btrfs > rootflags=inode_cache,space_cache,autodefrag rw ... > > However when I manually remount root fs without inode_cache (for > example via kexec), it triggers cache rebuild at next mount which > takes several tens of minutes and mimick 'freeze' on boot. > > Would it be possible to put some printk saying that this is happening > so users don't get confused about it??
Adding the printk is probably a good thing, but I'd rather reconsider using inode_cache at all. IMO it's supposed to fix problems with inode numbers that we don't have. https://btrfs.wiki.kernel.org/index.php/Project_ideas#Free_inode_number_cache "As the filesystem fills up, finding a free inode number will become expensive. This should be cached the same way we do free blocks." Without inode_cache the new inode number is a simple increment from the last number, in the 64bit space, per subvolume. We're not going to reach the limits anytime soon. The documentation does not say anything about that, I'll update the wiki. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
