Bug 1098023
Summary: | dht: mkdir fails for a particular name over nfs mount | ||||||
---|---|---|---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Saurabh <saujain> | ||||
Component: | distribute | Assignee: | Raghavendra G <rgowdapp> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | storage-qa-internal <storage-qa-internal> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | rhgs-3.0 | CC: | mzywusko, nbalacha, rgowdapp, smohan, spalai, tdesala, vbellur | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
Whiteboard: | triaged, dht-nameless-lookup-heal, dht-fixed | ||||||
Fixed In Version: | 3.7.9-10 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2017-03-25 14:24:20 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: | 1286208 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Saurabh
2014-05-15 05:52:13 UTC
Again, seen for this below directory [root@rhsauto054 ~]# ls /mnt/nfs-test [root@rhsauto054 ~]# mkdir /mnt/nfs-test//run6582/ mkdir: cannot create directory `/mnt/nfs-test//run6582/': Invalid argument Problem seen in this BZ is described bit more here, if you check the following lines of execution, then [root@rhsauto054 ~]# mkdir /mnt/nfs-test//run7777 mkdir: cannot create directory `/mnt/nfs-test//run7777': Invalid argument [root@rhsauto054 ~]# mkdir /mnt/nfs-test/run7777 mkdir: cannot create directory `/mnt/nfs-test/run7777': Invalid argument [root@rhsauto054 ~]# cd /mnt/nfs-test [root@rhsauto054 nfs-test]# mkdir run7777 mkdir: cannot create directory `run7777': Invalid argument if the mkdir is executed using "//" , bascially two slashes it fails ---> /mnt/nfs-test//run7777 ---- fails and even if you cd in the mount -point /mnt/nfs-test and try to create run7777, this attempt also fails. So, altogether the behaviour is wrong, needs correction. some more observation, presently highly confusing, [root@rhsauto054 ~]# mkdir /mnt/nfs-test//lllll mkdir: cannot create directory `/mnt/nfs-test//lllll': Invalid argument [root@rhsauto054 ~]# mkdir /mnt/nfs-test/llll mkdir: cannot create directory `/mnt/nfs-test/llll': Invalid argument [root@rhsauto054 ~]# mkdir /mnt/nfs-test/ll mkdir: cannot create directory `/mnt/nfs-test/ll': Invalid argument [root@rhsauto054 ~]# mkdir /mnt/nfs-test/rrr [root@rhsauto054 ~]# mkdir /mnt/nfs-test//rrrr [root@rhsauto054 ~]# mkdir /mnt/nfs-test//nnnnn [root@rhsauto054 ~]# mkdir /mnt/nfs-test//mmmmmmm mkdir: cannot create directory `/mnt/nfs-test//mmmmmmm': Invalid argument [root@rhsauto054 ~]# mkdir /mnt/nfs-test/mmmm Hi Saurabh, Tested the same on master branch upstream. Was not able reproduce the issue. From the log it seems layout had anomaly. [2014-05-15 05:41:48.140416] W [dht-layout.c:178:dht_layout_search] 0-dist-rep-dht: no subvolume for hash (value) = 2672484811 ---> Check Here [2014-05-15 05:41:48.144727] W [dht-layout.c:178:dht_layout_search] 0-dist-rep-dht: no subvolume for hash (value) = 2672484811 [2014-05-15 05:41:48.144838] W [nfs3.c:2722:nfs3svc_mkdir_cbk] 0-nfs: 6b260899: /run5959 => -1 (Invalid argument) Would you be able to provide sos reports so that I can find what might have caused anomaly in layout. * And dht does not blocks file creation with specific names. Created attachment 898315 [details]
nfs.log
Seems similar to bz 1110457. EINVAL is currently seen when a subvolume of dht is offline. This needs to be tested against the latest build. There is a WIP patch on upstream at: http://review.gluster.org/#/c/12414/ and this bug is most likely a duplicate of bz 1286208 https://code.engineering.redhat.com/gerrit/74435 should've fixed this. Hence marking this bug to be verified by QE. Please suggest the steps/scenarios to verify the fix. Tested this BZ with glusterfs version: 3.8.4-3.el7rhgs.x86_64. Raghavendra G has suggested the below scenario to verify the fix. 1) Create a distributed replicated volume and start it. 2) Enable nfs on the volume and NFS mount the volume on a client. 3) From mount point, create a directory. 4) Induce holes on the layout by setting the trusted.glusterfs.dht attribute to empty. 5) Bring down few bricks which are having correct layout. 6) Bring up the killed bricks. 7) Perform lookup on the directory and the directory layout should get healed without any holes or overlaps. No issues were seen. Hence, moving this BZ to Verified. |