Displaying 5 results from an estimated 5 matches for "nuvini".
Did you mean:
nutini
2018 Apr 16
0
Gluster FUSE mount sometimes reports that files do not exist until ls is performed on parent directory
On Mon, Apr 16, 2018 at 1:54 PM, Niels Hendriks <niels at nuvini.com> wrote:
> Hi,
>
> We have a 3-node gluster setup where gluster is both the server and the
> client.
> Every few days we have some $random file or directory that does not exist
> according to the FUSE mountpoint. When we try to access the file (stat,
> cat, etc...) the f...
2018 Apr 16
1
Gluster FUSE mount sometimes reports that files do not exist until ls is performed on parent directory
On 16 April 2018 at 14:07, Raghavendra Gowdappa <rgowdapp at redhat.com> wrote:
>
>
> On Mon, Apr 16, 2018 at 1:54 PM, Niels Hendriks <niels at nuvini.com> wrote:
>
>> Hi,
>>
>> We have a 3-node gluster setup where gluster is both the server and the
>> client.
>> Every few days we have some $random file or directory that does not exist
>> according to the FUSE mountpoint. When we try to access the file (s...
2018 Apr 16
2
Gluster FUSE mount sometimes reports that files do not exist until ls is performed on parent directory
Hi,
We have a 3-node gluster setup where gluster is both the server and the
client.
Every few days we have some $random file or directory that does not exist
according to the FUSE mountpoint. When we try to access the file (stat,
cat, etc...) the filesystem reports that the file/directory does not exist,
even though it does. When we try to create the file/directory we receive
the following error
2017 Nov 24
0
Changing performance.parallel-readdir to on causes CPU soft lockup and very high load all glusterd nodes
...o update this thread. We updated from Gluster 3.12.2 to 3.12.3 which
resolved the issue it seems. I checked the changelog but don't see anything
that looks like this issue, but I'm glad it seems like it's OK now.
Niels Hendriks
On 14 November 2017 at 09:42, Niels Hendriks <niels at nuvini.com> wrote:
> Hi,
>
> We're using a 3-node setup where GlusterFS is running as both a client and
> a server with a fuse mount-point.
>
> We tried to change the performance.parallel-readdir setting to on for a
> volume, but after that the load on all 3 nodes skyrocketed...
2017 Nov 14
3
Changing performance.parallel-readdir to on causes CPU soft lockup and very high load all glusterd nodes
Hi,
We're using a 3-node setup where GlusterFS is running as both a client and
a server with a fuse mount-point.
We tried to change the performance.parallel-readdir setting to on for a
volume, but after that the load on all 3 nodes skyrocketed due to the
glusterd process and we saw CPU soft lockup errors in the console.
I had to completely bring down/reboot all 3 nodes and disable the