On Thu, Dec 9, 2010 at 4:47 AM, Andrew Beekhof <span dir="ltr"><<a href="mailto:andrew@beekhof.net">andrew@beekhof.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Thu, Dec 9, 2010 at 9:04 AM, Florian Haas <<a href="mailto:florian.haas@linbit.com">florian.haas@linbit.com</a>> wrote:<br>
> On 2010-12-08 23:17, Mike Diehn wrote:<br>
</div><div class="im">>> While I waited to hear back from you, I tried this on our test cluster:<br>
>><br>
>> # bunch of primitives, then...<br>
>> group Shared-FS dlm clvm o2cb vg1 fs1<br>
>> clone Shared-FS_clone meta interleave="true"<br>
>><br>
>> and it seems to work.<br>
>><br>
>> Do you suppose I'm asking for trouble having all five resources in that<br>
>> one group?<br>
><br>
> Now I know that cloning groups is supposed to work (it requires that all<br>
> the primitives within the group are themselves cloneable, but you've got<br>
> that covered), but I've never used it myself and can't say for sure that<br>
> it's working as advertised. But it's supposed to, and if it is not,<br>
> please let Andrew know.<br>
<br>
</div>lmb uses it all the time and hasn't been complaining for quite a while.<br>
i'd claim the status is "known to work"<br></blockquote><div><br></div><div>I've seen the group clone work in other clusters I have running, so I would also.</div><div><br></div><div>I was wondering about practical concerns more than technical ones. Like "don't do that because you don't be able to unmount the filesystem without stopping the whole" and such.</div>
<div><br></div><div>Also, Florian's point about DAV locking is well taken here. I'll limit the Apache to one node and use the other for the many, many svnadmin, svndump, svnload tasks the repo admins run.</div><div>
<br></div><div>Thanks again,</div><div>Mike</div><div><br></div><div>--</div><div>Mike Diehn</div></div>Senior Systems Administrator<br>ANSYS, Inc - Lebanon, NH Office<br><a href="mailto:mike.diehn@ansys.com">mike.diehn@ansys.com</a>, (603) 727-5492<br>