Bug 999939

Summary:	Dist-geo-rep : geo-rep syncs block special, character special files and pipe as regular files to the slave
Product:	Red Hat Gluster Storage	Reporter:	Vijaykumar Koppad <vkoppad>
Component:	geo-replication	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED ERRATA	QA Contact:	Vijaykumar Koppad <vkoppad>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	2.1	CC:	aavati, asengupt, bbandari, csaba, rhs-bugs, surs, vraman
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.4.0.24rhs-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-23 22:38:52 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Vijaykumar Koppad 2013-08-22 11:56:53 UTC

Description of problem:Geo-rep syncs block special, character special and pipe as regular file to the slave 


Version-Release number of selected component (if applicable):glusterfs-3.4.0.21rhs-1.el6rhs.x86_64


How reproducible:Happens everytime 


Steps to Reproduce:
1.create and start a geo-rep relationship between master and slave. 
2.on the master create block special , character special files and pipe like mknod file_block b 12 5, mknod file_char c 12 5, and mknod file_pipe pipe
3.check it on the slave. 

Actual results:geo-rep syncs them as regular files


Expected results: Either it should be synced as the same file type or not sync at all 


Additional info:

Comment 2 Amar Tumballi 2013-08-27 06:14:16 UTC

https://code.engineering.redhat.com/gerrit/#/c/11998

Comment 3 Vijaykumar Koppad 2013-08-28 10:36:31 UTC

verified on glusterfs-3.4.0.24rhs-1.el6rhs.x86_64

Comment 4 Scott Haines 2013-09-23 22:38:52 UTC

Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html

Comment 5 Scott Haines 2013-09-23 22:41:31 UTC

Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. 

For information on the advisory, and where to find the updated files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1262.html