Bug 764227 (GLUSTER-2495)

Summary: Check for client mounting over brick directory
Product: [Community] GlusterFS Reporter: Jeff Darcy <jdarcy>
Component: unclassifiedAssignee: Rajesh <rajesh>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: mainlineCC: gluster-bugs, vagarwal, vijay
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jeff Darcy 2011-03-07 16:19:35 UTC 
Three times in just the past week, I've had to help users on IRC who were trying to set up peer-to-peer style mounts between a group of servers, and made the "classic" mistake of using the same directories both as bricks and as client mountpoints.  In spirit similar to bug764139, I'd like to suggest that we try to detect and avoid at least the most obvious cases of this error.  One fairly simple trick would be to have storage/posix place an xattr (e.g. trusted.glusterfs.isabrick) on the root directory.  Then mount.glusterfs and nfs/server could check for presence of this xattr, and fail the mount/export if found.  I'm sure many other schemes could be used also.
Comment 1 Rajesh 2011-08-08 03:58:09 UTC 

*** This bug has been marked as a duplicate of bug 2003 ***