* RE: Server IP address change screws up active mounts
@ 2004-05-17 16:17 Murata, Dennis W (SAIC)
2004-05-19 0:15 ` H. Peter Anvin
0 siblings, 1 reply; 6+ messages in thread
From: Murata, Dennis W (SAIC) @ 2004-05-17 16:17 UTC (permalink / raw)
To: Ian Kent, David Meleedy; +Cc: autofs
We experienced similar problems using autofs-3.x with both RedHat(7.3,
8.0, 2.1, 9.0) and Slackware(9.0). This seems to be fixed with
autofs-4.x. We have used 4.0.0-pre10 for a couple of years without
problem and are now trying 4.1.2.
The problems we were seeing dealt with and automounted nfs server not
responding, the mount would hang, autofs would not timeout and would
hang, only a hard reset would reboot the computer.
Wayne
-----Original Message-----
From: autofs-bounces@linux.kernel.org
[mailto:autofs-bounces@linux.kernel.org]On Behalf Of Ian Kent
Sent: Thursday, May 13, 2004 9:13 PM
To: David Meleedy
Cc: autofs@linux.kernel.org
Subject: Re: [autofs] Server IP address change screws up active mounts
On Thu, 13 May 2004, David Meleedy wrote:
>
> One question I had for you guys happened to us when we were moving
> our subnets to an internal 10. net. We were using autofs version 3
> on redhat 8, and I haven't had a chance to test this with version 4
> yet, but the problem might still exist.
>
> If the redhat client using automounter had mounted a directory from
some
> server (so the mount was active), and then we changed the IP address
of
> the server, the automounter would hang on that mount forever after.
In fact
> we couldn't even do "init 6", we had to do "reboot -f" to get
> the client working again. To compare, with our Solaris machines,
> we didn't have this problem. The new IP address was discovered and
> the mount continued to work.
You must post this to the nfs list.
>
> So I'm not really sure if this is an automount issue, or a mount
command issue,
> but I figured you guys would be the right ones to ask. I definitely
> think this issue should be fixed, it's not that uncommon to move
> servers to new IP addresses.
Sounds like an issue with NFS or mount.
It sounds a bit strange though. It's been my impression that these types
of behaviour have improved greatly in later kernel versions.
What are the versions of:
kernel
util-linux
autofs
Ian
_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Server IP address change screws up active mounts
2004-05-17 16:17 Server IP address change screws up active mounts Murata, Dennis W (SAIC)
@ 2004-05-19 0:15 ` H. Peter Anvin
0 siblings, 0 replies; 6+ messages in thread
From: H. Peter Anvin @ 2004-05-19 0:15 UTC (permalink / raw)
To: Murata, Dennis W (SAIC); +Cc: autofs, David Meleedy, Ian Kent
Murata, Dennis W (SAIC) wrote:
> We experienced similar problems using autofs-3.x with both RedHat(7.3,
> 8.0, 2.1, 9.0) and Slackware(9.0). This seems to be fixed with
> autofs-4.x. We have used 4.0.0-pre10 for a couple of years without
> problem and are now trying 4.1.2.
> The problems we were seeing dealt with and automounted nfs server not
> responding, the mount would hang, autofs would not timeout and would
> hang, only a hard reset would reboot the computer.
>
It wouldn't have anything to do with autofs, though. Rather, it's an
NFS problem.
-hpa
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: Server IP address change screws up active mounts
@ 2004-05-19 20:05 Murata, Dennis W (SAIC)
0 siblings, 0 replies; 6+ messages in thread
From: Murata, Dennis W (SAIC) @ 2004-05-19 20:05 UTC (permalink / raw)
To: H. Peter Anvin; +Cc: autofs, David Meleedy, Ian Kent
The nfs server not responding is indeed an NFS problem, however, using
autofs 3.x, if you tried to stop and restart the automounter or reboot
the workstation it would hang trying to kill automount. Only a power
cycle would reboot the workstation. When we switched to
autofs-4.0.0pre10, you will getting messages about trying to unmount
directories, but eventually (~30 seconds) autofs would timeout(?) then
continue the reboot, or allow you to start the service back up again.
The only change was the upgrade to autofs-4.0.0pre10.
Wayne
-----Original Message-----
From: H. Peter Anvin [mailto:hpa@zytor.com]
Sent: Tuesday, May 18, 2004 7:15 PM
To: Murata, Dennis W (SAIC)
Cc: Ian Kent; David Meleedy; autofs@linux.kernel.org
Subject: Re: [autofs] Server IP address change screws up active mounts
Murata, Dennis W (SAIC) wrote:
> We experienced similar problems using autofs-3.x with both RedHat(7.3,
> 8.0, 2.1, 9.0) and Slackware(9.0). This seems to be fixed with
> autofs-4.x. We have used 4.0.0-pre10 for a couple of years without
> problem and are now trying 4.1.2.
> The problems we were seeing dealt with and automounted nfs server not
> responding, the mount would hang, autofs would not timeout and would
> hang, only a hard reset would reboot the computer.
>
It wouldn't have anything to do with autofs, though. Rather, it's an
NFS problem.
-hpa
^ permalink raw reply [flat|nested] 6+ messages in thread
* Server IP address change screws up active mounts
@ 2004-05-13 21:40 David Meleedy
2004-05-14 2:12 ` Ian Kent
2004-05-17 20:11 ` mmarion
0 siblings, 2 replies; 6+ messages in thread
From: David Meleedy @ 2004-05-13 21:40 UTC (permalink / raw)
To: autofs
One question I had for you guys happened to us when we were moving
our subnets to an internal 10. net. We were using autofs version 3
on redhat 8, and I haven't had a chance to test this with version 4
yet, but the problem might still exist.
If the redhat client using automounter had mounted a directory from some
server (so the mount was active), and then we changed the IP address of
the server, the automounter would hang on that mount forever after. In fact
we couldn't even do "init 6", we had to do "reboot -f" to get
the client working again. To compare, with our Solaris machines,
we didn't have this problem. The new IP address was discovered and
the mount continued to work.
So I'm not really sure if this is an automount issue, or a mount command issue,
but I figured you guys would be the right ones to ask. I definitely
think this issue should be fixed, it's not that uncommon to move
servers to new IP addresses.
Thanks!
-Dave
________________________________________________________________________
David Meleedy Analog Devices, Inc.
David.Meleedy@analog.com Three Technology Way
Phone: 781 461 3494 Norwood, MA 02062-9106 USA
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Server IP address change screws up active mounts
2004-05-13 21:40 David Meleedy
@ 2004-05-14 2:12 ` Ian Kent
2004-05-17 20:11 ` mmarion
1 sibling, 0 replies; 6+ messages in thread
From: Ian Kent @ 2004-05-14 2:12 UTC (permalink / raw)
To: David Meleedy; +Cc: autofs
On Thu, 13 May 2004, David Meleedy wrote:
>
> One question I had for you guys happened to us when we were moving
> our subnets to an internal 10. net. We were using autofs version 3
> on redhat 8, and I haven't had a chance to test this with version 4
> yet, but the problem might still exist.
>
> If the redhat client using automounter had mounted a directory from some
> server (so the mount was active), and then we changed the IP address of
> the server, the automounter would hang on that mount forever after. In fact
> we couldn't even do "init 6", we had to do "reboot -f" to get
> the client working again. To compare, with our Solaris machines,
> we didn't have this problem. The new IP address was discovered and
> the mount continued to work.
You must post this to the nfs list.
>
> So I'm not really sure if this is an automount issue, or a mount command issue,
> but I figured you guys would be the right ones to ask. I definitely
> think this issue should be fixed, it's not that uncommon to move
> servers to new IP addresses.
Sounds like an issue with NFS or mount.
It sounds a bit strange though. It's been my impression that these types
of behaviour have improved greatly in later kernel versions.
What are the versions of:
kernel
util-linux
autofs
Ian
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Server IP address change screws up active mounts
2004-05-13 21:40 David Meleedy
2004-05-14 2:12 ` Ian Kent
@ 2004-05-17 20:11 ` mmarion
1 sibling, 0 replies; 6+ messages in thread
From: mmarion @ 2004-05-17 20:11 UTC (permalink / raw)
To: autofs
On 13 May, David Meleedy wrote:
> One question I had for you guys happened to us when we were moving
> our subnets to an internal 10. net. We were using autofs version 3
> on redhat 8, and I haven't had a chance to test this with version 4
> yet, but the problem might still exist.
It still exists in autofs4 because, like Dennis said, it's really a mount/nfs
issue, not autofs. If you run a mount -t nfs you'll note that the IP of the
server is stored in the mount into.
It's ugly, but one fix I've found to clear these up is to temporarily setup an
aliased ethernet entry with the IP of the server and netmask 255.255.255.255
(so you don't lose contact with a whole network), umount the mount, then shut
down that aliased ethernet entry, and let automounter remount the path on the
hosts' new ip. This is on each client btw.
i.e. if the host was 10.0.0.10 and is now 10.0.1.10, mount will show something
like:
myhost:/some/path on /some/path type nfs
(rw,noquota,addr=10.0.0.10)
do something like:
ifconfig eth0:1 inet 10.0.0.10 netmask 255.255.255.255 up
umount /some/path
ifconfig eth0:1 down
ls /some/path so that automount remounts it on new host ip... and you
should be ok.
I'm working on an audit script to do just this on our /net path, because /net
is used by a lot of our engineers to access other desktop's local disk/scratch
space, and when users' move... the machines move and often get re-IPd. I've
noted that when a box moves, and then things like df hang, the automount daemon
on /net will hang when checking for paths to expire and will never expire any
anymore. It will however still respond to and mount new /net requests. So
eventually a host can hit the max number of allowable mounts.
--
Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com
[Joe just pulled Antonio away from a beautiful woman he was talking to, to move
a cabinet a tiny bit]
Antonio: "We barely moved it!" Joe: "Yeah I know, but it was askew! Isn't it
amazing how something like that can throw off your whole day?"
Antonio: "Yes, and you know I only wish I could stay and slap you senseless..
but there's a goddess waiting for me in the terminal." -- Wings
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2004-05-19 20:05 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-05-17 16:17 Server IP address change screws up active mounts Murata, Dennis W (SAIC)
2004-05-19 0:15 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2004-05-19 20:05 Murata, Dennis W (SAIC)
2004-05-13 21:40 David Meleedy
2004-05-14 2:12 ` Ian Kent
2004-05-17 20:11 ` mmarion
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.