Bug 763443 (GLUSTER-1711) - Volume files for nfs xlator are generated wrongly
Summary: Volume files for nfs xlator are generated wrongly
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-1711
Product: GlusterFS
Classification: Community
Component: core
Version: nfs-alpha
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Shehjar Tikoo
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-27 07:07 UTC by Sachidananda Urs
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

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

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Amar Tumballi 2010-09-27 04:55:17 UTC 
checked the volgen script of 3.0.5. That doesn't contain anything related to access-control. 

In mainline (3.1) this is handled properly. Seems that issues is present only in NFS-Beta branch..

Hence assigned it to Shehjar
Comment 1 Sachidananda Urs 2010-09-27 07:07:23 UTC 
glusterfs-volgen -n nfsexport --nfs 192.168.1.90:/exports/nfs 192.168.1.91:/exports/nfs 192.168.1.92:/exports/nfs 192.168.1.93:/exports/nfs

Generate vol-file with a dangling volume:


volume posix1
    type storage/posix
#   option o-direct enable # (default: disable) boolean type only
#   option export-statfs-size no # (default: yes) boolean type only
#   option mandate-attribute off # (default: on) boolean type only
#   option span-devices 8 # (default: 0) integer value
#   option background-unlink yes # (default: no) boolean type
    option directory /exports/nfs
end-volume

volume posix-ac1
    type features/access-control
    subvolumes posix1
end-volume

volume locks1
    type features/locks
#   option mandatory on # Default off, used in specific applications
    subvolumes posix1
end-volume

========
subvolumes for locks1 should be posix-ac1. posix-ac1 is dangling.
Comment 2 Amar Tumballi 2010-10-04 04:35:41 UTC 
Please update the bug with current status
Comment 3 Shehjar Tikoo 2010-10-04 05:23:08 UTC 
(In reply to comment #2)
> Please update the bug with current status

Only applicable for nfs-beta. No worries. I'll fix it for the next RC.
Comment 4 Shehjar Tikoo 2010-10-05 08:53:41 UTC 
Changing target milestone because nfs-beta's volgen code is not relevant anymore for the mainline branch.
Comment 5 Shehjar Tikoo 2010-11-09 08:42:14 UTC 
This is a nfs-beta volgen bug. Closing.
Note You need to log in before you can comment on or make changes to this bug.