Bug 762462 (GLUSTER-730) - unknown filetypes and inode conflicts in afr
Summary: unknown filetypes and inode conflicts in afr
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-730
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anand Avati
QA Contact:
URL:
Whiteboard:
: GLUSTER-811 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-17 12:25 UTC by Raghavendra Bhat
Modified: 2015-12-01 16:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
log files of client and server and ls output on the mount point and export directories (3.53 KB, application/octet-stream)
2010-03-17 09:25 UTC, Raghavendra Bhat 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Raghavendra Bhat 2010-03-17 12:25:38 UTC 
The client log file says unknown filetype and inode conflict. Actually one of the backend directories contained some files and directories before starting glusterfs. Those files are not selfhealed. 

The server log files says in posix_setattr function setattr(lstat) on <file_name> failed. 

The client and server logs are attached. Also the "ls" output on the mountpoint and both the export directories are attached.
Comment 1 Vikas Gorur 2010-03-17 16:05:58 UTC 
This is because of POSIX constants still being used in afr:

afr-self-heal-common.c:1223:	case S_IFREG:
afr-self-heal-entry.c:767:	case S_IFREG:
afr-self-heal-entry.c:1759:	case S_IFREG:

These need to be changed to use the iatt constants.
Comment 2 Anand Avati 2010-04-08 16:57:01 UTC 
PATCH: http://patches.gluster.com/patch/3127 in master (iatt: change S_IF macros with IA_IF macros in missing places)
Comment 3 Vikas Gorur 2010-04-13 15:43:48 UTC 
*** Bug 811 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.