On Thu, 12 Sep 2013 15:17:57 -0500 Andrew Deason <[email protected]> wrote:
> On Thu, 12 Sep 2013 14:15:21 +0200 > Christof Hanke <[email protected]> wrote: > > > [root@ht14 ~]# df /afs > > Filesystem 1K-blocks Used Available Use% Mounted on > > - 9000000 0 9000000 0% /afs > > [root@ht14 ~]# df > > Filesystem 1K-blocks Used Available Use% Mounted on > > /dev/mapper/system-root > > 5160576 2069520 2828912 43% / > > tmpfs 12297268 0 12297268 0% /dev/shm > > /dev/sda1 148742 56616 84446 41% /boot > > df: `afs': No such file or directory > > It's just trying to statfs the mount point according to /proc/mounts (or > /etc/mtab or whatever). The entry apparently has 'afs' in it, and not > '/afs', so the statfs fails. If you strace it, I assume that's what > you'll see. Maybe it would work if your cwd was / . > > I didn't think we controlled that information, though. Did you maybe > mount afs by mounting 'afs' instead of '/afs' ? Maybe cacheinfo or > -mountdir specified 'afs' as the mount dir? > indeed that was the case on this machine. Playing around with this, I found lots of funny stuff, when the mountdir was not an absolute path. Thus, I propose to reject relative mountdirs in the cacheinfo-file. See http://gerrit.openafs.org/#change,10250 Many thanks, Christof _______________________________________________ OpenAFS-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
