Paul,
Thanks for the response.
You mention that the issue is orphaned files during updates when one node
is down. However I am less concerned about adding and removing files
because the file server will be predominately VM disks so the file
structure is fairly static. Those VM files will be
On 08/29/2014 07:34 PM, David King wrote:
Paul,
Thanks for the response.
You mention that the issue is orphaned files during updates when one
node is down. However I am less concerned about adding and removing
files because the file server will be predominately VM disks so the file
structure
On Fri, Aug 29, 2014 at 12:25 PM, Vijay Bellur vbel...@redhat.com wrote:
On 08/29/2014 07:34 PM, David King wrote:
Paul,
Thanks for the response.
You mention that the issue is orphaned files during updates when one
node is down. However I am less concerned about adding and removing
files
Hi Paul,
I would prefer to do a direct mount for local disk. However I am not certain
how to configure a single system with both local storage and bluster replicated
storage.
- The “Configure Local Storage” option for Hosts wants to make a datacenter
and cluster for the system. I presume
Hi,
I am currently testing oVirt 3.4.3 + gluster 3.5.2 for use in my relatively
small home office environment on a single host. I have 2 Intel hosts with
SSD and magnetic disk and one AMD host with only magnetic disk. I have
been trying to figure out the best way to configure my environment
I'll try to answer some of these.1) its not a serious problem persay the issue is if one node goes down and you delete a file while the second node is down it will be restored when the second node comes back which may cause orphaned files where as if you use 3 servers they will use quorum to
6 matches
Mail list logo
