> :> I am noticing a large number of pine (and only pine) procs stuck in disk-wait.
> :> All of the are in the WCHAN "vmpfw". Any ideas what this may mean?
> :
> :Is the mail spool pine accessing on this NFS volume, or just the binary?
> :
> :If so you're breaking the cardinal rule of NFS: Never serve mail spools
> :via NFS.
> :
>
> Which FreeBSD release is being used here? What kind of NFS mount is
> being used (localhost mount?)
Ok, I have some additional details, as I was able to mostly resolve the issue.
Yes, mail is nfs exported, but that does not appear to be the issue in this
case. pine is run from nfs mounted "/usr/local" pine would hang every time
a user would go to send a composed message and wind up in "vmpfw". The "fix"
was to go to the NFS server for /usr/local and do "mv pine pine.old; cp
pine.old pine". This would (obviously) not affect any of the old pine's, it
would however allow any new pines to run w/o problems. Note that any access
to /usr/local/bin/pine.old on the client machine would result in a hang.
Specifically "file /usr/local/bin/pine.old" resulted in "vmpfw" as did "cmp"
and a couple of others. All of these worked just fine on the NFS server.
The release in question is 3.3-STABLE from this past Friday (Nov. 12).
--
David Cross | email: [EMAIL PROTECTED]
Acting Lab Director | NYSLP: FREEBSD
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Department of Computer Science | Fax: 518.276.4033
I speak only for myself. | WinNT:Linux::Linux:FreeBSD
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
