Re: panic: vfs_busy: unexpected lock failure

1999-03-18 Thread Peter Wemm
Matthew Dillon wrote: :On Tue, Mar 16, 1999 at 12:52:32PM -0800, Matthew Dillon wrote: : A.. And if you make those AMD mounts normal nfs mounts it doesn't : fry? If so, then we have a bug in AMD somewhere. : :I tried the cp several times again on a regular NFS mount, to

Re: panic: vfs_busy: unexpected lock failure

1999-03-18 Thread Garrett Wollman
On Thu, 18 Mar 1999 22:49:10 +0800, Peter Wemm pe...@netplex.com.au said: AMD is easy to upset, and that's bad because it's holding a mountpoint in / (ie: /host) which often gets hit by every single getcwd() call when it gets a lstat(/host...) or whatever. I think this is the single largest

Re: panic: vfs_busy: unexpected lock failure

1999-03-17 Thread Matthew Dillon
:On Tue, Mar 16, 1999 at 12:52:32PM -0800, Matthew Dillon wrote: : A.. And if you make those AMD mounts normal nfs mounts it doesn't : fry? If so, then we have a bug in AMD somewhere. : :I tried the cp several times again on a regular NFS mount, to make :sure, and no, it doesn't

Re: panic: vfs_busy: unexpected lock failure

1999-03-16 Thread Pierre Beyssac
On Mon, Mar 15, 1999 at 01:24:46PM -0800, Matthew Dillon wrote: Compile up a kernel with 'options DDB' and get a backtrace when it panics next ( 'trace' command from DDB prompt ). Ok, here goes. The kernel is compiled without -g for the moment, but I've provided the function offsets if

Re: panic: vfs_busy: unexpected lock failure

1999-03-16 Thread Matthew Dillon
:On Mon, Mar 15, 1999 at 01:24:46PM -0800, Matthew Dillon wrote: : Compile up a kernel with 'options DDB' and get a backtrace when : it panics next ( 'trace' command from DDB prompt ). : :Ok, here goes. The kernel is compiled without -g for the moment, :but I've provided the function

Re: panic: vfs_busy: unexpected lock failure

1999-03-16 Thread Pierre Beyssac
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

Re: panic: vfs_busy: unexpected lock failure

1999-03-16 Thread Matthew Dillon
: :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

Re: panic: vfs_busy: unexpected lock failure

1999-03-16 Thread Pierre Beyssac
On Tue, Mar 16, 1999 at 12:52:32PM -0800, Matthew Dillon wrote: A.. And if you make those AMD mounts normal nfs mounts it doesn't fry? If so, then we have a bug in AMD somewhere. I tried the cp several times again on a regular NFS mount, to make sure, and no, it doesn't seem to

panic: vfs_busy: unexpected lock failure

1999-03-15 Thread Pierre Beyssac
every time I try (with cp -rp; not with piped tars). The kernel is today's, with NFS compiled-in (it's not a module). I'm having the following message: panic: vfs_busy: unexpected lock failure -- Pierre Beyssac p...@enst.fr To Unsubscribe: send mail to majord...@freebsd.org

Re: panic: vfs_busy: unexpected lock failure

1999-03-15 Thread Matthew Dillon
happens every time I try (with cp -rp; :not with piped tars). : :The kernel is today's, with NFS compiled-in (it's not a module). : :I'm having the following message: : panic: vfs_busy: unexpected lock failure :-- :Pierre Beyssac p...@enst.fr Compile up a kernel with 'options DDB