Bug 24593

Summary: NFS hang between stable and current boxes
Product: Base System Reporter: jsmethers <jsmethers>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description jsmethers 2001-01-24 07:50:01 UTC 
Both boxes NFS hung at the same time with each reporting a mount from the other machine not responding. In the case of the -stable machine it was the -current box's /mnt mounted on /var/ftp/incoming and on the -current machine it was the -stable box's /. The -stable box reports the -current box not responding at 3:22AM. ps -x on the -stable box reports the suspicious unkillable process:

"root 31885 0.0 0.7 896 448 ?? D 3:22AM 0:00.19 find /var -xdev -type f ( -perm -u+x -or perm -g+x -"

which I summize is from the scripts in /etc.

Unfortunatly on both boxes a mount related command (e.g. df, umount) hang a login and don't respond to kill -9 so I am not able to obtain any more information from the -current box untill it reboots.

I was about the put the latest snap on the -current box too. =/

How-To-Repeat: I'd guess running the security script in /etc that runs the find on /var while /var contains a NFS mount within its hierarchy.
Comment 1 jsmethers 2001-01-24 08:08:03 UTC 
The -current box actually hung for any utility run on it. As an
interesting side effect it also hung during shutdown because it tried
to write the entropy file and thus required a physical reset of the
machine.

The -stable box got to the "syncing disks... done" and then also
required a physical reset.

- Jason
Comment 2 iedowse freebsd_committer freebsd_triage 2001-11-18 20:20:59 UTC 
State Changed
From-To: open->feedback


Does this problem still occur?
Comment 3 iedowse freebsd_committer freebsd_triage 2002-03-02 17:05:08 UTC 
State Changed
From-To: feedback->closed


Feedback timeout.