Displaying 4 results from an estimated 4 matches for "ctfngluster".
2017 Oct 27
3
ctdb vacuum timeouts and record locks
...is on the SSD
with the OS. running mount from within the container shows:
/dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
However, the gluster native client is a fuse-based system, so the data
is stored on a fuse system which is mounted in the container:
masterchieflian:ctfngluster on /CTFN type fuse.glusterfs
(rw,relatime,user_id=0,group_id=0,allow_other,max_read=131072)
Since this is where the files that become inaccessible are, perhaps this
is really where the problem is, and not with the locking.tdb file? I
will investigate about file locks on the gluster system......
2017 Nov 02
0
ctdb vacuum timeouts and record locks
...ng mount from within the container shows:
>
> /dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
>
> However, the gluster native client is a fuse-based system, so the data
> is stored on a fuse system which is mounted in the container:
>
> masterchieflian:ctfngluster on /CTFN type fuse.glusterfs
> (rw,relatime,user_id=0,group_id=0,allow_other,max_read=131072)
>
> Since this is where the files that become inaccessible are, perhaps this
> is really where the problem is, and not with the locking.tdb file? I
> will investigate about file locks o...
2017 Nov 02
2
ctdb vacuum timeouts and record locks
...container shows:
>>
>> /dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered)
>>
>> However, the gluster native client is a fuse-based system, so the data
>> is stored on a fuse system which is mounted in the container:
>>
>> masterchieflian:ctfngluster on /CTFN type fuse.glusterfs
>> (rw,relatime,user_id=0,group_id=0,allow_other,max_read=131072)
>>
>> Since this is where the files that become inaccessible are, perhaps
>> this is really where the problem is, and not with the locking.tdb
>> file? I will investigate...
2017 Oct 27
2
ctdb vacuum timeouts and record locks
Hi List,
I set up a ctdb cluster a couple months back. Things seemed pretty
solid for the first 2-3 weeks, but then I started getting reports of
people not being able to access files, or some times directories. It
has taken me a while to figure some stuff out, but it seems the common
denominator to this happening is vacuuming timeouts for locking.tdb in
the ctdb log, which might go on