<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;">>At Thu, 17 Mar 2011 13:49:34 -0700 (PDT),<br>>Ski Mountain wrote:<br>>> <br>>> Thanks for the reply.<br>>> <br>>> While setting up RAID 0 would be a option, there must be more elegant solutions <br>>> out there. Just because one disk out of the whole array dies breaking the whole <br>>> array and drastically changing the size of the sheepdog cluster. <br>><br>>Agreed.<br>><br>>> <br>>> One problem I do see with starting many sheep daemons on the same server that <br>>> has many disks is that (especially on small clusters) it is possible for all <br>>> data
for one or many Virtual Machine to be stored on one physical server. <br>><br>>Could you explain more details about this? Fixing this looks the<br>>right way to go to me.<br><br>Since as far as I understand the ring architecture, each machine sits on a ring and VM's are RAIDed across the ring. <br><br>Having a sheep on a server that has many disks (these days it is very easy to have 10+ disks on one server) , and the best way to set up a machine with many disks is to assign a sheep daemon to each disk. I am simply saying it would be good if there where some additional sanity checks put into the sheepdog architecture so that it is not possible for a VM to be stored entirely on one server with many disks. I know this would be the exception, not the rule, but would just like all bases to be covered.<br><br>Or is that already listed under the to do as "better data re-balancing"<br><br>><br>>> Would it be
possible to do say<br>>> sheep /store_disk0 /store_disk1 /store_disk2 /store_disk3 /store_disk4 <br>>> /store_disk5 /store_disk6<br>>> So all mount points on a server would be handled by the same sheep using <br>>> multiple threads<br>>> <br>>> Add a mount point <br>>> sheep -a /store_disk7<br>>> <br>>> Remove a mount point<br>>> sheep -r /store_disk7<br>><br>>It is possible to support multiple disks. But if running multiple<br>>daemons solves the problem, I'd like to keep the current simple design<br>>(one daemon for one disk).+<br><br>Would it be possible to run one sheep daemon per a server, but spawn a child process for each disk. Then use the above method for adding and removing disks for the machine so that the administrator does not have to keep track of port
numbers?<br><br>><br>><br>>Thanks,<br>><br>>Kazutaka<br><br>-Thanks<br></div></div>
</div><br>
</body></html>