[Top] [All Lists]

Re: file system defragmentation

To: linux-xfs@xxxxxxxxxxx
Subject: Re: file system defragmentation
From: Cosmo Nova <cs_mcc98@xxxxxxxxxxx>
Date: Wed, 19 Jul 2006 03:33:13 -0700 (PDT)
In-reply-to: <20060718213304.GA27287@xxxxxxxxxxxxxxxxxxxxx>
References: <4f52331f050826001612f8e323@xxxxxxxxxxxxxx> <20050826101131.GA24544@xxxxxxxxx> <4f52331f0508260848782f240a@xxxxxxxxxxxxxx> <43128F82.4010004@xxxxxxxxx> <4312913F.6040205@xxxxxxxxxxxxxxx> <43311567.3060208@xxxxxxxxx> <5356806.post@xxxxxxxxxxxxxxx> <20060717141917.GY2114946@xxxxxxxxxxxxxxxxx> <5374022.post@xxxxxxxxxxxxxxx> <20060718213304.GA27287@xxxxxxxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
If there are AG locks, but multiple files can write in the same AG, how "AG
lock" is interpreted by XFS then? What does it really do?

For pre-allocation and delayed allocation, do they belong to the feature set
of XFS? Or are they application dependant?

I am trying to compare filesystems, especially xfs vs jfs. I found that
jfs's per AG locking would only allow one file to be written per AG, which
helps a lot to prevent fragmentation (according to experiment results).
There're no pre-allocation and delayed allocation in JFS though. Comparing
the experiment results, XFS is doing a good job, giving 6-10 fragments
(compare to majority of single fragment in JFS...). So answers of the above
questions with numbers would help a lot. Thanks!
View this message in context: 
Sent from the Xfs - General forum at Nabble.com.

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