| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 3/5] xfs: kill ino64 mount option |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Tue, 24 Mar 2009 08:11:36 -0500 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| In-reply-to: | <20090324083037.GP26138@disturbed> |
| References: | <20090318094119.561416000@xxxxxxxxxxxxxxxxxxxxxx> <20090318094132.076764000@xxxxxxxxxxxxxxxxxxxxxx> <49C4650B.4040509@xxxxxxxxxxx> <20090321200806.GA15245@xxxxxxxxxxxxx> <49C56650.10008@xxxxxxxxxxx> <20090324083037.GP26138@disturbed> |
On Mar 24, 2009, at 3:30 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote: On Sat, Mar 21, 2009 at 05:12:32PM -0500, Eric Sandeen wrote:Christoph Hellwig wrote:On Fri, Mar 20, 2009 at 10:54:51PM -0500, Eric Sandeen wrote:Christoph Hellwig wrote:The ino64 mount option adds a fixed offset to 32bit inode numbers to bring them into the 64bit range. There's no need for this kindof debug tool given that it's easy to produce real 64bit inode numbersfor testing.hm, easy how?Actually test with a large enough device and let them spread evenly over the AGs.It's the large-enough device which sometimes is at odds with "easy"Sparse loopback image OK I'm sold... Eric Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| Previous by Date: | Re: [patch] fix parallel build failures in xfsprogs-3.0.0, Andreas Gruenbacher |
|---|---|
| Next by Date: | Re: [PATCH 3/5] xfs: kill ino64 mount option, Dave Chinner |
| Previous by Thread: | Re: [PATCH 3/5] xfs: kill ino64 mount option, Dave Chinner |
| Next by Thread: | Re: [PATCH 3/5] xfs: kill ino64 mount option, Felix Blyakher |
| Indexes: | [Date] [Thread] [Top] [All Lists] |