search for: nod1

...Rtmpk1XxTl/downloaded_packages’ Updating HTML index of packages in '.Library' Warning message: In install.packages("cairoDevice", dep = T) : installation of package 'cairoDevice' had non-zero exit status When I connect with remote computer using ssh -X root at nod1 to enable X11 forwarding then installation works without problems. This would however require manually connect with each administred computer a do the installation. cssh which I use now to install packages on multiple computers does not enable X11 forwarding. I have also tested installation using R...

...e files which need to be healing using the "heal <volume> info" command and it still shows that very same GFID on node2 to be healed. So nothing changed here. The file /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 is only on node2 and not on my nod1 nor on my arbiternode. This file seems to be a regular file and not a symlink. Here is the output of the stat command on it from my node2: File: ?/data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397? Size: 0 Blocks: 1 IO Block: 512 regular empty file Device: 25h/37d...

...sing the "heal <volume> > info" command and it still shows that very same GFID on node2 to be > healed. So nothing changed here. > > The file > /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 > is only on node2 and not on my nod1 nor on my arbiternode. This file > seems to be a regular file and not a symlink. Here is the output of > the stat command on it from my node2: > > File: > ?/data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397? > Size: 0 Blocks: 1...

Hi, I'm building a cluster containing two nodes with seperate common storage server. On storage server i have volume with ocfs2 fs which is sharing this volume via iscsi target. When node connected to the target i can local mount volume on node and using it. Unfortunately. on storage server ocfs2 logged to dmesg: Oct 19 22:21:02 storage kernel: [ 1510.424144]

...hich need to be healing using the "heal <volume> info" command and it still shows that very same GFID on node2 to be healed. So nothing changed here. >> The file /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 is only on node2 and not on my nod1 nor on my arbiternode. This file seems to be a regular file and not a symlink. Here is the output of the stat command on it from my node2: >> File: ?/data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397? >> Size: 0 Blocks: 1 IO Block: 512 regular empty fil...

...info" command and it still shows that very same GFID >>> on node2 to be healed. So nothing changed here. >>> >>> The file >>> /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 >>> is only on node2 and not on my nod1 nor on my arbiternode. This file >>> seems to be a regular file and not a symlink. Here is the output of >>> the stat command on it from my node2: >>> >>> File: >>> ?/data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c39...

...d to be healing using the "heal <volume> info" command and it still shows that very same GFID on node2 to be healed. So nothing changed here. >>>> The file /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 is only on node2 and not on my nod1 nor on my arbiternode. This file seems to be a regular file and not a symlink. Here is the output of the stat command on it from my node2: >>>> File: ?/data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397? >>>> Size: 0 Blocks: 1 IO Block: 512 r...

...hat very same >>>>> GFID on node2 to be healed. So nothing changed here. >>>>> >>>>> The file >>>>> /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 >>>>> is only on node2 and not on my nod1 nor on my arbiternode. This >>>>> file seems to be a regular file and not a symlink. Here is the >>>>> output of the stat command on it from my node2: >>>>> >>>>> File: >>>>> ?/data/myvolume/brick/.glusterfs/indices/xat...

On 07/29/2017 04:36 PM, mabi wrote: > Hi, > > Sorry for mailing again but as mentioned in my previous mail, I have > added an arbiter node to my replica 2 volume and it seem to have gone > fine except for the fact that there is one single file which needs > healing and does not get healed as you can see here from the output of > a "heal info": > > Brick

...healing using the "heal <volume> info" command and it still shows that very same GFID on node2 to be healed. So nothing changed here. >>>>>> The file /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 is only on node2 and not on my nod1 nor on my arbiternode. This file seems to be a regular file and not a symlink. Here is the output of the stat command on it from my node2: >>>>>> File: ?/data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397? >>>>>> Size: 0 Blocks: 1...

Hi, Sorry for mailing again but as mentioned in my previous mail, I have added an arbiter node to my replica 2 volume and it seem to have gone fine except for the fact that there is one single file which needs healing and does not get healed as you can see here from the output of a "heal info": Brick node1.domain.tld:/data/myvolume/brick Status: Connected Number of entries: 0 Brick

...ame GFID on node2 to be healed. So nothing changed here. >>>>>>> >>>>>>> The file >>>>>>> /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397 >>>>>>> is only on node2 and not on my nod1 nor on my arbiternode. This >>>>>>> file seems to be a regular file and not a symlink. Here is the >>>>>>> output of the stat command on it from my node2: >>>>>>> >>>>>>> File: >>>>>>> ?/da...

...:gfs2" UUID: 885E2E87-90CE-B916-8A73-D66336CD98C0 Now start on node2 gfs: service gfs start. No make on both nodes in / the directory windows: mkdir windows. Then mount on both nodes the gfs filesystem to windows: mount -t gfs2 /dev/drbd0 /windows. Now lets do testing, on nod1: cd /windows. touch test.txt [root at node1 windows]# ls test.txt On node2 you must see in /windows: [root at node2 windows]# ls test.txt. On node2: vim test.txt, i, this is a test from node2,:, wq. On node1: /cat/windows/test.txt [root at node1 windows]# cat /windows/test.txt this is a test fr...

...:gfs2" UUID: 885E2E87-90CE-B916-8A73-D66336CD98C0 Now start on node2 gfs: service gfs start. No make on both nodes in / the directory windows: mkdir windows. Then mount on both nodes the gfs filesystem to windows: mount -t gfs2 /dev/drbd0 /windows. Now lets do testing, on nod1: cd /windows. touch test.txt [root at node1 windows]# ls test.txt On node2 you must see in /windows: [root at node2 windows]# ls test.txt. On node2: vim test.txt, i, this is a test from node2,:, wq. On node1: /cat/windows/test.txt [root at node1 windows]# cat /windows/test.txt this is a test fr...

...:gfs2" UUID: 885E2E87-90CE-B916-8A73-D66336CD98C0 Now start on node2 gfs: service gfs start. No make on both nodes in / the directory windows: mkdir windows. Then mount on both nodes the gfs filesystem to windows: mount -t gfs2 /dev/drbd0 /windows. Now lets do testing, on nod1: cd /windows. touch test.txt [root at node1 windows]# ls test.txt On node2 you must see in /windows: [root at node2 windows]# ls test.txt. On node2: vim test.txt, i, this is a test from node2,:, wq. On node1: /cat/windows/test.txt [root at node1 windows]# cat /windows/test.txt this is a test fr...