| To: | Matthias Schniedermeyer <ms@xxxxxxx> |
|---|---|
| Subject: | Re: File size more than 4G on XFS (Bigendian-32bit-cpu) |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Fri, 24 Sep 2004 06:41:47 +1000 |
| Cc: | argon@xxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20040923080656.GA11343@xxxxxxx>; from ms@xxxxxxx on Thu, Sep 23, 2004 at 10:06:56AM +0200 |
| References: | <OF03A5DEB4.00B337D2-ON48256F16.002D3828@xxxxxxxxxxxxx> <20040923080656.GA11343@xxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Thu, Sep 23, 2004 at 10:06:56AM +0200, 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". Eh? Who told you that? Its not correct at all. > 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. Thats not right either. There are big advantages to moving to allocation groups larger than 4G. Use the mkfs defaults here, unless you really know what you're doing. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: File size more than 4G on XFS (Bigendian-32bit-cpu), Eric Sandeen |
|---|---|
| Next by Date: | Re: File size more than 4G on XFS (Bigendian-32bit-cpu), Matthias Schniedermeyer |
| Previous by Thread: | Re: File size more than 4G on XFS (Bigendian-32bit-cpu), Eric Sandeen |
| Next by Thread: | Re: File size more than 4G on XFS (Bigendian-32bit-cpu), Matthias Schniedermeyer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |