| To: | linux-xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: file system defragmentation |
| From: | Cosmo Nova <cs_mcc98@xxxxxxxxxxx> |
| Date: | Mon, 17 Jul 2006 00:36:09 -0700 (PDT) |
| In-reply-to: | <43311567.3060208@xxxxxxxxx> |
| References: | <4f52331f050826001612f8e323@xxxxxxxxxxxxxx> <20050826101131.GA24544@xxxxxxxxx> <4f52331f0508260848782f240a@xxxxxxxxxxxxxx> <43128F82.4010004@xxxxxxxxx> <4312913F.6040205@xxxxxxxxxxxxxxx> <43311567.3060208@xxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
Hi, you mentioned delayed allocation. What is the size of the buffer holding the data, before they're actually written to disk? How can it tackle growing files? If I have a DVR system of 16 channels. They keep writing data to the disk in pieces of video files. I read some spec of xfs. Apart from extend-based allocation, there're allocaiton groups in xfs. I would like to ask, does XFS's allocation groups work similar as JFS's, which would lock an allocation group for individual file write? How does the allocation group in XFS work? And how would it help the fragmentation problem? Thankyou! -- View this message in context: http://www.nabble.com/file-system-defragmentation-tf255485.html#a5356806 Sent from the Xfs - General forum at Nabble.com. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS and write barrier, Chris Wedgwood |
|---|---|
| Next by Date: | Re: XFS failure, Martin Steigerwald |
| Previous by Thread: | XFS failure, Michel |
| Next by Thread: | Re: file system defragmentation, David Chatterton |
| Indexes: | [Date] [Thread] [Top] [All Lists] |