xfs
[Top] [All Lists]

Re: [PATCH 3/5] xfs: kill ino64 mount option

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: [PATCH 3/5] xfs: kill ino64 mount option
From: Felix Blyakher <felixb@xxxxxxx>
Date: Thu, 26 Mar 2009 17:37:11 -0500
Cc: Dave Chinner <david@xxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
In-reply-to: <612C6156-D3B9-43BF-880A-DE54EB4F56A9@xxxxxxxxxxx>
References: <20090318094119.561416000@xxxxxxxxxxxxxxxxxxxxxx> <20090318094132.076764000@xxxxxxxxxxxxxxxxxxxxxx> <49C4650B.4040509@xxxxxxxxxxx> <20090321200806.GA15245@xxxxxxxxxxxxx> <49C56650.10008@xxxxxxxxxxx> <20090324083037.GP26138@disturbed> <612C6156-D3B9-43BF-880A-DE54EB4F56A9@xxxxxxxxxxx>
On Mar 24, 2009, at 8:11 AM, Eric Sandeen wrote:



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 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

OK I'm sold...

That addressed my concern too.

Reviewed-by: Felix Blyakher <felixb@xxxxxxx>



Eric


Cheers,

Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx


_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs

<Prev in Thread] Current Thread [Next in Thread>