Messages in this thread | | | From | Andreas Dilger <> | Subject | Re: regression: 4.13 cannot follow symlinks on some ext3 fs | Date | Thu, 23 Nov 2017 17:41:04 -0700 |
| |
On Nov 23, 2017, at 4:31 PM, Andi Kleen <andi@firstfloor.org> wrote: > > On Thu, Nov 23, 2017 at 05:23:17PM -0500, Theodore Ts'o wrote: >> On Thu, Nov 23, 2017 at 12:33:30PM -0800, Andi Kleen wrote: >>> >>> I have an older qemu VM image that i sometimes use for testing. It >>> stopped booting with 4.13-4.14 because it couldn't run init. >>> It uses ext3 for the root file system. >> >> Hmm, do you know roughly when (what krenel version) this image was >> created? We had done quite a lot of research and the belief was >> kernels never would create a "slow" symlink which was less than 60 >> bytes. > > The date of the inode is from 2007, the original kernel was 2.6.17 > with a 32bit kernel. > >> Or was this image something that was created manually (e.g., using debugfs)? > > No, it was installed.
As a workaround, you could delete and recreate the symlink with the new kernel to create a proper fast symlink. It would be useful to scan the image to see if there are other similar symlinks present:
find /myth/tmp -type l -size -60 -ls | awk '$2 != 0 { print }'
This is probably something that e2fsck should check for and fix.
Cheers, Andreas
[unhandled content-type:application/pgp-signature] | |