This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 763856 - (GLUSTER-2124) NFS crashes when volume-id option is not given with dynamic-volume option
NFS crashes when volume-id option is not given with dynamic-volume option
Product: GlusterFS
Classification: Community
Component: nfs (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Gaurav
Depends On:
  Show dependency treegraph
Reported: 2010-11-17 05:41 EST by Shehjar Tikoo
Modified: 2015-12-01 11:45 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: RTP
Mount Type: nfs
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Shehjar Tikoo 2010-11-17 05:41:25 EST
Not a critical crash but needs to be fixed nonetheless. Not critical because the only time when dynamic-volume option is set is through the gluster CLI which correctly always sets the volume-id option also.

This crash occurred when Sac manually changed commented out the volume-id line which is not a supported combination of operations.
[2010-11-11 02:37:40.39562] D [nfs.c:212:nfs_subvolume_set_started] nfs: Starting up: distrib , vols started till now: 1
[2010-11-11 02:37:40.39584] T [nfs-fops.c:353:nfs_fop_lookup] nfs: Lookup: /
[2010-11-11 02:37:40.39716] T [rpc-clnt.c:1222:rpc_clnt_record] : Auth Info: pid: 0, uid: 0, gid: 0, owner: 0
[2010-11-11 02:37:40.39739] T [rpc-clnt.c:1122:rpc_clnt_record_build_header] rpc-clnt: Request fraglen 324, payload: 196, rpc hdr: 128
[2010-11-11 02:37:40.39767] T [rpc-clnt.c:1426:rpc_clnt_submit] rpc-clnt: submitted request (XID: 0x5 Program: GlusterFS 3.1, ProgVers: 310, Proc: 27) to rpc-transport (distrib-client-0)
[2010-11-11 02:37:40.39787] T [nfs.c:603:notify] nfs: All children up, starting RPC
[2010-11-11 02:37:40.39801] D [nfs.c:107:nfs_init_versions] nfs: Initing protocol versions
[2010-11-11 02:37:40.39816] D [mount3.c:1567:mnt3svc_init] nfs-mount: Initing Mount v3 state
[2010-11-11 02:37:40.39837] T [mount3.c:1466:__mnt3_init_volume_export] nfs-mount: Volume exports enabled
[2010-11-11 02:37:40.39850] T [mount3.c:1487:mnt3_init_options] nfs-mount: Initing options for: distrib
[2010-11-11 02:37:40.39866] E [mount3.c:1376:__mnt3_init_volume] nfs-mount: DVM is on but volume-id not given for volume: distrib
[2010-11-11 02:37:40.39880] E [mount3.c:1490:mnt3_init_options] nfs-mount: Volume init failed
[2010-11-11 02:37:40.39893] E [mount3.c:1523:mnt3_init_state] nfs-mount: Options init failed
[2010-11-11 02:37:40.39905] E [mount3.c:1570:mnt3svc_init] nfs-mount: Mount v3 state init failed
pending frames:

patchset: v3.1.0
signal received: 11

time of crash: 2010-11-11 02:37:40
configuration details:
argp 1
backtrace 1
dlfcn 1
fdatasync 1
libpthread 1
llistxattr 1
setfsid 1
spinlock 1
epoll.h 1
xattr.h 1
st_atim.tv_nsec 1
package-string: glusterfs 3.1.0
Comment 1 Gaurav 2011-02-08 21:33:33 EST
Its working fine with Cli as we generate volume_id and write it to volfile.
Since in NFS we always expect volume_id for Dynamic-volume = "on", we have to fail nfs_init if its not there, we can gracefully exit with proper error message whenever we don't find any volume_id in volfile.
Comment 2 Anand Avati 2011-02-10 22:18:15 EST
PATCH: in master (NFS : Fail Nfs init if volume-id not found.)
Comment 3 Saurabh 2011-03-10 22:26:14 EST
Please update the target milestone
Comment 4 Saurabh 2011-03-11 01:46:51 EST
Commented the volume id line was commented and then checked the nfs.log , and it disn't point any crash.

Note You need to log in before you can comment on or make changes to this bug.