I've been using these for a few weeks now without any issues, thank you!
-Original Message-
From: gluster-users-boun...@gluster.org On
Behalf Of Matt Waymack
Sent: Thursday, December 27, 2018 10:56 AM
To: Diego Remolina
Cc: gluster-users@gluster.org List
Subject: Re: [Gluster-users
Has anyone any other ideas where to look? This is only affecting FUSE clients.
SMB clients are unaffected by this problem.
Thanks!
From: gluster-users-boun...@gluster.org On
Behalf Of Matt Waymack
Sent: Monday, January 7, 2019 1:19 PM
To: Raghavendra Gowdappa
Cc: gluster-users@gluster.org
Yep, first unmount/remounted, then rebooted clients. Stopped/started the
volumes, and rebooted all nodes.
From: Davide Obbi
Sent: Monday, January 7, 2019 12:47 PM
To: Matt Waymack
Cc: Raghavendra Gowdappa ; gluster-users@gluster.org List
Subject: Re: [External] Re: [Gluster-users] Input
Yes, all volumes use sharding.
From: Davide Obbi
Sent: Monday, January 7, 2019 12:43 PM
To: Matt Waymack
Cc: Raghavendra Gowdappa ; gluster-users@gluster.org List
Subject: Re: [External] Re: [Gluster-users] Input/output error on FUSE log
are all the volumes being configured with sharding
: Sunday, January 6, 2019 12:26 PM
To: Raghavendra Gowdappa
Cc: Matt Waymack ; gluster-users@gluster.org List
Subject: Re: [External] Re: [Gluster-users] Input/output error on FUSE log
Hi,
i would start doing some checks like: "(Input/output error)" seems returned by
the operat
Hi all,
I'm having a problem writing to our volume. When writing files larger than
about 2GB, I get an intermittent issue where the write will fail and return
Input/Output error. This is also shown in the FUSE log of the client (this is
affecting all clients). A snip of a client log is
updated with stability.
Thank you!
-Original Message-
From: Diego Remolina
Sent: Thursday, December 20, 2018 1:36 PM
To: Matt Waymack
Cc: gluster-users@gluster.org List
Subject: Re: [Gluster-users] Unable to create new files or folders using samba
and vfs_glusterfs
Hi Matt,
The update
Hi all,
I'm looking to update Samba from fasttrack, but I only still se 4.8.3 and yum
is not wanting to update. The test build is also showing 4.8.3.
Thank you!
From: gluster-users-boun...@gluster.org On
Behalf Of Matt Waymack
Sent: Sunday, December 16, 2018 1:55 PM
To: Diego Remolina
Cc
Diego
On Fri, Dec 14, 2018 at 12:52 AM Anoop C S
mailto:anoo...@cryptolab.net>> wrote:
>
> On Thu, 2018-12-13 at 15:31 +, Matt Waymack wrote:
> > Hi all,
> >
> > I'm having an issue on Windows clients accessing shares via smb when
> > using vfs_glusterfs. The
Hi all,
I'm having an issue on Windows clients accessing shares via smb when using
vfs_glusterfs. They are unable to create any file or folders at the root of
the share and get the error "The file is too large for the destination file
system." When I change from vfs_glusterfs to just using a
Mine also has a list of files that seemingly never heal. They are usually
isolated on my arbiter bricks, but not always. I would also like to find an
answer for this behavior.
-Original Message-
From: gluster-users-boun...@gluster.org
[mailto:gluster-users-boun...@gluster.org] On
Waymack <mwaym...@nsgdv.com>
Cc: gluster-users <Gluster-users@gluster.org>
Subject: Re: [Gluster-users] Production Volume will not start
On Sat, Dec 16, 2017 at 12:45 AM, Matt Waymack
<mwaym...@nsgdv.com<mailto:mwaym...@nsgdv.com>> wrote:
Hi all,
I have a
Hi all,
I have an issue where our volume will not start from any node. When attempting
to start the volume it will eventually return:
Error: Request timed out
For some time after that, the volume is locked and we either have to wait or
restart Gluster services. In the gluserd.log, it shows
In my case I was able to delete the hard links in the .glusterfs folders of the
bricks and it seems to have done the trick, thanks!
From: Karthik Subrahmanya [mailto:ksubr...@redhat.com]
Sent: Monday, October 23, 2017 1:52 AM
To: Jim Kinney <jim.kin...@gmail.com>; Matt Waymack
are
orphaned.
From: Karthik Subrahmanya [mailto:ksubr...@redhat.com]
Sent: Wednesday, October 18, 2017 4:34 AM
To: Matt Waymack <mwaym...@nsgdv.com>
Cc: gluster-users <Gluster-users@gluster.org>
Subject: Re: [Gluster-users] gfid entries in volume heal info that do not heal
He
ies in split-brain: 0
-Matt
From: Karthik Subrahmanya [mailto:ksubr...@redhat.com]
Sent: Tuesday, October 17, 2017 1:26 AM
To: Matt Waymack <mwaym...@nsgdv.com>
Cc: gluster-users <Gluster-users@gluster.org>
Subject: Re: [Gluster-users] gfid entries in volume heal info that do not h
: Monday, October 16, 2017 10:27 AM
To: Matt Waymack <mwaym...@nsgdv.com>
Cc: gluster-users <Gluster-users@gluster.org>
Subject: Re: [Gluster-users] gfid entries in volume heal info that do not heal
Hi Matt,
The files might be in split brain. Could you please send the outputs of these?
gl
Hi all,
I have a volume where the output of volume heal info shows several gfid entries
to be healed, but they've been there for weeks and have not healed. Any normal
file that shows up on the heal info does get healed as expected, but these gfid
entries do not. Is there any way to remove
18 matches
Mail list logo
