From owner-freebsd-current  Thu May 27 23:18:46 1999
Delivered-To: freebsd-current@freebsd.org
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
	by hub.freebsd.org (Postfix) with ESMTP id 381D814D77
	for <freebsd-current@FreeBSD.ORG>; Thu, 27 May 1999 23:18:42 -0700 (PDT)
	(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA32640;
	Fri, 28 May 1999 16:18:40 +1000
Date: Fri, 28 May 1999 16:18:40 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199905280618.QAA32640@godzilla.zeta.org.au>
To: freebsd-current@FreeBSD.ORG, wilko@yedi.iaf.nl
Subject: Re: error message, what does this mean?
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>May 27 23:39:23 p100 /kernel: vnode_pager: *** WARNING *** stale FS getpages
>May 27 23:39:23 p100 /kernel: No strategy for buffer at 0xc13637e0 
>May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4,
>writecount 0,
> refcount 0, flags (VOBJBUF)
>May 27 23:39:23 p100 /kernel: tag VT_PROCFS, type 5, pid 252, mode 180,
>flags 0 
>May 27 23:39:23 p100 /kernel: : 0xc35ffd80: type VREG, usecount 4,
>...

>This was during a cp -R /* /mnt where /mnt is a SCSI disk I'm testing.
>Both disks are on seperate SCSI buses. Is this because the cp -R 
>tries to copy /proc ??

Probably.  Procfs has bugs that cause bad things to happen when some
files in it are copied.

Bruce


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message