Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*mkfs\.xfs\s+error\s+creating\s+large\s+agcount\s+an\s+raid\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*mkfs\.xfs\s+error\s+creating\s+large\s+agcount\s+an\s+raid\s*$/: 15 ]

Total 15 documents matching your query.

1. mkfs.xfs error creating large agcount an raid (score: 1): Author: Marcus Pereira <marcus@xxxxxxxxxxx>; Date: Sat, 25 Jun 2011 16:49:26 -0300; I have an issue when creating xfs volume using large agcounts on raid volumes. /dev/md0 is a 4 disks raid 0 array: -- mkfs.xfs version 3.1.4 Warning: AG size is a multiple of stripe width. This can c; /archives/xfs/2011-06/msg00388.html (8,697 bytes)
2. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Sat, 25 Jun 2011 21:09:16 -0500; Yes, you do have an issue, but not the one you think. mkfs.xfs queries mdraid for its parameters and creates close to the optimal number of AGs, sets the stripe width, etc, all automatically. The def; /archives/xfs/2011-06/msg00392.html (8,522 bytes)
3. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Marcus Pereira <marcus@xxxxxxxxxxx>; Date: Sun, 26 Jun 2011 02:53:43 -0300; Em 25-06-2011 23:09, Stan Hoeppner escreveu: On 6/25/2011 2:49 PM, Marcus Pereira wrote: I have an issue when creating xfs volume using large agcounts on raid volumes. Yes, you do have an issue, but; /archives/xfs/2011-06/msg00393.html (11,191 bytes)
4. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Sun, 26 Jun 2011 16:26:52 -0500; Maildir is much more metadata intensive than mbox, generating many more small IOs, and thus head movement. With a large number of allocation groups this will exacerbate the head seeking problem. That; /archives/xfs/2011-06/msg00395.html (13,435 bytes)
5. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Sun, 26 Jun 2011 18:29:33 -0500; The DS8300 has up to 256GB of read/write cache: http://publib.boulder.ibm.com/infocenter/dsichelp/ds8000ic/index.jsp?topic=%2Fcom.ibm.storage.ssic.help.doc%2Ff2c_ds8300models922and9a2_1w2zq9.html It'; /archives/xfs/2011-06/msg00396.html (9,999 bytes)
6. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Mon, 27 Jun 2011 09:59:59 +1000; Perhaps you should just usethe defaults first and only consider changes if there is an obvious problem,? AGs are not for reducing seeking - they are for increasing allocation parallelism and scaling; /archives/xfs/2011-06/msg00397.html (13,023 bytes)
7. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Sun, 26 Jun 2011 22:33:27 -0500; I missed this part of the reply probably due to the reply formatting style used. Marcus, if you are seeing excessive head seeking with this maildir workload, the problem isn't the number of AGs. The; /archives/xfs/2011-06/msg00399.html (10,546 bytes)
8. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Marcus Pereira <marcus@xxxxxxxxxxx>; Date: Mon, 27 Jun 2011 01:14:34 -0300; Em 27-06-2011 00:33, Stan Hoeppner escreveu: I recommend 3 changes, one of which I previously mentioned: 1. Use 8 mirror pairs instead of 4 2. Don't use striping. Make an mdraid --linear device of th; /archives/xfs/2011-06/msg00401.html (10,304 bytes)
9. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Mon, 27 Jun 2011 03:55:11 -0500; So you do or don't have the excessive head seek problem you previously mentioned? If not then use the mkfs.xfs defaults. You're welcome. Google should turn up a decent amount of information about XFS; /archives/xfs/2011-06/msg00410.html (11,062 bytes)
10. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Paul Anderson <pha@xxxxxxxxx>; Date: Mon, 27 Jun 2011 09:04:54 -0400; One thing this thread indicates is the need for a warning in mkfs.xfs - according to several developers, there is, I think, linear increase in allocation time to number of allocation groups. It would; /archives/xfs/2011-06/msg00411.html (14,345 bytes)
11. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Mon, 27 Jun 2011 10:10:06 -0500; I disagree. There are all sorts of ways a user can shoot themselves in the foot with unix commands. Detecting and warning about all of them is a fool's errand. == = Warning! mkfs.xfs detected insane; /archives/xfs/2011-06/msg00413.html (14,538 bytes)
12. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Paul Anderson <pha@xxxxxxxxx>; Date: Mon, 27 Jun 2011 11:27:00 -0400; Clearly a philosophical difference. In managing complex software, it is far better for users if the software itself can simply report why something is a problem, without resorting to expecting users; /archives/xfs/2011-06/msg00414.html (17,566 bytes)
13. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Mon, 27 Jun 2011 10:37:15 -0500; This one instance would not be hard to do, agreed. To point out every potential pitfall in every bad option or combination of options would be impossible. I'd be happy with a version of the FAQ entry; /archives/xfs/2011-06/msg00415.html (18,202 bytes)
14. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Stan Hoeppner <stan@xxxxxxxxxxxxxxxxx>; Date: Mon, 27 Jun 2011 15:55:26 -0500; It is. From the 2nd paragraph of 'man 5 xfs': ...The data section is divided into a number of allocation groups. The number and size of the allocation groups are chosen by mkfs.xfs(8) so that there i; /archives/xfs/2011-06/msg00419.html (11,537 bytes)
15. Re: mkfs.xfs error creating large agcount an raid (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Tue, 28 Jun 2011 11:22:57 +1000; I don't expect users to read code. We have documentation, we expect users to read it first and have some understanding of how stuff works. If you don't understand it, then I expect that users will as; /archives/xfs/2011-06/msg00424.html (18,665 bytes)

Current List: 1 - 15
Page: [1]