Displaying 5 results from an estimated 5 matches for "node004".
Did you mean:
node04
2006 Jun 24
3
recover data from linear raid
Hello,
I had a scientific linux 3.0.4 system (rhel compatible), with 3
ide disks, one for / and two others in linear raid (250 gb and 300 gb
each).
This system was obsoleted so i move the raid disks to a new
scientific linux 3.0.7 installation. However, the raid array was not
detected ( I put the disks on the same channels and same master/lsave
setup as in the previous setup). In fact
2017 Aug 24
1
using both ConnectTo and AutoConnect to avoid network partitions
...ket
-- Got REQ_KEY from node003 while we already started a SPTPS session!
-- Invalid packet seqno: 7951 != 1 from node003 (22.22.22.22 port 655)
-- Failed to verify SIG record from node003 (22.22.22.22 port 655)
-- message repeated 3 times: [ Received short packet]
-- Metadata socket read error for node004 (33.33.33.33 port 655):
Connection reset by peer
-- Failed to decrypt and verify packet from node005 (44.44.44.44 port 655)
-nirmal
On Tue, Aug 22, 2017 at 11:08 PM, Guus Sliepen <guus at tinc-vpn.org> wrote:
> On Tue, Aug 22, 2017 at 03:19:18PM -0700, Nirmal Thacker wrote:
>
>...
2011 Mar 28
1
gluster 3.1.3 mount using nfs
...ter 5 seconds
nfs mount: retry: giving up on: /mnt
and it was ok when I tried it in linux machine.
I attached the volume setting
Plz help me out.
Volume Name: isi
Type: Distributed-Replicate
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: node003:/data02
Brick2: node004:/data02
Brick3: node005:/data02
Brick4: node006:/data02
Options Reconfigured:
nfs.rpc-auth-allow: 150.2.223.249
nfs.rpc-auth-unix: on
Cloud Computing Business Team
Andrew Kong Assistant Manager | andrew.kong at sk.com| T:+82-2-6400-4328 | M:+82-10-8776-5025
SK u-Tower, 25-1, Jeongja-dong, Bundan...
2012 Jan 04
0
FUSE init failed
...volume
14:
15: volume test-volume-client-2
16: type protocol/client
17: option remote-host node003
18: option remote-subvolume /local
19: option transport-type tcp
20: end-volume
21:
22: volume test-volume-client-3
23: type protocol/client
24: option remote-host node004
25: option remote-subvolume /local
26: option transport-type tcp
27: end-volume
28:
29: volume test-volume-replicate-0
30: type cluster/replicate
31: subvolumes test-volume-client-0 test-volume-client-1
32: end-volume
33:
34: volume test-volume-replicate-1
35: type...
2017 Aug 22
3
using both ConnectTo and AutoConnect to avoid network partitions
Hi Guus
Thanks for clarifying. Some follow up questions:
- How do we patch 1.1pre14 with this fix? Or will there be a 1.1pre15 to
upgrade to?
- What is the workaround until we patch with this fix? Using a combination
of AutoConnect and ConnectTo?
- When we use ConnectTo, is it mandatory to have a cert file in the hosts/*
dir with an IP to ConnectTo ?
-nirmal
On Tue, Aug 22, 2017 at 12:10