| To: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 3/5] xfs: kill ino64 mount option |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Tue, 24 Mar 2009 19:30:37 +1100 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <49C56650.10008@xxxxxxxxxxx> |
| Mail-followup-to: | Eric Sandeen <sandeen@xxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| References: | <20090318094119.561416000@xxxxxxxxxxxxxxxxxxxxxx> <20090318094132.076764000@xxxxxxxxxxxxxxxxxxxxxx> <49C4650B.4040509@xxxxxxxxxxx> <20090321200806.GA15245@xxxxxxxxxxxxx> <49C56650.10008@xxxxxxxxxxx> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
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 kind > >>> of debug tool given that it's easy to produce real 64bit inode numbers > >>> for 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. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| Previous by Date: | Re: [PATCH 3/5] xfs: kill ino64 mount option, Eric Sandeen |
|---|---|
| Next by Date: | Re: How to configure 36 disks ?, Drew |
| Previous by Thread: | Re: [PATCH 3/5] xfs: kill ino64 mount option, Eric Sandeen |
| Next by Thread: | Re: [PATCH 3/5] xfs: kill ino64 mount option, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |