Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*file\s+system\s+defragmentation\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*file\s+system\s+defragmentation\s*$/: 51 ]

Total 51 documents matching your query.

1. Re: file system defragmentation (score: 1): Author: David Chinner <dgc@xxxxxxx>; Date: Wed, 9 Aug 2006 09:34:25 +1000; Sure it is. The limit on how much is buffered before writeback (and therefore allocation) is determined by how much memory you have and your /proc/sys/vm/dirty* tunable settings. This can range from; /archives/xfs/2006-08/msg00064.html (8,135 bytes)
2. Re: file system defragmentation (score: 1): Author:; Date: Wed, 9 Aug 2006 09:34:25 +1000; Sure it is. The limit on how much is buffered before writeback (and therefore allocation) is determined by how much memory you have and your /proc/sys/vm/dirty* tunable settings. This can range from; /archives/xfs/2006-08/msg00316.html (8,135 bytes)
3. Re: file system defragmentation (score: 1): Author: Cosmo Nova <cs_mcc98@xxxxxxxxxxx>; Date: Mon, 17 Jul 2006 00:36:09 -0700 (PDT); 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.; /archives/xfs/2006-07/msg00146.html (8,717 bytes)
4. Re: file system defragmentation (score: 1): Author: David Chatterton <chatz@xxxxxxxxxxxxxxxxx>; Date: Mon, 17 Jul 2006 19:32:30 +1000; Cosmo Nova wrote: 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? I'll leave the detai; /archives/xfs/2006-07/msg00150.html (10,666 bytes)
5. Re: file system defragmentation (score: 1): Author: David Chinner <dgc@xxxxxxx>; Date: Tue, 18 Jul 2006 00:19:17 +1000; No special buffering is needed in XFS as the page cache does it all for us. delalloc means that XFS does not allocate until the data gets written to disk (i.e. flushed from the cache). The size of th; /archives/xfs/2006-07/msg00157.html (9,080 bytes)
6. Re: file system defragmentation (score: 1): Author: Chris Wedgwood <cw@xxxxxxxx>; Date: Mon, 17 Jul 2006 12:08:27 -0700; I did some work for someone who does a similar thing (they write 96 channels in parallel and have to be able to do read back up to 32 of them at the same time of something). By default concurrent wri; /archives/xfs/2006-07/msg00161.html (8,995 bytes)
7. Re: file system defragmentation (score: 1): Author: Cosmo Nova <cs_mcc98@xxxxxxxxxxx>; Date: Tue, 18 Jul 2006 00:59:39 -0700 (PDT); 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?; /archives/xfs/2006-07/msg00165.html (9,250 bytes)
8. Re: file system defragmentation (score: 1): Author: Chris Wedgwood <cw@xxxxxxxx>; Date: Tue, 18 Jul 2006 14:33:04 -0700; the allocator has per-AG locks i'm not sure what you mean, but any number of files can be writing to a single AG at once, the degree of fragmentation you will see depends on the IO patterns and where; /archives/xfs/2006-07/msg00176.html (10,044 bytes)
9. Re: file system defragmentation (score: 1): Author: Cosmo Nova <cs_mcc98@xxxxxxxxxxx>; Date: Wed, 19 Jul 2006 03:33:13 -0700 (PDT); 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; /archives/xfs/2006-07/msg00191.html (9,447 bytes)
10. Re: file system defragmentation (score: 1): Author: Cosmo Nova <cs_mcc98@xxxxxxxxxxx>; Date: Wed, 19 Jul 2006 21:23:42 -0700 (PDT); what is the maximum tolerance for the delayed allocations pls? I guess it's not possible to buf a GB size file and delay its allocation? -- View this message in context: http://www.nabble.com/file-sy; /archives/xfs/2006-07/msg00209.html (8,487 bytes)
11. Re: file system defragmentation (score: 1): Author: Cosmo Nova <cs_mcc98@xxxxxxxxxxx>; Date: Wed, 19 Jul 2006 21:22:00 -0700 (PDT); does the preallocation belong to xfs layer? or it's a "suggested feature" for -- View this message in context: http://www.nabble.com/file-system-defragmentation-tf255485.html#a5408744 Sent from the X; /archives/xfs/2006-07/msg00210.html (8,355 bytes)
12. Re: file system defragmentation (score: 1): Author: Cosmo Nova <cs_mcc98@xxxxxxxxxxx>; Date: Mon, 17 Jul 2006 00:36:09 -0700 (PDT); 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.; /archives/xfs/2006-07/msg00536.html (8,717 bytes)
13. Re: file system defragmentation (score: 1): Author: David Chatterton <chatz@xxxxxxxxxxxxxxxxx>; Date: Mon, 17 Jul 2006 19:32:30 +1000; Cosmo Nova wrote: 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? I'll leave the detai; /archives/xfs/2006-07/msg00540.html (10,666 bytes)
14. Re: file system defragmentation (score: 1): Author: David Chinner <dgc@xxxxxxx>; Date: Tue, 18 Jul 2006 00:19:17 +1000; No special buffering is needed in XFS as the page cache does it all for us. delalloc means that XFS does not allocate until the data gets written to disk (i.e. flushed from the cache). The size of th; /archives/xfs/2006-07/msg00547.html (9,080 bytes)
15. Re: file system defragmentation (score: 1): Author: Chris Wedgwood <cw@xxxxxxxx>; Date: Mon, 17 Jul 2006 12:08:27 -0700; I did some work for someone who does a similar thing (they write 96 channels in parallel and have to be able to do read back up to 32 of them at the same time of something). By default concurrent wri; /archives/xfs/2006-07/msg00551.html (8,995 bytes)
16. Re: file system defragmentation (score: 1): Author: Cosmo Nova <cs_mcc98@xxxxxxxxxxx>; Date: Tue, 18 Jul 2006 00:59:39 -0700 (PDT); 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?; /archives/xfs/2006-07/msg00555.html (9,250 bytes)
17. Re: file system defragmentation (score: 1): Author: Chris Wedgwood <cw@xxxxxxxx>; Date: Tue, 18 Jul 2006 14:33:04 -0700; the allocator has per-AG locks i'm not sure what you mean, but any number of files can be writing to a single AG at once, the degree of fragmentation you will see depends on the IO patterns and where; /archives/xfs/2006-07/msg00566.html (10,044 bytes)
18. Re: file system defragmentation (score: 1): Author: Cosmo Nova <cs_mcc98@xxxxxxxxxxx>; Date: Wed, 19 Jul 2006 03:33:13 -0700 (PDT); 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; /archives/xfs/2006-07/msg00581.html (9,447 bytes)
19. Re: file system defragmentation (score: 1): Author: Cosmo Nova <cs_mcc98@xxxxxxxxxxx>; Date: Wed, 19 Jul 2006 21:23:42 -0700 (PDT); what is the maximum tolerance for the delayed allocations pls? I guess it's not possible to buf a GB size file and delay its allocation? -- View this message in context: http://www.nabble.com/file-sy; /archives/xfs/2006-07/msg00599.html (8,487 bytes)
20. Re: file system defragmentation (score: 1): Author: Cosmo Nova <cs_mcc98@xxxxxxxxxxx>; Date: Wed, 19 Jul 2006 21:22:00 -0700 (PDT); does the preallocation belong to xfs layer? or it's a "suggested feature" for -- View this message in context: http://www.nabble.com/file-system-defragmentation-tf255485.html#a5408744 Sent from the X; /archives/xfs/2006-07/msg00600.html (8,355 bytes)

Current List: 1 - 20
Page: [1] [2] [3]