It seems that the following commit changed the dir name hash:
commit d1f5273e9adb40724a85272f248f210dc4ce919a
Author: Fan Yong <yong....@whamcloud.com>
Date: Sun Mar 18 22:44:40 2012 -0400
ext4: return 32/64-bit dir name hash according to usage type
Traditionally ext2/3/4 has returned a 32-bit hash value from llseek()
to appease NFSv2, which can only handle a 32-bit cookie for seekdir()
and telldir(). However, this causes problems if there are 32-bit hash
collisions, since the NFSv2 server can get stuck resending the same
entries from the directory repeatedly.
Allow ext4 to return a full 64-bit hash (both major and minor) for
telldir to decrease the chance of hash collisions. This still needs
integration on the NFS side.
This commit reworked hash2pos which is used for calculating the d_off
value from the major/minor and contains the following comment:
Upper layer (for example NFS) should specify FMODE_32BITHASH or
FMODE_64BITHASH explicitly. On the other hand, we allow ext4 to be mounted
directly on both 32-bit and 64-bit nodes, under such case, neither
FMODE_32BITHASH nor FMODE_64BITHASH is specified.
For reference, nfsd_open() sets the f_mode flag to FMODE_64BITHASH if
NFSD_MAY_64BIT_COOKIE or FMODE_32BITHASH otherwise.
So it seems likely that gluster needs to be updated to handle this
change. { thanks to Seth Forshee for the original analysis }
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022500
Title:
ext4 d_off values too high
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1022500/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
