Displaying 9 results from an estimated 9 matches for "5f0e".
Did you mean:
5f00
2018 May 21
2
split brain? but where?
...9; from absolute path names
# file: bricks/brick1/gv0
security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x000000010000000000000000ffffffff
trusted.glusterfs.volume-id=0xcfceb3535f0e4cf18b533ccfb1f091d3
glusterp3.graywitch.co.nz:
getfattr: Removing leading '/' from absolute path names
# file: bricks/brick1/gv0
security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000
trusted.gfid=0x00000000000000000000000000000001
trusted.glu...
2018 May 21
0
split brain? but where?
...mes
> # file: bricks/brick1/gv0
>
>security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000
> trusted.gfid=0x00000000000000000000000000000001
> trusted.glusterfs.dht=0x000000010000000000000000ffffffff
> trusted.glusterfs.volume-id=0xcfceb3535f0e4cf18b533ccfb1f091d3
>glusterp3.graywitch.co.nz:
> getfattr: Removing leading '/' from absolute path names
> # file: bricks/brick1/gv0
>
>security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000
> trusted.gfid=0x000000000000000000000000...
2018 May 22
2
split brain? but where?
...k1/gv0
> >
> >security.selinux=0x73797374656d5f753a6f626a6563
> 745f723a756e6c6162656c65645f743a733000
> > trusted.gfid=0x00000000000000000000000000000001
> > trusted.glusterfs.dht=0x000000010000000000000000ffffffff
> > trusted.glusterfs.volume-id=0xcfceb3535f0e4cf18b533ccfb1f091d3
> >glusterp3.graywitch.co.nz:
> > getfattr: Removing leading '/' from absolute path names
> > # file: bricks/brick1/gv0
> >
> >security.selinux=0x73797374656d5f753a6f626a6563
> 745f723a756e6c6162656c65645f743a733000
> > tru...
2018 May 22
0
split brain? but where?
...;> >security.selinux=0x73797374656d5f753a6f626a6563745f723a756e
>> 6c6162656c65645f743a733000
>> > trusted.gfid=0x00000000000000000000000000000001
>> > trusted.glusterfs.dht=0x000000010000000000000000ffffffff
>> > trusted.glusterfs.volume-id=0xcfceb3535f0e4cf18b533ccfb1f091d3
>> >glusterp3.graywitch.co.nz:
>> > getfattr: Removing leading '/' from absolute path names
>> > # file: bricks/brick1/gv0
>> >
>> >security.selinux=0x73797374656d5f753a6f626a6563745f723a756e
>> 6c6162656c65645f743...
2018 May 22
1
split brain? but where?
...ty.selinux=0x73797374656d5f753a6f626a6563745f723a756e
>>> 6c6162656c65645f743a733000
>>> > trusted.gfid=0x00000000000000000000000000000001
>>> > trusted.glusterfs.dht=0x000000010000000000000000ffffffff
>>> > trusted.glusterfs.volume-id=0xcfceb3535f0e4cf18b533ccfb1f091d3
>>> >glusterp3.graywitch.co.nz:
>>> > getfattr: Removing leading '/' from absolute path names
>>> > # file: bricks/brick1/gv0
>>> >
>>> >security.selinux=0x73797374656d5f753a6f626a6563745f723a756e
>>...
2018 May 10
0
broken gluster config
...leading '/' from absolute path names
# file: bricks/brick1/gv0
security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000
trusted.gfid=0x00000000000000000000000000000001
trusted.glusterfs.dht=0x000000010000000000000000ffffffff
trusted.glusterfs.volume-id=0xcfceb3535f0e4cf18b533ccfb1f091d3
[root at glusterp1 gv0]# gluster volume info vol
Volume vol does not exist
[root at glusterp1 gv0]# gluster volume info gv0
Volume Name: gv0
Type: Replicate
Volume ID: cfceb353-5f0e-4cf1-8b53-3ccfb1f091d3
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-...
2018 May 10
2
broken gluster config
Whatever repair happened has now finished but I still have this,
I cant find anything so far telling me how to fix it. Looking at
http://staged-gluster-docs.readthedocs.io/en/release3.7.0beta1/Features/heal-info-and-split-brain-resolution/
I cant determine what file? dir gvo? is actually the issue.
[root at glusterp1 gv0]# gluster volume heal gv0 info split-brain
Brick
2010 Jan 28
15
2.6.31.6 pv_ops can''t boot pv_ops DomU kernel
Hello,
i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops.
Dom0 seams to work fine.
But i can only boot "old" domU kernel.
A pv_ops Kernel hangs after initrd.
Regards,
Stefan Kuhne
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
2010 Jan 28
15
2.6.31.6 pv_ops can''t boot pv_ops DomU kernel
Hello,
i''ve a xen-4.0.0-rc1 with 2.6.31.6 pv_ops.
Dom0 seams to work fine.
But i can only boot "old" domU kernel.
A pv_ops Kernel hangs after initrd.
Regards,
Stefan Kuhne
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel