xfs
[Top] [All Lists]

Re: fresh xfs vs used xfs

To: Deanan <delusion@xxxxxxxxxxxx>
Subject: Re: fresh xfs vs used xfs
From: Eric Sandeen <sandeen@xxxxxxx>
Date: Mon, 12 Sep 2005 12:47:12 -0500
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <4325B3C1.20506@xxxxxxxxxxxx>
References: <Pine.LNX.4.63.0509121822550.3870@xxxxxxxxxxxxxxx> <4325B3C1.20506@xxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (X11/20041206)
Deanan wrote:
Hi,

I'm seeing some strange things happen that i can't really explain.
I'm using the XFS with SLES 9 and 2.6.5-7.97 on x86_64.

I'm filling up 6TB in one shot with 16mb files. When I delete the
directory that contains all the files and then go back the to refill
the directory again, I get performance problems.

This may have to do with inode clusters left on-disk after you delete the associated files. Although xfs creates inode clusters dynamically, by default it does not delete them dynamically.

You might try mounting with the noikeep option to delete the inode clusters - however, a comment in the code still says that this may have some issues, so tread carefully.

Another thought is that since you are on a box which can handle 64-bit inodes, turn on the inode64 mount option; this will allow inode numbers to grow to 64 bits, and cause inodes & data to be allocated more uniformly across the filesystem. Note, however, that an xfs filesystem with 64-bit inodes will have trouble on a 32-bit kernel (if you boot 32-bit kernels on the box, or if you were to move the storage to a 32-bit box).

-Eric

Is this a problem with the logs?

Thanks,

Deanan



<Prev in Thread] Current Thread [Next in Thread>