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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Pre\-production\s+questions\s*$/: 14 ]

Total 14 documents matching your query.

1. Pre-production questions (score: 1): Author: Joshua Baker-LePain <jlb17@xxxxxxxx>; Date: Mon, 19 Mar 2001 23:04:02 -0500 (EST); First, let me say thanks to this list and to SGI for all the hard work on XFS. It's a rather impressive bit of work, and almost kind of eerie knowing that I could pull a disk out of my Indigo2, put i; /archives/xfs/2001-03/msg00295.html (8,026 bytes)
2. Re: Pre-production questions (score: 1): Author: "Martin K. Petersen" <mkp@xxxxxxxxxxxxx>; Date: 20 Mar 2001 08:28:15 -0500; Well. You could try and hint to the allocator how your RAID device is set up. Try and look up which chunk size it uses. You can pass that information on to mkfs using the sunit and swidth options. S; /archives/xfs/2001-03/msg00304.html (9,256 bytes)
3. Re: Pre-production questions (score: 1): Author: Joshua Baker-LePain <jlb17@xxxxxxxx>; Date: Tue, 20 Mar 2001 13:18:41 -0500 (EST); The unit's default is a stripe size of 64 512 byte blocks. The stripe size can be set between 4 and 128 (incrementally, of course). For the defaults, would this be correct: mkfs.xfs -d sunit=1,swidth; /archives/xfs/2001-03/msg00309.html (9,379 bytes)
4. Re: Pre-production questions (score: 1): Author: "Martin K. Petersen" <mkp@xxxxxxxxxxxxx>; Date: 20 Mar 2001 15:21:34 -0500; sunit = stripe width / number of disks So mkfs.xfs -d sunit=8,swidth=64 for your 8 disks. Depends how log-heavy the fs will be. But in general we tend to use a bigger log than the 1000b default. We'; /archives/xfs/2001-03/msg00315.html (9,197 bytes)
5. Re: Pre-production questions (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Tue, 20 Mar 2001 14:25:03 -0600; Actually this is incorrect, you need -d sunit=64,swidth=448 The sunit is the amount of data on each disk in 512 byte chunks, the swidth is the total amount of data before we go back to the first dis; /archives/xfs/2001-03/msg00316.html (9,570 bytes)
6. Re: Pre-production questions (score: 1): Author: "Martin K. Petersen" <mkp@xxxxxxxxxxxxx>; Date: 20 Mar 2001 15:41:22 -0500; Hmmm. I read the 64KB as across all the disks. Usually RAID5 arrays tend to use very small values compared to RAID0/1. Joshua - check your manual to make sure what they mean. -- Martin K. Petersen,; /archives/xfs/2001-03/msg00317.html (8,751 bytes)
7. Re: Pre-production questions (score: 1): Author: Joshua Baker-LePain <jlb17@xxxxxxxx>; Date: Tue, 27 Mar 2001 11:20:43 -0500 (EST); OK. ;) The answer is a bit, but not really. I verified with the vendor that, indeed, the stripe size specified on the RAID system is blocks/disk. So, I upped the stripe size to 128 (512byte) blocks (; /archives/xfs/2001-03/msg00446.html (11,889 bytes)
8. Pre-production questions (score: 1): Author: Joshua Baker-LePain <jlb17@xxxxxxxx>; Date: Mon, 19 Mar 2001 23:04:02 -0500 (EST); First, let me say thanks to this list and to SGI for all the hard work on XFS. It's a rather impressive bit of work, and almost kind of eerie knowing that I could pull a disk out of my Indigo2, put i; /archives/xfs/2001-03/msg00828.html (8,026 bytes)
9. Re: Pre-production questions (score: 1): Author: "Martin K. Petersen" <mkp@xxxxxxxxxxxxx>; Date: 20 Mar 2001 08:28:15 -0500; Well. You could try and hint to the allocator how your RAID device is set up. Try and look up which chunk size it uses. You can pass that information on to mkfs using the sunit and swidth options. S; /archives/xfs/2001-03/msg00837.html (9,256 bytes)
10. Re: Pre-production questions (score: 1): Author: Joshua Baker-LePain <jlb17@xxxxxxxx>; Date: Tue, 20 Mar 2001 13:18:41 -0500 (EST); The unit's default is a stripe size of 64 512 byte blocks. The stripe size can be set between 4 and 128 (incrementally, of course). For the defaults, would this be correct: mkfs.xfs -d sunit=1,swidth; /archives/xfs/2001-03/msg00842.html (9,379 bytes)
11. Re: Pre-production questions (score: 1): Author: "Martin K. Petersen" <mkp@xxxxxxxxxxxxx>; Date: 20 Mar 2001 15:21:34 -0500; sunit = stripe width / number of disks So mkfs.xfs -d sunit=8,swidth=64 for your 8 disks. Depends how log-heavy the fs will be. But in general we tend to use a bigger log than the 1000b default. We'; /archives/xfs/2001-03/msg00848.html (9,197 bytes)
12. Re: Pre-production questions (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: Tue, 20 Mar 2001 14:25:03 -0600; Actually this is incorrect, you need -d sunit=64,swidth=448 The sunit is the amount of data on each disk in 512 byte chunks, the swidth is the total amount of data before we go back to the first dis; /archives/xfs/2001-03/msg00849.html (9,570 bytes)
13. Re: Pre-production questions (score: 1): Author: "Martin K. Petersen" <mkp@xxxxxxxxxxxxx>; Date: 20 Mar 2001 15:41:22 -0500; Hmmm. I read the 64KB as across all the disks. Usually RAID5 arrays tend to use very small values compared to RAID0/1. Joshua - check your manual to make sure what they mean. -- Martin K. Petersen,; /archives/xfs/2001-03/msg00850.html (8,751 bytes)
14. Re: Pre-production questions (score: 1): Author: Joshua Baker-LePain <jlb17@xxxxxxxx>; Date: Tue, 27 Mar 2001 11:20:43 -0500 (EST); OK. ;) The answer is a bit, but not really. I verified with the vendor that, indeed, the stripe size specified on the RAID system is blocks/disk. So, I upped the stripe size to 128 (512byte) blocks (; /archives/xfs/2001-03/msg00979.html (11,889 bytes)

Current List: 1 - 14
Page: [1]