| To: | hank peng <pengxihan@xxxxxxxxx> |
|---|---|
| Subject: | Re: xfs: validate inode numbers in file handles correctly |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Tue, 6 Dec 2011 10:17:38 -0500 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx, Guoquan Yang <ygq51@xxxxxxxxxxx> |
| In-reply-to: | <CAJNJY8RSOX2XsbM+0riNNPGxaLGm+OWkHexTVM4v5+rhkchuAw@xxxxxxxxxxxxxx> |
| References: | <1276846374-23916-1-git-send-email-david@xxxxxxxxxxxxx> <loom.20111123T134243-580@xxxxxxxxxxxxxx> <20111123143045.GA20892@xxxxxxxxxxxxx> <20111128111947.GA26454@xxxxxxxxxxxxx> <CAJNJY8RSOX2XsbM+0riNNPGxaLGm+OWkHexTVM4v5+rhkchuAw@xxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Sat, Dec 03, 2011 at 04:27:39PM +0800, hank peng wrote: > I haven't tested this patch, but I have a question now: although I use > inode64 option when mounting, my filesystem did not exceed 2T limit, > so, 32-bit inode would be no problem, right? In the normal configuration > 32bit inode numbers kick in at 1TB filesystem sizes. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] xfstests: check if qa user can execute commands, Jan Schmidt |
|---|---|
| Next by Date: | Re: [PATCH] xfstests: check if qa user can execute commands, Christoph Hellwig |
| Previous by Thread: | Re: xfs: validate inode numbers in file handles correctly, hank peng |
| Next by Thread: | RE: xfs: validate inode numbers in file handles correctly, yangguoquan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |