search for: d6b8

...from "regular files", but it doesn't seem possible to remove locks from shards. We are running GlusterFS 3.8.15 on all nodes. Here is part of statedump that shows shard having active lock on crashed node: [xlator.features.locks.zone2-ssd1-vmstor1-locks.inode] path=/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21 mandatory=0 inodelk-count=1 lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:metadata lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:self-heal lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0 inodelk.inodelk[0](ACTIVE)=type=WRITE, whence=0, start=0, len...

...> doesn't seem possible to remove locks from shards. > > We are running GlusterFS 3.8.15 on all nodes. > > Here is part of statedump that shows shard having active lock on > crashed node: > [xlator.features.locks.zone2-ssd1-vmstor1-locks.inode] > path=/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21 > mandatory=0 > inodelk-count=1 > lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:metadata > lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:self-heal > lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0 > inodelk.inodelk[0](ACTIVE)=type...

...ll nodes. >> >> Here is part of statedump that shows shard having >> active lock on >> crashed node: >> [xlator.features.locks.zone2-ssd1-vmstor1-locks.inode] >> path=/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21 >> mandatory=0 >> inodelk-count=1 >> lock-dump.domain.domain=zone2- >> ssd1-vmstor1-replicate-0:metadata >> lock-dump.domain.domain=zone2- >> ssd1-vmstor1-replicate-0:self-h...

...>>> We are running GlusterFS 3.8.15 on all nodes. >>>> >>>> Here is part of statedump that shows shard having active lock on >>>> crashed node: >>>> [xlator.features.locks.zone2-ssd1-vmstor1-locks.inode] >>>> path=/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21 >>>> mandatory=0 >>>> inodelk-count=1 >>>> lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:metadata >>>> lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:self-heal >>>> lock-dump.domain.domain=zone2-s...

...it doesn't seem > possible to remove locks from shards. > > We are running GlusterFS 3.8.15 on all nodes. > > Here is part of statedump that shows shard having active lock on crashed > node: > [xlator.features.locks.zone2-ssd1-vmstor1-locks.inode] > path=/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21 > mandatory=0 > inodelk-count=1 > lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:metadata > lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:self-heal > lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0 > inodelk.inodelk[0](ACTIVE)=type...

...ng GlusterFS 3.8.15 on all nodes. > > Here is part of statedump that shows shard having > active lock on > crashed node: > [xlator.features.locks.zone2-ssd1-vmstor1-locks.inode] > path=/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21 > mandatory=0 > inodelk-count=1 > lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:metadata > lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:self-heal > lock-dump.d...

...nning GlusterFS 3.8.15 on all nodes. >>> >>> Here is part of statedump that shows shard having >>> active lock on >>> crashed node: >>> >>> [xlator.features.locks.zone2-ssd1-vmstor1-locks.inode] >>> >>> path=/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21 >>> mandatory=0 >>> inodelk-count=1 >>> >>> lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:metadata >>> >>> lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:self-heal >>> >>> lock-dump...

...nodes. >>>> >>>> Here is part of statedump that shows shard having >>>> active lock on >>>> crashed node: >>>> >>>> [xlator.features.locks.zone2-ssd1-vmstor1-locks.inode] >>>> >>>> path=/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21 >>>> mandatory=0 >>>> inodelk-count=1 >>>> >>>> lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:metadata >>>> >>>> lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:self-heal >>>&g...

...;>>>> Here is part of statedump that shows shard having >>>>> active lock on >>>>> crashed node: >>>>> >>>>> [xlator.features.locks.zone2-ssd1-vmstor1-locks.inode] >>>>> >>>>> path=/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21 >>>>> mandatory=0 >>>>> inodelk-count=1 >>>>> >>>>> lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:metadata >>>>> >>>>> lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:...

...es. > > Here is part of statedump that shows shard having > active lock on > crashed node: > > [xlator.features.locks.zone2-ssd1-vmstor1-locks.inode] > > path=/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21 > mandatory=0 > inodelk-count=1 > > lock-dump.domain.domain=zone2- > ssd1-vmstor1-replicate-0:metadata > > lock-dump.domain.domain=zone2- > ssd1-vmstor1-replicate-0:self...

...rds. >>> >>> We are running GlusterFS 3.8.15 on all nodes. >>> >>> Here is part of statedump that shows shard having active lock on >>> crashed node: >>> [xlator.features.locks.zone2-ssd1-vmstor1-locks.inode] >>> path=/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21 >>> mandatory=0 >>> inodelk-count=1 >>> lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:metadata >>> lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:self-heal >>> lock-dump.domain.domain=zone2-ssd1-vmstor1-replicat...

...>> >>> Here is part of statedump that shows shard >>> having >>> active lock on >>> crashed node: >>> >>> >>> [xlator.features.locks.zone2-ssd1-vmstor1-locks.inode] >>> >>> >>> path=/.shard/75353c17-d6b8-485d-9baf-fd6c700e39a1.21 >>> mandatory=0 >>> inodelk-count=1 >>> >>> >>> lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:metadata >>> >>> >>> lock-dump.domain.domain=zone2-ssd1-vmstor1-replicate-0:self-heal >>...

Anybody know the proceedure to factory reset the a 7960 phone running 6.3 SIP software? I've tried holding # when booting the phone and nothing, i can do that on my 8.2 phone but this phone i just got with 6.3 isnt working. Also **# doesnt work either.. -- ~Shaun