search for: a52055bd

...e we thought that it was causing issues. However now I think that this was unnecessary. After the crash arbiter logs had lots of messages like this: [2018-01-20 10:19:36.515717] I [MSGID: 115072] [server-rpc-fops.c:1640:server_setattr_cbk] 0-zone2-ssd1-vmstor1-server: 37374187: SETATTR <gfid:a52055bd-e2e9-42dd-92a3-e96b693bcafe> (a52055bd-e2e9-42dd-92a3-e96b693bcafe) ==> (Operation not permitted) [Operation not permitted] Is there anyways to force self heal to stop? Any help would be very much appreciated :) Best regards, Samuli Heinonen > Samuli Heinonen <mailto:samppah a...

...; the crash arbiter logs had lots of messages like this: >> [2018-01-20 10:19:36.515717] I [MSGID: 115072] >> [server-rpc-fops.c:1640:server_setattr_cbk] >> 0-zone2-ssd1-vmstor1-server: 37374187: SETATTR >> <gfid:a52055bd-e2e9-42dd-92a3-e96b693bcafe> >> (a52055bd-e2e9-42dd-92a3-e96b693bcafe) ==> (Operation not >> permitted) >> [Operation not permitted] >> >> Is there anyways to force self heal to stop? Any help >> w...

...that this was unnecessary. After >>> the crash arbiter logs had lots of messages like this: >>> [2018-01-20 10:19:36.515717] I [MSGID: 115072] >>> [server-rpc-fops.c:1640:server_setattr_cbk] >>> 0-zone2-ssd1-vmstor1-server: 37374187: SETATTR >>> <gfid:a52055bd-e2e9-42dd-92a3-e96b693bcafe> >>> (a52055bd-e2e9-42dd-92a3-e96b693bcafe) ==> (Operation not permitted) >>> [Operation not permitted] >>> >>> Is there anyways to force self heal to stop? Any help would be very >>> much appreciated :) >>> &gt...

...was causing issues. > However now I think that this was unnecessary. After the crash arbiter logs > had lots of messages like this: > [2018-01-20 10:19:36.515717] I [MSGID: 115072] [server-rpc-fops.c:1640:server_setattr_cbk] > 0-zone2-ssd1-vmstor1-server: 37374187: SETATTR > <gfid:a52055bd-e2e9-42dd-92a3-e96b693bcafe> (a52055bd-e2e9-42dd-92a3-e96b693bcafe) > ==> (Operation not permitted) [Operation not permitted] > > Is there anyways to force self heal to stop? Any help would be very much > appreciated :) > Exposing .shard to a normal mount is opening a can of w...

...ssary. After > the crash arbiter logs had lots of messages like this: > [2018-01-20 10:19:36.515717] I [MSGID: 115072] > [server-rpc-fops.c:1640:server_setattr_cbk] > 0-zone2-ssd1-vmstor1-server: 37374187: SETATTR > <gfid:a52055bd-e2e9-42dd-92a3-e96b693bcafe> > (a52055bd-e2e9-42dd-92a3-e96b693bcafe) ==> (Operation not > permitted) > [Operation not permitted] > > Is there anyways to force self heal to stop? Any help > would be very >...

Hi all! One hypervisor on our virtualization environment crashed and now some of the VM images cannot be accessed. After investigation we found out that there was lots of images that still had active lock on crashed hypervisor. We were able to remove locks from "regular files", but it doesn't seem possible to remove locks from shards. We are running GlusterFS 3.8.15 on all

...>>> unnecessary. After >>> the crash arbiter logs had lots of messages like this: >>> [2018-01-20 10:19:36.515717] I [MSGID: 115072] >>> [server-rpc-fops.c:1640:server_setattr_cbk] >>> 0-zone2-ssd1-vmstor1-server: 37374187: SETATTR >>> <gfid:a52055bd-e2e9-42dd-92a3-e96b693bcafe> >>> (a52055bd-e2e9-42dd-92a3-e96b693bcafe) ==> (Operation >>> not >>> permitted) >>> [Operation not permitted] >>> >>> Is there anyways to force self heal to stop? Any help >>> would be very >>&...

...ssary. After >>>> the crash arbiter logs had lots of messages like this: >>>> [2018-01-20 10:19:36.515717] I [MSGID: 115072] >>>> [server-rpc-fops.c:1640:server_setattr_cbk] >>>> 0-zone2-ssd1-vmstor1-server: 37374187: SETATTR >>>> <gfid:a52055bd-e2e9-42dd-92a3-e96b693bcafe> >>>> (a52055bd-e2e9-42dd-92a3-e96b693bcafe) ==> (Operation >>>> not >>>> permitted) >>>> [Operation not permitted] >>>> >>>> Is there anyways to force self heal to stop? Any help >>>&...

...;>>> the crash arbiter logs had lots of messages like this: >>>>> [2018-01-20 10:19:36.515717] I [MSGID: 115072] >>>>> [server-rpc-fops.c:1640:server_setattr_cbk] >>>>> 0-zone2-ssd1-vmstor1-server: 37374187: SETATTR >>>>> <gfid:a52055bd-e2e9-42dd-92a3-e96b693bcafe> >>>>> (a52055bd-e2e9-42dd-92a3-e96b693bcafe) ==> (Operation >>>>> not >>>>> permitted) >>>>> [Operation not permitted] >>>>> >>>>> Is there anyways to force self heal to stop...

...e crash arbiter logs had lots of messages like this: > [2018-01-20 10:19:36.515717] I [MSGID: 115072] > [server-rpc-fops.c:1640:server_setattr_cbk] > 0-zone2-ssd1-vmstor1-server: 37374187: SETATTR > <gfid:a52055bd-e2e9-42dd-92a3-e96b693bcafe> > (a52055bd-e2e9-42dd-92a3-e96b693bcafe) ==> (Operation > not > permitted) > [Operation not permitted] > > Is there anyways to force self heal to...

...However now I think that this was unnecessary. After >> the crash arbiter logs had lots of messages like this: >> [2018-01-20 10:19:36.515717] I [MSGID: 115072] >> [server-rpc-fops.c:1640:server_setattr_cbk] >> 0-zone2-ssd1-vmstor1-server: 37374187: SETATTR >> <gfid:a52055bd-e2e9-42dd-92a3-e96b693bcafe> >> (a52055bd-e2e9-42dd-92a3-e96b693bcafe) ==> (Operation not permitted) >> [Operation not permitted] >> >> Is there anyways to force self heal to stop? Any help would be very >> much appreciated :) > > Exposing .shard to a nor...

...unnecessary. After >>> the crash arbiter logs had lots of messages >>> like this: >>> [2018-01-20 10:19:36.515717] I [MSGID: 115072] >>> [server-rpc-fops.c:1640:server_setattr_cbk] >>> 0-zone2-ssd1-vmstor1-server: 37374187: SETATTR >>> <gfid:a52055bd-e2e9-42dd-92a3-e96b693bcafe> >>> (a52055bd-e2e9-42dd-92a3-e96b693bcafe) ==> >>> (Operation >>> not >>> permitted) >>> [Operation not permitted] >>> >>> Is there anyways to force self heal to stop? >>> Any help >>&g...