Btrfs devel - Apr 2014 - Is there any way to determine fragmentation for compressed btrfs volumes?

Hi,

I've been running btrfs on my SSD powered laptop for about a year and
a half  (with force-compress=lzo and autodefrag) and it seems the
volume has degraded quite a lot although I am not using snapshot
functionality.
No matter what I do (scrub, defrag ob the whole volume), files seem to
stay highly fragmented - at least that is my guess.
When e.g. starting up X11+XFCE the hdd led is lid for about 10s (the
Samsung 830 can do up to 80k/iops random read), also starting
google-chrome results in an active SSD for ~5s (although the chrome
binary + libs is for sure < 200mb, so should be loaded in 500ms).

What I wonder is how can I diagnose whats happening and why the FS is
rather slow?
The only target value I know is the extend count,  which doesn't seem
to be meaningful when using fragmentation.

Thank you in advance, Clemens Eisserer
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html