![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=776563 https://bugzilla.novell.com/show_bug.cgi?id=776563#c30 Marguerite Su <i@marguerite.su> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |dsterba@suse.com --- Comment #30 from Marguerite Su <i@marguerite.su> 2012-10-19 18:58:18 UTC --- It is solved! http://www.spinics.net/lists/linux-btrfs/msg19766.html I asked for help upstream. and they found the reason is:
It appears space_cache isn't enabled on your rootfs; can you do a "mount / -o remount,space_cache", sync a couple times, make some coffee, and then reboot, and see if it's better?
You should see two instances of "btrfs: disk space caching is enabled" in your dmesg, one for / and the second for /home.
Without space_cache (once), btrfs has to repopulate that information the slow way every mount; with it, it can just load the data from the last unmount (modulo some consistency checks).
The setting is sticky, so you don't actually need it in fstab any more (although it won't hurt anything either).
the solution is: UUID=9b9aa9d9-760e-445c-a0ab-68e102d9f02e / btrfs defaults,space_cache,comment=systemd.automount 1 0 UUID=559dec06-4fd0-47c1-97b8-cc4fa6153fa0 /home btrfs defaults,space_cache,comment=systemd.automount 1 0 which openSUSE has a different setting: defaults 1 2 it means it didn't enable cache for btrfs at all(so my last try of clear_cache didn't work, because there's no cache to clear). So David, can we make the setting above happen in openSUSE? * add "space_cache" to btrfs partition will make sure it enables cache. * 2->0 make sure it will not do fsck.btrfs. then we can restore fsck.btrfs to its normal function. Marguerite -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.