Bug 1397499 - Create directory with dot failed on FUSE mounted Gluster
Summary: Create directory with dot failed on FUSE mounted Gluster
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: fuse
Version: 3.8
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-22 16:14 UTC by Quentin
Modified: 2023-09-14 03:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-07 10:35:48 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)
Screenshot of directory listing (9.57 KB, image/png)
2016-11-22 16:14 UTC, Quentin
no flags Details

Description Quentin 2016-11-22 16:14:00 UTC
Created attachment 1222764 [details]
Screenshot of directory listing

Description of problem:

If you create a directory with a dot in it on a FUSE mounted Gluster system, you'll see a directory with question marks in it.
Log files give entries like:
remote operation failed. Path: /config/conf.d (00000000-0000-0000-0000-000000000000) [No data available]

Version-Release number of selected component (if applicable):

3.8.4-1.el7.x86_64

How reproducible:

Every time you create a directory with a dot on FUSE mounted Gluster filesystem.

Steps to Reproduce:
1. Mount a Gluster system with the FUSE client
2. Go to the mounted directory
3. Create a directory with dot in it, f.e.: conf.d
4. Do a 'ls -al' on the path and you'll see the question marks.

Actual results:

Directory create like:
d????????? ? ?    ?       ?            ? conf.d

Expected results:

Directory like this:
drwxr-xr-x 2 root root 4096 Nov 22 16:59 conf.d


Additional info:

Comment 2 Niels de Vos 2017-11-07 10:35:48 UTC
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.

Comment 3 Red Hat Bugzilla 2023-09-14 03:34:52 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


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