Displaying 5 results from an estimated 5 matches for "4e2e".
Did you mean:
4e20
2017 Jul 31
0
Possible stale .glusterfs/indices/xattrop file?
...> /data/myvolume/brick/.glusterfs/29/e0/29e0d13e-1217-41cc-9bda-1fbbf781c397
> -ls
>
> node1:
> 8404683 0 lrwxrwxrwx 1 root root 66 Jul 27 15:43
> /data/myvolume/brick/.glusterfs/29/e0/29e0d13e-1217-41cc-9bda-1fbbf781c397
> -> ../../fe/c0/fec0e4f4-38d2-4e2e-b5db-fdc0b9b54810/OC_DEFAULT_MODULE
>
> node2:
> 8394638 0 lrwxrwxrwx 1 root root 66 Jul 27 15:43
> /data/myvolume/brick/.glusterfs/29/e0/29e0d13e-1217-41cc-9bda-1fbbf781c397
> -> ../../fe/c0/fec0e4f4-38d2-4e2e-b5db-fdc0b9b54810/OC_DEFAULT_MODULE
>
>
>...
2017 Jul 31
2
Possible stale .glusterfs/indices/xattrop file?
...l 3 nodes below:
sudo find /data/myvolume/brick -samefile /data/myvolume/brick/.glusterfs/29/e0/29e0d13e-1217-41cc-9bda-1fbbf781c397 -ls
node1:
8404683 0 lrwxrwxrwx 1 root root 66 Jul 27 15:43 /data/myvolume/brick/.glusterfs/29/e0/29e0d13e-1217-41cc-9bda-1fbbf781c397 -> ../../fe/c0/fec0e4f4-38d2-4e2e-b5db-fdc0b9b54810/OC_DEFAULT_MODULE
node2:
8394638 0 lrwxrwxrwx 1 root root 66 Jul 27 15:43 /data/myvolume/brick/.glusterfs/29/e0/29e0d13e-1217-41cc-9bda-1fbbf781c397 -> ../../fe/c0/fec0e4f4-38d2-4e2e-b5db-fdc0b9b54810/OC_DEFAULT_MODULE
arbiternode:
find: '/data/myvolume/brick/.glusterfs/29/...
2009 May 08
4
XEN/bridge mode
Hi!
I want to forward the port 3389 from the domU to the virtual server with ip
address 192.168.122.77 with not success...
I tried a lot of iptables rules with no luck so far. Is this possible? I
take a look at other post and I don''t found an answer.
By example:
/sbin/iptables -t nat -A PREROUTING -p tcp -i xenbr0 --dport 3389 -j DNAT
--to 192.168.122.77:3389
the virtual nic for the
2017 Jul 31
0
Possible stale .glusterfs/indices/xattrop file?
On 07/31/2017 02:00 PM, mabi wrote:
> To quickly resume my current situation:
>
> on node2 I have found the following file xattrop/indices file which
> matches the GFID of the "heal info" command (below is there output of
> "ls -lai":
>
> 2798404 ---------- 2 root root 0 Apr 28 22:51
>
2017 Jul 31
2
Possible stale .glusterfs/indices/xattrop file?
To quickly resume my current situation:
on node2 I have found the following file xattrop/indices file which matches the GFID of the "heal info" command (below is there output of "ls -lai":
2798404 ---------- 2 root root 0 Apr 28 22:51 /data/myvolume/brick/.glusterfs/indices/xattrop/29e0d13e-1217-41cc-9bda-1fbbf781c397
As you can see this file has inode number 2798404, so I ran