Displaying 1 result from an estimated 1 matches for "p2xfhnmc2gr10xsdtd".
2013 Dec 06
1
replace-brick failing - transport.address-family not specified
Hello,
I have what I think is a fairly basic Gluster setup, however when I try to carry out a replace-brick operation it consistently fails...
Here are the command line options:
root at osh1:~# gluster volume info media
Volume Name: media
Type: Replicate
Volume ID: 4c290928-ba1c-4a45-ac05-85365b4ea63a
Status: Started
Number of Bricks: 1 x 2 = 2
Transport-type: tcp
Bricks:
Brick1: