On Tue, Mar 16, 1999 at 11:11:44AM -0800, Matthew Dillon wrote:
> (cnp->cn_flags & NOCROSSMOUNT) == 0) {
> if (vfs_busy(mp, 0, 0, p))
> continue;
...
> You shouldn't be crossing a mount point. Are you by chance doing a
> recursive copy onto itself?
> e.g. cp -rp src dest where dest is mounted under src somewhere ?
No. At first it was from a NFS-mounted volume to another NFS-mounted
volume. I then found that it panic'ed the same when I copied from
a local FFS volume to the same NFS volume.
The NFS volumes are automounted by amd under /a. That may well have
something to do with the panic: that's a recent change in my
configuration; I previously used NFS mounts in /etc/fstab which
didn't cause me any trouble.
> Of course, it is still a serious kernel bug. I would like to try
> to reproduce it in order to track it down. How are things mounted on
> your system ( df ) and what are the *exact* arguments you are using with
> cp?
Here's the df (I removed some of the amd dummy mount points).
$ df
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/wd0s1a 49583 34595 11022 76% /
/dev/wd1s1e 5975845 3556146 1941632 65% /home
/dev/wd0s1f 148823 1290 135628 1% /tmp
/dev/wd0s1g 5380597 1615221 3334929 33% /usr
/dev/wd0s1e 396895 38127 327017 10% /var
procfs 4 4 0 100% /proc
[ ten pid...@bofh:/xyz lines removed ]
pid...@bofh:/cal 0 0 0 100% /cal
huuh:/home/huuh 1217519 1064153 141191 88% /a/huuh/home/huuh
The failing cp is:
$ cp -rp /home/beyssac/src/sendmail-8.9.3/cf/ /home/beyssac/nfs/junk/
In the above, "/home/beyssac/nfs" is a symbolic link to
/cal/huuh/cal/beyssac which is automounted by amd (last line in
the above df).
--
Pierre Beyssac p...@enst.fr
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
