/net

DISCUSSION Bryan Simmons 2 participants 4 messages Oct 30, 2002

Share & tools

Bryan Simmons

author

2002-10-30 00:23 UTC #0 lore raw

I'm still recovering from upgrading into almost a completely new system. I thought I didn't install NFS and samba and the other network file system stuff, but it seems it's there anyway.

Anyway, when the system is shutting down or rebooting, just after the umount command is given, I get the error: umount2: <something about RPC not being found>: umount /net: device busy
and right there, all attempts to shutdown/reboot are ended. The system just sits there. The only thing I can do is hit the reset button. If not for XFS, I'd be running fsck at every frickin reboot.

I have an AthlonXP 2100+ system, integrated ethernet, adsl connex (started at boot and not stopped manually at all). Can't think of what else is important here. Can anyone tell me how to make this go away? I tried to disable nfslock and nfs at boot (set to start manually), but it frickin started anyway.

Thanks guys!!!

Signature · 7 lines

Bryan Simmons <[email protected]>

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Ray Olszewski

2002-10-30 01:32 UTC #1 lore raw

It's hard to be sure from a fragmentary report, but the "something about RPC not being found" probably refers to the portmapper daemon (which runs as /sbin/portmap on my systems) that is used by mountd . Is it running prior to the the start of the halt or reboot process? And you need to tell us what is mounted as /net (look in /etc/fstab to find out, if you don't know, or look at the output of "df").

Usually, a "device busy" error from umount means that some active process is using the partition that umount is trying to unmount. Without more detail, I don't know what that might be at this point in the halt or reboot sequence. You might check this with "lsof" just before you halt or reboot. Indeed, you might even try umount'ing /net by hand, to track down the source of the conflict.

As to "what else is important", it never hurts to mention what Linux distro and version is involved (even if it seems like you are repeating yourself again and again; there's enough traffic on help lists to make it tough for me, and probably others, to remember the configurations others have). Also, *how* you "tried" to disable nfslock and nfs.

Also ... "The only thing I can do is hit the reset button" ... you are probably right, but did you try CTRL-C? It probably won't work right at this spot, but it might ... the shutdown process really is just "init" running a bunch of scripts, and you can sometimes SIGTERM out of them.

Quoted 11 lines · Bryan Simmons

I'm still recovering from upgrading into almost a completely new system. I thought I didn't install NFS and samba and the other network file system stuff, but it seems it's there anyway.
Anyway, when the system is shutting down or rebooting, just after the umount command is given, I get the error: umount2: <something about RPC not being found>: umount /net: device busy
and right there, all attempts to shutdown/reboot are ended. The system just sits there. The only thing I can do is hit the reset button. If not for XFS, I'd be running fsck at every frickin reboot.

Quoted 5 lines

I have an AthlonXP 2100+ system, integrated ethernet, adsl connex (started at boot and not stopped manually at all). Can't think of what else is important here. Can anyone tell me how to make this go away? I tried to disable nfslock and nfs at boot (set to start manually), but it frickin started anyway.

--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [email protected]
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Bryan Simmons

author

2002-10-30 02:29 UTC #2 lore raw

Here is what /etc/mtab says about /net:

brainpress:(pid1532) /net nfs intr,rw,port=1023,timeo=8,retrans=110,indirect,map =/etc/amd.net,dev=0000000b 0 0
automount(pid1622) /net autofs rw,fd=5,pgrp=1622,minproto=2,maxproto=4 0 0

Here's what I know: I'm running Mandrake 9.0 kernel 2.4.19-16mdk. In the "services" configuration (which sets up what daemons and other services start at boot automatically etc...) I tried to stop netfs and nfslock by stopping them and changing their startup to "manual" instead of "on boot". But it didn't take. In the syslog logfile it says that amd was the last process to mount /net. The only reason I installed these services is because I am planning on putting this machine on a home network with a WinXP box. Could it be having problems because there is nothing to find in the /net folder? Since it is not listed in /etc/fstab is there any way to get rid of it?

Thanks again!!

Quoted 57 lines · Ray Olszewski

It's hard to be sure from a fragmentary report, but the "something about RPC not being found" probably refers to the portmapper daemon (which runs as /sbin/portmap on my systems) that is used by mountd . Is it running prior to the the start of the halt or reboot process? And you need to tell us what is mounted as /net (look in /etc/fstab to find out, if you don't know, or look at the output of "df").
Usually, a "device busy" error from umount means that some active process is using the partition that umount is trying to unmount. Without more detail, I don't know what that might be at this point in the halt or reboot sequence. You might check this with "lsof" just before you halt or reboot. Indeed, you might even try umount'ing /net by hand, to track down the source of the conflict.
As to "what else is important", it never hurts to mention what Linux distro and version is involved (even if it seems like you are repeating yourself again and again; there's enough traffic on help lists to make it tough for me, and probably others, to remember the configurations others have). Also, *how* you "tried" to disable nfslock and nfs.
Also ... "The only thing I can do is hit the reset button" ... you are probably right, but did you try CTRL-C? It probably won't work right at this spot, but it might ... the shutdown process really is just "init" running a bunch of scripts, and you can sometimes SIGTERM out of them.
Quoted 11 lines · Bryan Simmons
I'm still recovering from upgrading into almost a completely new system. I thought I didn't install NFS and samba and the other network file system stuff, but it seems it's there anyway.
Anyway, when the system is shutting down or rebooting, just after the umount command is given, I get the error: umount2: <something about RPC not being found>: umount /net: device busy
and right there, all attempts to shutdown/reboot are ended. The system just sits there. The only thing I can do is hit the reset button. If not for XFS, I'd be running fsck at every frickin reboot.
Quoted 5 lines
I have an AthlonXP 2100+ system, integrated ethernet, adsl connex (started at boot and not stopped manually at all). Can't think of what else is important here. Can anyone tell me how to make this go away? I tried to disable nfslock and nfs at boot (set to start manually), but it frickin started anyway.
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [email protected]
-------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Signature · 7 lines

Bryan Simmons <[email protected]>

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Ray Olszewski

2002-10-30 02:48 UTC #3 lore raw

I can't help you too much, Bryan, but maybe just enough to let you move ahead.

This mount point is managed by amd (AutoMount Daemon), which I do not use. You might look through your init scripts to find the one that invokes it, then modify the script or disable it completely (depending on whether it does other things you still need done). Or maybe Mandrake's "services" configuration offers a way to control amd.

Beyond that ... you still need to use "lsof" to find out what process has something in that directory (or perhaps the directory itself) open to interfere with the umount command. Or the control file "/etc/amd.net" may contain illuminating information.

Quoted 8 lines · Bryan Simmons

Here is what /etc/mtab says about /net:
brainpress:(pid1532) /net nfs intr,rw,port=1023,timeo=8,retrans=110,indirect,map =/etc/amd.net,dev=0000000b 0 0
automount(pid1622) /net autofs rw,fd=5,pgrp=1622,minproto=2,maxproto=4 0 0

Quoted 10 lines

Here's what I know: I'm running Mandrake 9.0 kernel 2.4.19-16mdk. In the "services" configuration (which sets up what daemons and other services start at boot automatically etc...) I tried to stop netfs and nfslock by stopping them and changing their startup to "manual" instead of "on boot". But it didn't take. In the syslog logfile it says that amd was the last process to mount /net. The only reason I installed these services is because I am planning on putting this machine on a home network with a WinXP box. Could it be having problems because there is nothing to find in the /net folder? Since it is not listed in /etc/fstab is there any way to get rid of it?