<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
Whit,<br>Thank you for those answers. I'll investigate UCARP and autofs and give you feedback<br><br>Anthony<br><br><br><div>> Date: Tue, 6 Sep 2011 09:00:31 -0400<br>> From: whit.gluster@transpect.com<br>> To: sokar6012@hotmail.com<br>> CC: whit.gluster@transpect.com; gluster-users@gluster.org<br>> Subject: Re: [Gluster-users] How to know clients currently connected ?<br>> <br>> > In my understanding of autofs is that it will mount as you need the<br>> > filesystem but will it remount the FS when there is a server crash ?<br>> <br>> Anthony,<br>> <br>> I haven't specifically tested it in this precise context, but in general<br>> that's exactly what it does. We went to using autofs because we had a server<br>> that was prone to crash. With autofs, as soon as that server came back up,<br>> it got remounted. Very reliable for that.<br>> <br>> When a server crashes the mount goes away. When you ask for a filesystem<br>> with autofs, if it's not there, it tries to mount it. I don't see how it can<br>> even know if you've switched which system has the IP and filesystem it's<br>> trying to mount. I know for sure it works well in a setup with<br>> DRBD/Heartbeat/NFS, so it ought to work as well for Gluster/UCARP/NFS. From<br>> autofs's perspective, it's just NFS.<br>> <br>> Whit<br>> <br></div> </div></body>
</html>