[Help]Cannot read symbolic link, Invalid argument

[Help]Cannot read symbolic link, Invalid argument

[kagamine rinfans]

Hello. I met a bug and want your help. When I run a container by
docker for a long time, some problems appeared.
In the container, a symbolic link has been broken.The filesystem is
overlay. The symlink libipfwinner.so point to libipfwinner.so.0.0.0.5.

Device Info:
sh-4.2$ uname -a
Linux xx 4.9.29 #1 SMP PREEMPT Fri Dec 21 16:00:00 CST 2018 x86_64
x86_64 x86_64 GNU/Linux

sh-4.2$ df
Filesystem     1K-blocks    Used Available Use% Mounted on
overlay          7891460 2300196   5591264  30% /

Normal:
sh-4.2$ ls  /lib/ -ll | grep libipfw
lrwxrwxrwx 1 root root       23 Feb 21 09:31 libipfwinner.so ->
libipfwinner.so.0.0.0.5
-rwxr-xr-x 1 root root    69808 Feb 21 09:31 libipfwinner.so.0.0.0.5

Bug：
sh-4.2$ ls /lib/ -ll | grep libipfwinner
ls: cannot read symbolic link /lib/libipfwinner.so: Invalid argument
lrwxrwxrwx 1 root root       23 Feb 22 09:42 libipfwinner.so
-rwxr-xr-x 1 root root    69808 Feb 22 09:42 libipfwinner.so.0.0.0.5

sh-4.2$ cat libipfwinner.so
cat: libipfwinner.so: Too many levels of symbolic links


I think it might be a bug of overlayfs.I cannot reproduce this
problem.It only happened once.

I hope you can give me some advice.Thanks!

Re: [Help]Cannot read symbolic link, Invalid argument

[Amir Goldstein]

On Mon, Mar 11, 2019 at 8:36 AM kagamine rinfans <maykagura@gmail.com> wrote:
>
> Hello. I met a bug and want your help. When I run a container by
> docker for a long time, some problems appeared.
> In the container, a symbolic link has been broken.The filesystem is
> overlay. The symlink libipfwinner.so point to libipfwinner.so.0.0.0.5.
>
> Device Info:
> sh-4.2$ uname -a
> Linux xx 4.9.29 #1 SMP PREEMPT Fri Dec 21 16:00:00 CST 2018 x86_64
> x86_64 x86_64 GNU/Linux
>
> sh-4.2$ df
> Filesystem     1K-blocks    Used Available Use% Mounted on
> overlay          7891460 2300196   5591264  30% /
>
> Normal:
> sh-4.2$ ls  /lib/ -ll | grep libipfw
> lrwxrwxrwx 1 root root       23 Feb 21 09:31 libipfwinner.so ->
> libipfwinner.so.0.0.0.5
> -rwxr-xr-x 1 root root    69808 Feb 21 09:31 libipfwinner.so.0.0.0.5
>
> Bug：
> sh-4.2$ ls /lib/ -ll | grep libipfwinner
> ls: cannot read symbolic link /lib/libipfwinner.so: Invalid argument
> lrwxrwxrwx 1 root root       23 Feb 22 09:42 libipfwinner.so
> -rwxr-xr-x 1 root root    69808 Feb 22 09:42 libipfwinner.so.0.0.0.5
>
> sh-4.2$ cat libipfwinner.so
> cat: libipfwinner.so: Too many levels of symbolic links
>
>
> I think it might be a bug of overlayfs.I cannot reproduce this
> problem.It only happened once.
>

Not much to go with.
If you have overelayfs warnings/errors from kernel log
that could shed some light.

Thanks,
Amir.