Hi Soumya Koduri and all,
To start with, could you please check the logs
'/var/log/glusterfs/nfs.log' and brick logs for any errors/warnings.
Thanks,
Soumya
As that cluster is needed quickly I decided to stop the use of NFS for
the local mount of the volume. I delete the volume, reformat
I am triying to attach a brick from another server to a local gluster
development server. Therfore I have done a dd from a snapshot on production
and a dd on the lvm volume on development. Then I deleted the .glusterfs
folder on root.
Unfortunatelly forming a new brick failed nevertheless with
On Tue, 2015-11-10 at 10:18 +0100, Niels de Vos wrote:
> Please speak up and let us know what versions you depend on for next few
> months. You can reply to this email to the list (note that it is
> x-posted, one mailinglist is sufficient for your reply), directly to me
> or over IRC in
On 11/20/2015 01:30 AM, Merlin Morgenstern wrote:
> I am triying to attach a brick from another server to a local gluster
> development server. Therfore I have done a dd from a snapshot on
> production and a dd on the lvm volume on development. Then I deleted the
> .glusterfs folder on root.
>
I’ve got 3.6 & 3.7 systems on Cent 7, migrating into 3.7 for everything these
days…
> On Nov 19, 2015, at 7:57 PM, Kingsley wrote:
>
> On Tue, 2015-11-10 at 10:18 +0100, Niels de Vos wrote:
>> Please speak up and let us know what versions you depend on for next
On 19/11/15 14:49, Krutika Dhananjay wrote:
I wanted to ask you one more thing: specifically in VM workload with
sharding, do you run into consistency issues with
strict-write-ordering being off?
I remember suggesting that this option be enabled. But that was for
plain dd on the mountpoint
On 20/11/15 15:15, Lindsay Mathieson wrote:
One caveat - I started testing with 3.7.5, then upgraded to 3.7.6, but
didn't upgrade the op-version (always forget that).
Once I set the op version to 3.7.6 sharded volumes started reporting
correct file sizes (for new files) even with