The bug has been fixed in -proposed.
Performed the test in the bug description. The `128` file accurately
points to a 128 bytes long filename. Double-checked that the file system
was actually using -O inline_data. Disk usage reflects it as well:
# du ext4{,_inline}/test{/*,}
4 ext4/test/128
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
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 sym
That fixes the bug. Even symlinks created by the faulty kernel will be
interpreted correctly by the fixed kernel, as the fault is in reading,
not in writing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
** Description changed:
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
Public bug reported:
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 h
5 matches
Mail list logo
