search for: 92a3

...t 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 at neutraali.net...

...rash 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 &g...

...essary. 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 :) >>> >> >>...

...> 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 worms. You shoul...

...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 appr...

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

...essary. 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 apprec...

...t;>> 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 ve...

...rash 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 >...

...s 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...

...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 op...

...>>> 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 ver...

All, I understand that ZFS gives you more error correction when using two LUNS from a SAN. But, does it provide you with less features than UFS does on one LUN from a SAN (i.e is it less stable). Thanks, Shawn This message posted from opensolaris.org