On 06/09/2016 10:52 AM, Marc Haber wrote:
On Thu, Jun 09, 2016 at 01:10:46AM +0200, Hans van Kranenburg wrote:
So, instead of being the cause, apt-get update causing a new chunk to be
allocated might as well be the result of existing ones already filled up
with too many fragments.
The next question is what files these extents belong to. To find out, I need
to open up the extent items I get back and follow a backreference to an
inode object. Might do that tomorrow, fun.
Does your apt use pdiffs to update the packages lists? If yes, I'd try
turning it off just for the fun of it and to see whether this changes
btrfs' allocation behavior. I have never looked at apt's pdiff stuff
in detail, but I guess that it creates many tiny temporary files.
No, it does not:
Acquire::Pdiffs "false";
--
Hans van Kranenburg - System / Network Engineer
Mendix | Driving Digital Innovation | www.mendix.com
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
