[Bug 1022500] Re: ext4 d_off values too high
** Changed in: linux (Ubuntu) Status: Triaged = Won't Fix -- 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
[Bug 1022500] Re: ext4 d_off values too high
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
[Bug 1022500] Re: ext4 d_off values too high
** Changed in: linux (Ubuntu) Status: Confirmed = Triaged ** Tags removed: kernel-key -- 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
[Bug 1022500] Re: ext4 d_off values too high
** Description changed: After you create a mkfs.ext4 filesystem, the new filesystem returns very high d_off values for all fs content. - I came across this problem using GlusterFS what utilizes the d_off values got so high that even in 64bit the values were overflowing gluster's transformed d_off causing a wrap around and readdir to loop. + I came across this problem using GlusterFS what utilizes the d_off values, they got so high that even in 64bit the values were overflowing gluster's transformed d_off causing a wrap around and readdir to loop. Originally discovery of the bug was on kernel 3.4.4, but as I report this it is still the case in 3.5.0-3-generic kernel. d_off listing of my ext4 fs: ..: 2296413350859310193 .: 4783779301059207147 lost+found: 5425848893403102488 test: 9223372036854775807 as a comparison I formatted the same disk with xfs, give these more normal d_off values .: 4 ..: 6 test: 512 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-3-generic 3.5.0-3.3 ProcVersionSignature: User Name 3.5.0-3.3-generic 3.5.0-rc5 Uname: Linux 3.5.0-3-generic x86_64 AlsaDevices: - total 0 - crw-rw---T 1 root audio 116, 1 Jul 9 08:48 seq - crw-rw---T 1 root audio 116, 33 Jul 9 08:48 timer + total 0 + crw-rw---T 1 root audio 116, 1 Jul 9 08:48 seq + crw-rw---T 1 root audio 116, 33 Jul 9 08:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.2.5-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDmesg: [ 51.139794] EXT4-fs (vdb): mounted filesystem with ordered data mode. Opts: (null) Date: Mon Jul 9 08:52:43 2012 IwConfig: - eth0 no wireless extensions. - - lono wireless extensions. + eth0 no wireless extensions. + + lono wireless extensions. Lsusb: - Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd - Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: - + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-3-generic root=UUID=96867050-a925-4b6e-a85d-fa3ef6875343 ro console=ttyS0 RelatedPackageVersions: - linux-restricted-modules-3.5.0-3-generic N/A - linux-backports-modules-3.5.0-3-generic N/A - linux-firmware N/A + linux-restricted-modules-3.5.0-3-generic N/A + linux-backports-modules-3.5.0-3-generic N/A + linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs -- 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
[Bug 1022500] Re: ext4 d_off values too high
** Changed in: linux (Ubuntu) Status: New = Confirmed -- 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
[Bug 1022500] Re: ext4 d_off values too high
Further testing shows that it seems to be a change to the mainline linux kernel since the v3.3 kernel Hopeful this can be resolve before the quantal release or this bug will break glusterfs for everyone using quantal with ext4 bricks. -- 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
[Bug 1022500] Re: ext4 d_off values too high
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages. Once you've tested the upstream kernel, please remove the 'needs- upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream-testing' text. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc6-quantal/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Importance: Medium = High ** Tags added: needs-upstream-testing ** Tags added: kernel-key ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- 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
[Bug 1022500] Re: ext4 d_off values too high
tested with the kernel from that link: Linux test-kernel 3.5.0-030500rc6-generic #201207072135 SMP Sun Jul 8 01:35:57 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Bug not fixed. ** Tags removed: needs-upstream-testing ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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
[Bug 1022500] Re: ext4 d_off values too high
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report. [1] https://wiki.ubuntu.com/Bugs/Upstream/kernel -- 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
