xfs
[Top] [All Lists]

Re: Configuring large XFS filesystem

To: "Kevin P. Fleming" <kpfleming@xxxxxxx>
Subject: Re: Configuring large XFS filesystem
From: "Harald Wagener" <hwagener@xxxxxxxxxxxxxxx>
Date: Fri, 12 Sep 2003 10:09:58 +0200
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <3F613BE3.6000507@xxxxxxx>
References: <3F613BE3.6000507@xxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx

On Freitag, 12. September 2003, at 05:22vorm., Kevin P. Fleming wrote:

I've been using XFS for a while now on Linux, but never on a filesystem larger than about 60GB or so. Tomorrow I need to configure a disk array for a client with a single XFS filesystem. The total size of the filesystem will be approximately 300GB, and it needs to be able hold 1.5-2.0 million files at any one time. There are no database work loads or transaction processing workloads, it's just a big fat file server for their network. They store a wide range of file sizes, but at least 50% of the files will be less than 32KB in size. The filesystem will be shared out using Samba 3.0, and there will be limited usage of extended attributes and ACLs through Samba (but probably no more than a couple thousand files, unless Samba decides to put extended attributes on things I'm not aware of yet).

The server is running kernel 2.6.0-test5. Anyone have any suggestions on configuring the filesystem? I hesitate to just use mkfs.xfs defaults for something this large, and I certainly don't want them to run out of space for new files/directories when the system is not full.




We have something similar like that running over here. We just took the standard mkfs.xfs for a 400 Gigabyte data store that is accessed via netatalk and samba (still on 2.2.x, but that is going to change soon...). So far, our problems did not come from xfs, but from interop problems between samba, netatalk, and various versions of client operating systems.

Regards,
    Harald

P.S.: Is there any advice on filesystem care after two years of continuous usage of an xfs file system? (except for backups, which we do of course). - H.


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