It looks like this is a bug that has already been fixed upstream by
commit
commit bd9db175dde14b606265e0d37e8319d96fe1a58f
Author: Zheng Liu <wenqing...@taobao.com>
Date: Mon Jun 2 10:48:22 2014 -0400
ext4: handle symlink properly with inline_data
I've uploaded a Trusty test kernel containing this commit here:
http://people.canonical.com/~henrix/lp1349020/amd64/
Could you please verify if it fixes the bug for you? Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1349020
Title:
inline_data option on ext4 truncates symlinks
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
To replicate the bug, create two filesystems, one with `mkfs.ext4 -I
256`, one with `mkfs.ext4 -I 256 -O inline_data`. An inode size of 256
bytes is the default, but included here for clarity. To do this, you
are going to need an `e2fsprogs` from trunk, or version 1.43 if it has
been released.
Mount the two filesystems, in each of them do:
$ ln -s $(for i in {1..64}; do echo -n .; done) 64
$ ln -s $(for i in {1..128}; do echo -n .; done) 128
$ ln -s $(for i in {1..192}; do echo -n .; done) 192
$ ls -l 64 128 192
Both directory listings will show symlinks named `64`, `128` and
`256`, each pointing to a filename with the corresponding amount of
dots. This is the expected behavior.
Unmount both filesystems, mount them again. Do the `ls -l` again.
The default filesystem will show the same output as previously, the
one with inline_data activated will show the `128` symlink pointing to
a filename of only 64 dots.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-32-generic 3.13.0-32.57
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: clacke 3532 F.... pulseaudio
CurrentDesktop: GNOME
Date: Sun Jul 27 00:47:06 2014
EcryptfsInUse: Yes
MachineType: LENOVO IdeaPad Z370
ProcFB:
0 inteldrmfb
1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic
root=/dev/mapper/hostname-trusty_root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.13.0-32-generic N/A
linux-backports-modules-3.13.0-32-generic N/A
linux-firmware 1.127.5
SourcePackage: linux
StagingDrivers: rts5139
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/29/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 4ACN35WW
dmi.board.name: KL5
dmi.board.vendor: LENOVO
dmi.board.version: Rev 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Rev 1.0
dmi.modalias:
dmi:bvnLENOVO:bvr4ACN35WW:bd08/29/2011:svnLENOVO:pnIdeaPadZ370:pvrRev1.0:rvnLENOVO:rnKL5:rvrRev1.0:cvnLENOVO:ct10:cvrRev1.0:
dmi.product.name: IdeaPad Z370
dmi.product.version: Rev 1.0
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349020/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
