Open Stack

Am 01.05.2015 um 02:21 schrieb Samuel Merritt:
> 
> It seems like 1430268763.41931.data would be in the same allocation group as
> objects/757/a94/bd77129a1cae9e32381776e322efca94, and bd77129a1cae9e32381776e322efca94 would be in the same allocation
> group as objects/757/a94, and so on. Thus, everything would be in the same allocation group as the root directory.
> 
> This can't be the case, or else there'd be no point to allocation groups. What am I missing here?


Hi,

I think what you're missing is, that inodes stay in the allocation group where they first were created. So moving a file
around in the filesystem changes the path but not the allocation group. So first creating a temporary file and then
moving it into the hash folder leaves the file associated with the temp folder's allocation group, thus the allocation
group grows bigger and bigger and searching the allocation group takes more and more time.

Regards,

	Uwe