Use RAID disks, Logical Volume Manager and/or clustering. All of these
features are downloadable.
Paul Anderson
"Ashley M. Kirchner" wrote:
> Past experience has taught me that if an NFS server happens to go
> down for whatever reason (and then restarted), the machines connected to
> it will be in a state of 'being stuck' and the only way to fix that is
> to either try to unmount those NFS volumes, and remount them, or to
> restart the client (which solves the problem all together).
>
> Is there any better mechanism to check for things like this
> automatically? If the NFS server gets rebooted, or the connection died
> long enough for the clients to lose it. What can be done? Is there any
> specific way I should set the clients up to reconnect or something?
>
> For that matter, if and when the NFS server goes down, is there any
> way of telling the clients to stop trying to use that particular mounted
> volume, and switch to a local (mirrored) partition till the NFS server
> comes back up?
>
> AMK4
>
> --
> W |
> | I haven't lost my mind; it's backed up on tape somewhere.
> |____________________________________________________________________
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Ashley M. Kirchner <mailto:[EMAIL PROTECTED]> . 303.442.6410 x130
> SysAdmin / Websmith . 800.441.3873 x130
> Photo Craft Laboratories, Inc. . eFax 248.671.0909
> http://www.pcraft.com . 3550 Arapahoe Ave #6
> .................. . . . . Boulder, CO 80303, USA
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
