[Top] [All Lists]

Re: file system defragmentation

To: linux-xfs@xxxxxxxxxxx
Subject: Re: file system defragmentation
From: Cosmo Nova <cs_mcc98@xxxxxxxxxxx>
Date: Tue, 18 Jul 2006 00:59:39 -0700 (PDT)
In-reply-to: <20060717141917.GY2114946@melbourne.sgi.com>
References: <4f52331f050826001612f8e323@mail.gmail.com> <20050826101131.GA24544@ii.uib.no> <4f52331f0508260848782f240a@mail.gmail.com> <43128F82.4010004@tlinx.org> <4312913F.6040205@coremetrics.com> <43311567.3060208@tlinx.org> <5356806.post@talk.nabble.com> <20060717141917.GY2114946@melbourne.sgi.com>
Sender: xfs-bounce@xxxxxxxxxxx
Hi, can I summarize by saying that, XFS still partition the volume into
different allocation groups, but there is NO locking. Two files may write in
the same allocation group and introduce fragments?
What is the maximum and typical number of allocation groups please? I can't
find the numbers in the source code...

And for the buffer, Is preallocation the same as delayed allocation? page
cache, as I remember belongs to Linux VFS. What are the memory / disk
requirement and sizing for the cache please? If a file space allocation is
delayed, what is the upper bound of the delayed size? Can files of MBs, GBs
being delayed allocate, and multiple channels/threads files all store in
memory?? How XFS's allocation works (with number please if possible) to help
tackle fragmentation?

View this message in context: 
Sent from the Xfs - General forum at Nabble.com.

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