| Summary: | vmware unmount crashes nfsx | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Shehjar Tikoo <shehjart> |
| Component: | nfs | Assignee: | Shehjar Tikoo <shehjart> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | nfs-alpha | CC: | gluster-bugs, lakshmipathi |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | RTP | Mount Type: | nfs |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Shehjar Tikoo
2010-05-24 12:33:43 UTC
nfsx provides users to mount nfs exports using just volume names also. For eg, if there is a subvolume exported through nfsx called posix, then the traditional way to mount it is using the /posix export name with the mount command. nfsx, in its attempt to be a little fancy, allows users to exclude the / in front of volume names. Unfortunately the mount code path supports such export names, i.e without a / but the unmount code path does not. The way to reproduce is to mount using "posix" style and the unmount. Just doing that crashes it. The tests till now have all used the /posix as the export name so it never showed up. Ah! I know why it never crashed earlier when I tested it myself. Linux nfs client does not even send the unmount request when it sees that an export has been mounted without a / in front of the export name. So Linux NFS client never hit this code path, even when I tested it myself during development. PATCH: http://patches.gluster.com/patch/3356 in master (mount3: Handle <volname> as well for unmount dirpath) Regression Test See Comment 1 for details. Test Case 1. Create a posix+nfsx vol file and start glusterfsd. 2. Start vsphere client tool on a windows machine and connect to the ESX server. 3. In vSphere, create a NFS datastore through the Configuration->Storage tab. 4. Suppose the exported volume is called "posix", the traditional way of mounting will be /posix. But, while creating the data store, give the export name only as "posix" instead of /posix. 5. Start up the datastore. 6. Next, right click on the NFS data store and click unmount. The test is a success if nfsx does not crash at the end of step 6. Verified with nfs-beta-rc10. |