xfs
[Top] [All Lists]

Re: [PATCH] xfs: Update mount options documentation

To: xfs@xxxxxxxxxxx
Subject: Re: [PATCH] xfs: Update mount options documentation
From: Mark Tinguely <tinguely@xxxxxxx>
Date: Thu, 18 Oct 2012 12:15:18 -0500
In-reply-to: <20121018170442.GA6634@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <1350574138-30305-1-git-send-email-cmaiolino@xxxxxxxxxx> <5080253A.9060906@xxxxxxx> <5080279C.8030702@xxxxxxxxxxxxxxxxx> <508028CC.5080800@xxxxxxx> <20121018170442.GA6634@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20120122 Thunderbird/9.0
On 10/18/12 12:04, Carlos Maiolino wrote:
On Thu, Oct 18, 2012 at 11:05:32AM -0500, Mark Tinguely wrote:
On 10/18/12 11:00, Dave Howorth wrote:
Mark Tinguely wrote:
Would "Indicates that XFS is allowed to create inodes at locations up to
32 bits of significance .."

I prefer the original wording. Your suggestion says something about what
XFS can do, but nothing about what it is not allowed to do, which is
rather more important.

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

I see your point. Sounds good to me.

--Mark.

This means no change is needed?


I am okay with what is written about creating inodes.

On a separate question, should something be mentioned that inode32 mode can still read/write/unlink any inode, even those number greater than 32 bit, or will that confuse the inode creation point?

--Mark.


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