Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Every\s+new\s+file\s+goes\s+into\s+a\s+new\s+ag\s*$/: 15 ]

Total 15 documents matching your query.

1. Every new file goes into a new ag (score: 1)
Author: xxxx>
Date: Wed, 11 May 2005 16:46:33 +0200
Hi there, I just got XFS running under RedHat EL 3.0. Since I need high bandwidth for media playout, where in our case each and every frame of a film image sequence is a new file, I need file sequenc
/archives/xfs/2005-05/msg00053.html (8,656 bytes)

2. Re: Every new file goes into a new ag (score: 1)
Author: xxxx>
Date: Wed, 11 May 2005 10:15:03 -0500
If you have a "rotorstep" systune in your xfs codebase you might play with that; otherwise try making the size of your inode bigger (at mkfs time) so that you don't get into inode32 mode. (or, if you
/archives/xfs/2005-05/msg00054.html (9,872 bytes)

3. RE: Every new file goes into a new ag (score: 1)
Author: xxxx>
Date: Wed, 11 May 2005 17:41:54 +0200
I can't find any rotorstep within my xfs kernel codebase. Any idea how I can get this in? I'm running on a 32 bit machine that's why I can't use idnode64 right? My machine currently shows me isize=2
/archives/xfs/2005-05/msg00056.html (10,266 bytes)

4. Re: Every new file goes into a new ag (score: 1)
Author: xxxx>
Date: Wed, 11 May 2005 11:38:31 -0500
I can't find any rotorstep within my xfs kernel codebase. Any idea how I can get this in? Depends on where you got your xfs code, I guess - I think it should be in cvs at least. I'm running on a 32 b
/archives/xfs/2005-05/msg00058.html (8,975 bytes)

5. RE: Every new file goes into a new ag (score: 1)
Author: xxxx>
Date: Thu, 12 May 2005 17:36:41 +0200
the tip with the inode size helped in getting the files contiguous on disk. However the performance of the filesystem 250 MByte/sec is much worth compared to the raw lvm volume which is 400 MByte/se
/archives/xfs/2005-05/msg00070.html (9,136 bytes)

6. Every new file goes into a new ag (score: 1)
Author: ea@xxxxxxx>
Date: Wed, 11 May 2005 16:46:33 +0200
Hi there, I just got XFS running under RedHat EL 3.0. Since I need high bandwidth for media playout, where in our case each and every frame of a film image sequence is a new file, I need file sequenc
/archives/xfs/2005-05/msg00254.html (8,656 bytes)

7. Re: Every new file goes into a new ag (score: 1)
Author: xxxxxxxxxx>
Date: Wed, 11 May 2005 10:15:03 -0500
If you have a "rotorstep" systune in your xfs codebase you might play with that; otherwise try making the size of your inode bigger (at mkfs time) so that you don't get into inode32 mode. (or, if you
/archives/xfs/2005-05/msg00255.html (9,872 bytes)

8. RE: Every new file goes into a new ag (score: 1)
Author: en@xxxxxxx>
Date: Wed, 11 May 2005 17:41:54 +0200
I can't find any rotorstep within my xfs kernel codebase. Any idea how I can get this in? I'm running on a 32 bit machine that's why I can't use idnode64 right? My machine currently shows me isize=2
/archives/xfs/2005-05/msg00257.html (10,266 bytes)

9. Re: Every new file goes into a new ag (score: 1)
Author: xxxxxxxxxx>
Date: Wed, 11 May 2005 11:38:31 -0500
I can't find any rotorstep within my xfs kernel codebase. Any idea how I can get this in? Depends on where you got your xfs code, I guess - I think it should be in cvs at least. I'm running on a 32 b
/archives/xfs/2005-05/msg00259.html (8,975 bytes)

10. RE: Every new file goes into a new ag (score: 1)
Author: @xxxxxxxxx>
Date: Thu, 12 May 2005 17:36:41 +0200
the tip with the inode size helped in getting the files contiguous on disk. However the performance of the filesystem 250 MByte/sec is much worth compared to the raw lvm volume which is 400 MByte/se
/archives/xfs/2005-05/msg00271.html (9,136 bytes)

11. Every new file goes into a new ag (score: 1)
Author: "Bub Thomas" <thomas.bub@xxxxxxxxxxx>
Date: Wed, 11 May 2005 16:46:33 +0200
Hi there, I just got XFS running under RedHat EL 3.0. Since I need high bandwidth for media playout, where in our case each and every frame of a film image sequence is a new file, I need file sequenc
/archives/xfs/2005-05/msg00455.html (8,656 bytes)

12. Re: Every new file goes into a new ag (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxx>
Date: Wed, 11 May 2005 10:15:03 -0500
If you have a "rotorstep" systune in your xfs codebase you might play with that; otherwise try making the size of your inode bigger (at mkfs time) so that you don't get into inode32 mode. (or, if you
/archives/xfs/2005-05/msg00456.html (10,110 bytes)

13. RE: Every new file goes into a new ag (score: 1)
Author: "Bub Thomas" <thomas.bub@xxxxxxxxxxx>
Date: Wed, 11 May 2005 17:41:54 +0200
Eric, I can't find any rotorstep within my xfs kernel codebase. Any idea how I can get this in? I'm running on a 32 bit machine that's why I can't use idnode64 right? My machine currently shows me is
/archives/xfs/2005-05/msg00458.html (10,281 bytes)

14. Re: Every new file goes into a new ag (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxx>
Date: Wed, 11 May 2005 11:38:31 -0500
Depends on where you got your xfs code, I guess - I think it should be in cvs at least. I'm running on a 32 bit machine that's why I can't use idnode64 right? My machine currently shows me isize=256.
/archives/xfs/2005-05/msg00460.html (9,181 bytes)

15. RE: Every new file goes into a new ag (score: 1)
Author: "Bub Thomas" <thomas.bub@xxxxxxxxxxx>
Date: Thu, 12 May 2005 17:36:41 +0200
Eric, the tip with the inode size helped in getting the files contiguous on disk. However the performance of the filesystem 250 MByte/sec is much worth compared to the raw lvm volume which is 400 MBy
/archives/xfs/2005-05/msg00472.html (9,151 bytes)


This search system is powered by Namazu