Re: find command misbehaves on debian with kernel 4.9
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 07/20/2017 08:25 PM, Anthony DeRobertis wrote:
> I tried this on a VM running Jessie w/ the bpo kernel. It
> reproduces here.
>
> vm:~# echo 1 > /proc/sys/vm/drop_caches vm:~# cd / vm:/# find .
> -name "*systemd-resolved*"
> ./usr/share/man/man8/systemd-resolved.service.8.gz
> ./usr/share/man/man8/systemd-resolved.8.gz vm:/# find . -name
> "*systemd-resolved*"
> ./usr/share/man/man8/systemd-resolved.service.8.gz
> ./usr/share/man/man8/systemd-resolved.8.gz
> ./lib/systemd/system/systemd-resolved.service
> ./lib/systemd/systemd-resolved
>
> Although it only happened once. I tried another 20-odd times, even
> using 3 for drop_caches, and couldn't make it happen again.
>
> But on another VM, on the first try. So apparently drop_caches
> isn't strong enough to make it happen again
>
It happens after every reboot on a virtual machine with Debian jessie
and backport kernel 4.9. Filesystem is ext4 and the storage device is
a SSD disk. The problem is not limited to this search term only. I
think it happens when there's an asterisk in the search phrase. For
example the first output of this:
root@localhost:/#find . -name "*apache*"
is also wrong.
-----BEGIN PGP SIGNATURE-----
iQFMBAEBCAA2FiEEj2P+5uDa2IXpZ1f/tTM9/Ar9ka8FAllw1QEYHHNpcnVzLnNo
YWhpbmlAZ21haWwuY29tAAoJELUzPfwK/ZGvWUQH/RAq6rHZZdZVfsStO9MAOjWP
hZjOeUWegPMahAJwWrkf/MjYOzy7ORUW5rdzYD20xSFbuBfbE8iLP7giNtmpuMUp
U9hEWBQ7grbzVgMKko82B90AWgV75Mon2UTvbAxhDKdhGdI+5Z1srlYtsx3rmiqO
pxWx5ByZkshZ3VqbarA8mf4PpSEyiWsAWc+5xpF29Y11jl8/VsHxAimn515bRwHw
vHoAQcuJLJ7aslkcGi3g3tCMTEtebAdpkb3FuBrp4Yt+KXkjMxjoTRysya2rcjpn
Wb+ElqRgWh+6CH9UswtLApsWuIPobZnUgs2ioScez6JNltFPMsD6FEgZXAsOVAk=
=IPhS
-----END PGP SIGNATURE-----
Reply to: