On Thu, Oct 18, 2012 at 9:28 PM, Chris Mason <chris.ma...@fusionio.com> wrote: > > Usually when btrfs is slow to mount, or slow right after a mount it is > because we're regenerating the free space cache. This is slow enough > that you should be able to see the free space cache threads active even > after the initial boot is done. > > The good news is that you should be able to just let them finish > generating the cache and then the problem should go away. >
HI,Chris, yes...I did regenerate free_space last time Frederic told me to. the next boot after removing clear_cache from fstab is super slow. but after that boot, kernel still needs 135s to load... > If it isn't the free space cache, it'll be a fragmentation problem. The > easiest way to tell the difference is to get a few sysrq-w snapshots > during the boot. How can I "get a few sysrq-w snapshots" please? My btrfs is automatically created during openSUSE install, so I don't know which command I can use to do so...please forgive my freshness and stupidity... Marguerite -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
