Bug 1472773
Summary: | [GNFS] GNFS got crashed while mounting volume on solaris client | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Manisha Saini <msaini> |
Component: | gluster-nfs | Assignee: | Niels de Vos <ndevos> |
Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> |
Severity: | unspecified | Docs Contact: | |
Priority: | urgent | ||
Version: | rhgs-3.3 | CC: | amukherj, msaini, ndevos, rhinduja, rhs-bugs, storage-qa-internal |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | RHGS 3.3.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | glusterfs-3.8.4-37 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-09-21 05:04:21 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: | |
Embargoed: | |||
Bug Depends On: | 1468291, 1477190 | ||
Bug Blocks: | 1417151, 1451224 |
Description
Manisha Saini
2017-07-19 11:38:18 UTC
upstream patch : https://review.gluster.org/17822 In case no sub-dir is given for mounting, mnt3_parse_dir_exports() returns -ENOENT. I expected it to return "/" in case no subdir, was given during mounting. Now testing with getting "/" as default subdir. Behaviour of no-subdir and subdir mounts should be the same everywhere. Two more upstream patches have been posted: https://review.gluster.org/17897 - libglusterfs: the global_xlator should have valid cbks https://review.gluster.org/17898 - nfs: use "/" as subdir for volume mounts With these changes subdir mounting (and restricting access) works for me. The additional test by deleting the subdir after mounting does not segfault anymore either. upstream 3.12 patches: https://review.gluster.org/17946 https://review.gluster.org/17947 Niels, As the use case is passing for this bug we can keep this bug in Verified state only instead of moving from verified to FailQA. We can have a separate bug to track this backport. 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. https://access.redhat.com/errata/RHBA-2017:2774 |