Re: Allow ":" as brick path

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Oct 29, 2016 at 01:07:33PM +0200, Gandalf Corvotempesta wrote:
> Would be possible to add support for ":" in brick path?
> 
> i'm trying to use the following command:
> 
> # gluster volume replace-brick gv0 1.2.3.4:/export/brick1/brick
> 1.2.3.4:/export/pci-0000:01:00.0-scsi-0:0:2:0/brick commit force
> wrong brick type: 1.2.3.4:/export/pci-0000:01:00.0-scsi-0:0:2:0/brick,
> use <HOSTNAME>:<export-dir-abs-path>
> Usage: volume replace-brick <VOLNAME> <SOURCE-BRICK> <NEW-BRICK> {commit force}
> 
> but the new brick name is not reconized, probably because there are
> too many ":" in the argument.
> 
> As the hostname (or the IP address) can't have ":", you should get the
> hostname/ip up to the first occurence of ":" and leaving the rest as
> brick name/path

Actually, IPv6 addresses would have ":" too. But, I'm not sure anyone
would want to write IPv6 addresses instead of hostnames.

I guess the parsing of the brick path could always use ":/" as separator
between the hostname and path. Please file a bug for this, as I also
agree that ":" should be allowed in the path.

https://bugzilla.redhat.com/enter_bug.cgi?product=GlusterFS&version=mainline&component=cli

Thanks,
Niels

Attachment: signature.asc
Description: PGP signature

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux