Hi all,
When I checked my glusterfs configuration, the default value of
performance.cache-max-file-size is 0. Please find the following
command that I have run.
$ sudo gluster volume set help
Option: performance.cache-max-file-size
Default Value: 0
Description: Maximum file size which would be
Hi,
Currently there are two suggested options for the syntax of add/remove brick:
1) gluster v tier add-brick [replica ] [tier-type ]
...
this syntax shows that its a add-brick operation on a tiered volume through a
argument
instead of distinguishing using the command. The separation of
Hi Gluster Team,
We saw a bunch of intermittent EBADF errors on clients, We saw these
errors immediately after an add-brick operation followed by a self-heal of
that volume. We are wondering if these errors might close file descriptors
prematurely. causing problems on files we had
Hi Gluster team & users,
We are seeing multiple instances of the following error: "remote operation
failed [No such file or directory]" on our gluster clients, and this has
affects cases where we have some files hosted and are opened/memory-mapped
We are seeing this error after we recently added
> On 21 Oct 2016, at 19.52,
> wrote:
>
> Will that work for samba mounts? (cifs)
Just based on a Google search, I’d say yes.
https://wiki.archlinux.org/index.php/samba#As_mount_entry
We use the FUSE mounts and with those it works
Will that work for samba mounts? (cifs)
Sent from my Windows 10 phone
From: Ville-Pekka Vainio
Sent: Saturday, 22 October 2016 2:26
To: gluster-users@gluster.org
Subject: Re: [Gluster-users] gluster volume not mounted on boot
Hi all,
On a system using systemd, you should also be able to use
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users
Hi all,
On a system using systemd, you should also be able to use x-systemd.automount.
Just add 'noauto,x-systemd.automount’ to your fstab line and systemd should
mount the gluster volume for you when it’s accessed.
The ‘noauto’ option means that autofs won’t touch the mount and systemd will
On 21/10/2016 12:39 PM, Lindsay Mathieson wrote:
And now I have it all setup for logging etc I can't reproduce the error:(
Ah, figured out what I was doing different - started the heavy I/O
before the add bricks and rebalance which reliably triggers a "volume
rebalance: teststore1: failed:
Hi,
As we were discussing in the "gluster volume not mounted on boot" you
should probably just go with AutoFS, not ideal but I don't see any
other reliable solutions.
On Fri, Oct 21, 2016 at 02:46:05PM +0200, Paul Boven wrote:
> Hi everyone,
>
> For the past few days I've been experimenting
Hi everyone,
For the past few days I've been experimenting with Gluster and systemd.
The issue I'm trying to solve is that my gluster servers always fail to
self-mount their gluster volume locally on boot. Apparently this is
because the mount happens right after glusterd has been started, but
On Fri, Oct 21, 2016 at 12:14:15PM +0200, Josep Manel Andrés wrote:
> Hi again,
> I have two servers SLES 12 SP 0 with
>
> Information for package glusterfs:
> --
> Repository: GlusterFS
> Name: glusterfs
> Version: 3.7.11-101.1
> Arch: x86_64
> Vendor:
Hi again,
I have two servers SLES 12 SP 0 with
Information for package glusterfs:
--
Repository: GlusterFS
Name: glusterfs
Version: 3.7.11-101.1
Arch: x86_64
Vendor: obs://build.opensuse.org/home:kkeithleatredhat
and now I decided to upgrade one server to SP1
> But I have a question, it is possible to mount a volume at /gluster-data
> for example???
>
No, the way AutoFS works it needs a directory just for itself, so you can't do
that.
I think the simplest would be to use /mnt/autofs like us, and then do a
symbolic link :
ln -s
Hi Kevin,
Thank you for your help, I manage to set it up!
But I have a question, it is possible to mount a volume at /gluster-data
for example???
I cannot do:
opsld04:~ # cat /etc/auto.master
#
# Sample auto.master file
# This is a 'master' automounter map and it has the following format:
Hi Atin,
the node with the UUID=bb12d7e7-ded5-4d32-b294-8f5011f70afb is one of
the nodes I sent the logs
root@chglbcvtprd04:~# cat /var/lib/glusterd/glusterd.info
UUID=bb12d7e7-ded5-4d32-b294-8f5011f70afb
operating-version=30703
below the info you requested, but I don't know how relevant it is as
On Thu, Oct 20, 2016 at 8:09 PM, Amye Scavarda wrote:
>
>
> On Thu, Oct 20, 2016 at 7:06 AM, Kaushal M wrote:
>>
>> Hi All,
>>
>> Our weekly community meetings have become mainly one hour of status
>> updates. This just drains the life out of the meeting,
On Thu, Oct 20, 2016 at 7:06 AM, Kaushal M wrote:
> Hi All,
>
> Our weekly community meetings have become mainly one hour of status
> updates. This just drains the life out of the meeting, and doesn't
> encourage new attendees to speak up.
>
> Let's try and change this. For
18 matches
Mail list logo