| To: | Matthias Schniedermeyer <ms@xxxxxxx> |
|---|---|
| Subject: | Re: File size more than 4G on XFS (Bigendian-32bit-cpu) |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | Thu, 23 Sep 2004 09:51:00 -0500 |
| Cc: | argon@xxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20040923080656.GA11343@citd.de> |
| References: | <OF03A5DEB4.00B337D2-ON48256F16.002D3828@sernet.com.cn> <20040923080656.GA11343@citd.de> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 0.7.3 (X11/20040803) |
Matthias Schniedermeyer wrote:
For me mkfs.xfs ALWAYS uses a too low agcount, with a too low agcount a single aggregategroup can be lager than 4GB which i was told is a "no no".
mkfs_xfs.c: revision 1.52 date: 2003/10/28 04:41:37; author: nathans; state: Exp; lines: +141 -126 modid: xfs-cmds:slinx:160712a Rework the mkfs allocation group sizing algorithm, making better use of the available bits. This changes the maximum allocation group size enforced by mkfs to be 1TB (from 4GB), which scales alot better for very large filesystems. Hm, Nathan, I think we need to update the mkfs man page...? Do a xfs_info on your device and if (agsize * sectsz) > 4GB (or "Capacity / agcount" > 4GB) then you have to reformat with a bigger agcount/lower agsize. Feel free to try, maybe it will help, but the design intent is that larger AGs should be fine. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: File size more than 4G on XFS (Bigendian-32bit-cpu), Matthias Schniedermeyer |
|---|---|
| Next by Date: | Re: File size more than 4G on XFS (Bigendian-32bit-cpu), Nathan Scott |
| Previous by Thread: | Re: File size more than 4G on XFS (Bigendian-32bit-cpu), Matthias Schniedermeyer |
| Next by Thread: | Re: File size more than 4G on XFS (Bigendian-32bit-cpu), Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |