From owner-freebsd-current Tue Mar 16 12:53:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 89A3014D9C for ; Tue, 16 Mar 1999 12:52:57 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA12300; Tue, 16 Mar 1999 12:52:32 -0800 (PST) (envelope-from dillon) Date: Tue, 16 Mar 1999 12:52:32 -0800 (PST) From: Matthew Dillon Message-Id: <199903162052.MAA12300@apollo.backplane.com> To: Pierre Beyssac Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: vfs_busy: unexpected lock failure References: <19990315174734.A400@enst.fr> <199903152124.NAA02779@apollo.backplane.com> <19990316111040.A384@enst.fr> <199903161911.LAA11778@apollo.backplane.com> <19990316213355.A4561@enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :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 pid156@bofh:/xyz lines removed ] :pid156@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 pb@enst.fr Ahhhh.. And if you make those AMD mounts normal nfs mounts it doesn't fry? If so, then we have a bug in AMD somewhere. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message