02.10.2018 12:59, Amar Tumballi пишет:
Recently, in one of the situation, we found
that locks were not freed up due to not getting TCP
timeout..
Can you try the option like below and let us know?
`gluster volume set $volname tcp-user-timeout 42`
Thank you, we'll try this.
On Tue, Oct 2, 2018 at 10:40 AM Dmitry Melekhov
< dm@xxxxxxxxxx> wrote:
01.10.2018
23:09, Danny Lee пишет:
Ran into this issue too with 4.1.5 with an
arbiter setup. Also could not run a statedump due to
"Segmentation fault".
Tried with 3.12.13 and had issues with
locked files as well. We were able to do a statedump
and found that some of our files were "BLOCKED"
(xlator.features.locks.vol-locks.inode). Attached
part of statedump.
Also tried clearing the locks using
clear-locks, which did remove the lock, but as soon as
I tried to cat the file, it got locked again and the
cat process hung.
I created issue in bugzilla, can't find it though :-(
Looks like there is no activity after I sent all logs...
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
--
|
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-devel