Dear Duncan! Thanks very much for your exhaustive answer.
Hm, I also thought of fragmentation. Alhtough I don't think this is really very likely, as my server doesn't serve things that likely cause fragmentation. It is a mailserver (but only maildir-format), fileserver for windows clients (huge files that hardly don't get rewritten), a server for TV-records (but only copy recordings from a sat receiver after they have been recorded, so no heavy rewriting here), a tiny webserver and all kinds of such things, but not a storage for huge databases, virtual machines or a target for filesharing clients. It however serves as a target for a hardlink-based backupprogram run on windows PCs, but only once per month or so, so that shouldn't bee too much. The problem must lie somewhere on the root partition itslef, because the system is already slow before mounting the fat data-partitions. I'll give the defragmentation a try. But # sudo btrfs filesystem defrag -r doesn't work, because "-r" is an unknown option (I'm running Btrfs v0.20-rc1 on an Ubuntu 3.11.0-14-generic kernel). I'm doing a # sudo btrfs filesystem defrag / & on the root directory at the moment. Question: will this defragment everything or just the root-fs and will I need to run a defragment on /home as well, as /home is a separate btrfs filesystem? I've also added autodefrag mountoptions and will do a "mount -a" after the defragmentation. I've considered a # sudo btrfs balance start as well, would this do any good? How close should I let the data fill the partition? The large data partitions are 85% used, root is 70% used. Is this safe or should I add space? Thanx, Wolfgang -- 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
