Date: Sun, 15 Jun 2014 13:28:32 +0300 From: Kimmo Paasiala <kpaasial@icloud.com> To: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: Odd problem with find(1) on FUSE sshfs mounted filesystems Message-ID: <696F97DE-5581-460E-B2B3-FFC43BCCBC00@icloud.com> In-Reply-To: <996494CC-21F5-4476-8E5E-22F5E5E673DD@icloud.com> References: <996494CC-21F5-4476-8E5E-22F5E5E673DD@icloud.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On 13.6.2014, at 9.49, Kimmo Paasiala <kpaasial@icloud.com> wrote: > I’m on FreeBSD stable/10 r267390 on one of my systems and on FreeBSD 10.0-RELEASE-p5 i386 on another one. Both exhibit a strange behaviour when find(1) is used on a FUSE sshfs mounted filesystems. This an excerpt of a log from such run (I mounted FreeBSD sources on /mnt using sshfs): > > ... > mnt/contrib/ofed/libmlx4/autogen.sh^M > /mnt/contrib/ofed/libmlx4/mlx4.driver^M > /mnt/contrib/ofed/libmlx4/config^M > /mnt/contrib/ofed/libmlx4/Makefile.am^M > /mnt/contrib/openresolv^M > find: /mnt/contrib/openresolv/pdnsd.in: No such file or directory^M > find: /mnt/contrib/openresolv/resolvconf.8.in: No such file or directory^M > find: /mnt/contrib/openresolv/resolvconf.conf.5.in: No such file or directory^M > find: /mnt/contrib/openresolv/configure: No such file or directory^M > find: /mnt/contrib/openresolv/unbound.in: No such file or directory^M > find: /mnt/contrib/openresolv/named.in: No such file or directory^M > find: /mnt/contrib/openresolv/resolvconf.conf: No such file or directory^M > find: /mnt/contrib/openresolv/dnsmasq.in: No such file or directory^M > find: /mnt/contrib/openresolv/Makefile: No such file or directory^M > find: /mnt/contrib/openresolv/libc.in: No such file or directory^M > find: /mnt/contrib/openresolv/README: No such file or directory^M > find: /mnt/contrib/openresolv/resolvconf.in: No such file or directory^M > find: /mnt/contrib/openresolv: No such file or directory^M > /mnt/contrib/ntp^M > … > > > I can rsync(1) the files from the mounted filesystem just fine without any errors/corruption so clearly all the files and directories are there and accessible. > > Is this a problem in FUSE/sshfs or find(1) and how to start debugging this? > > I have tested with both FreeBSD and OS X as SSH servers and the same problem is present using both systems. > > In all of the tests I’ve done there are no mountpoints crossed, each mounted directory tree is on a single filesystem on the server. > > -Kimmo No one else has seen this behaviour? I’d like to use sshfs as a secure and less complicated replacement for NFS but if I can’t trust it to work with standard utilities like find(1) I’ll have to pass for now. -Kimmo [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJTnXVVAAoJEFvLZC0FWRVpkVUIAL2OSe0sXi63rKRJ9jq/vSnC /Ud815Y2CQPHIvspOtrqddo/R4MxgiyjYm5uB6CnpWOSshsYS38qkTavHjQh4YGI B6zUXP3V4023Ze6zjEZnYqlFSfIgONAkQFv8EyWztivlC8CK7VddgJKjLh8olD5+ 9J0iERxiKUkHvbBcDfIOligozv9Z0FViOa+Z1BQf8b5TksT7+BJ45E3lYornZGzH uGV21X/lzd5yAI46+0hkwiM2HclansKHmOvPuEpoJUQ2bpLTwTZoO2Hj6lzXyaJ4 HXUtxEDabpGG7Mexjnr0jZegy5YiB1KJGO+vCSAMIaRQXCINvlgGouwjS1YrDfc= =i4Kh -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?696F97DE-5581-460E-B2B3-FFC43BCCBC00>