On Wed, 14 Aug 2013 at 21:29, Christian Kujau wrote:
> On Wed, 14 Aug 2013 at 22:54, Dave Kleikamp wrote:
> > It looks like the problem is that jfs was using a cookie value of 2 for
> > a real directory entry, where NFSv4 expect 2 to represent "..". This
> > patch has so far only been lightly tested.
>
> Hm, a first compile of 3.11-rc5 errors out with:
>
> CC [M] fs/jfs/jfs_dtree.o
> /usr/local/src/linux-git/fs/jfs/jfs_dtree.c: In function ‘add_index’:
> /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:493:13: error: invalid storage class for function ‘free_index’
[...]
>
> I'll run mrproper and try again...
This did not help, but adding a closing bracket did, in fs/jfs/jfs_dtree.c:354
if (jfs_ip->next_index < 3) {
jfs_ip->next_index = 3;
}
-----^
This compiled and booted and now I can run find(1) over that whole NFS
share, without any "readdir loop" messages and with unique inode numbers,
yay!
Tested-by: Christian Kujau <lists@xxxxxxxxxxxxxxx>
Thanks!
Christian.
--
BOFH excuse #36:
dynamic software linking table corrupted
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
