Re: error message, what does this mean?
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 majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: error message, what does this mean?
As Bruce Evans wrote ... 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. Hmm. Never seen it before. But doing a cd / ; find . -fstype ufs -print | cpio -pudm /mnt works like a charm without the vnode_pager messages. So looks like procfs alright. | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: error message, what does this mean?
As Matthew Dillon wrote ... :etc : :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 ?? : :| / o / / _Arnhem, The Netherlands- Powered by FreeBSD - :|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org It seems to me that a cp command like is probably trying to cp -R /mnt to /mnt ... /* will include /mnt, right? I'm not sure what would be causing the errors, though, unless the cp is recursing endlessly due to the cp of /mnt on top of /mnt and running the filesystem out of space... In the end that happens, but not after a couple of seconds already. I'm quite sure it is the copying of /proc that triggers the messages. The VT_PROCFS like in May 28 10:04:15 p100 /kernel: tag VT_PROCFS, type 6, pid 193, mode 180, flags 0 also seems to indicate this. If I do: cd / ; find . -fstype ufs -print | cpio -pdum /mnt it works just fine without messages (of course until /mnt becomes full like you mention above). I've never seen this procfs behaviour before BTW. | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
error message, what does this mean?
Hi My P100 testbox running a fairly recent current just said: 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, 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: vnode_pager_getpages: I/O read error May 27 23:39:23 p100 /kernel: vm_fault: pager read error, pid 252 (cp) 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: : 0xc36002c0: type VREG, usecount 4, writecount 0, refcount 0, flags (VOBJBUF) etc 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 ?? | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: error message, what does this mean?
:etc : :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 ?? : :| / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - :|/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org It seems to me that a cp command like is probably trying to cp -R /mnt to /mnt ... /* will include /mnt, right? I'm not sure what would be causing the errors, though, unless the cp is recursing endlessly due to the cp of /mnt on top of /mnt and running the filesystem out of space... -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
