| To: | Ben Myers <bpm@xxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 5/4] xfs: fix nfs export of 64-bit inodes numbers on 32-bit kernels |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Fri, 2 Dec 2011 12:29:08 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20111202160712.GO29840@xxxxxxx> |
| References: | <20111128081732.350228200@xxxxxxxxxxxxxxxxxxxxxx> <20111130085817.GA22471@xxxxxxxxxxxxx> <20111202160712.GO29840@xxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Fri, Dec 02, 2011 at 10:07:12AM -0600, Ben Myers wrote: > To what extent did you test this one? Anything in particular I should > look for when I test it? Create a large filesystem, mount it using -o inode64 on a 32-bit kernel, find an inode that actually uses more than 32-bits, and try to access it from an nfs client. Alternatively you could probably reproduce it using the open by handle system calls, I have an idea how to turn that into a test case for xfstests using a large loopback filesystem. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH 08/12] repair: handle filesystems with the log in allocation group 0, Christoph Hellwig |
|---|---|
| Next by Date: | [PATCH 01/12] repair: do not walk the unlinked inode list, Christoph Hellwig |
| Previous by Thread: | Re: [PATCH 5/4] xfs: fix nfs export of 64-bit inodes numbers on 32-bit kernels, Ben Myers |
| Next by Thread: | Re: [PATCH 5/4] xfs: fix nfs export of 64-bit inodes numbers on 32-bit kernels, Ben Myers |
| Indexes: | [Date] [Thread] [Top] [All Lists] |