Bug 765566 (GLUSTER-3834)
Summary: | Error with lost+found directory when using multiple disks | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | ahazelwood |
Component: | core | Assignee: | Divya <divya> |
Status: | CLOSED EOL | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | mainline | CC: | bugs, gluster-bugs, kbsingh, matorola, storage-doc |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-10-22 15:46:38 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | DP | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
ahazelwood
2011-11-30 14:34:04 UTC
We acknowledge that this may be an issue now. But normally we recommend to use a directory inside your mount as export. (if /dev/sdb1 is mounted in /gfs_export/, don't use /gfs_export/ as brick dir, instead use /gfs_export/<VOLNAME> or something like that as export dir) With that, in glusterfs exported directory, you won't have 'lost+found' directory itself. Thanks for having the bug report, we will work on fix this glitch, but as there is a work around, we treat it as an enhancement. Thanks for looking at this. I wasn't sure how it should be marked, so enhancement makes sense. Please at least add this to the installation instructions as potentially a note as it would have saved me some time trying to track down. Thanks. Not working on fixing this, should surely need to document this behavior. Can you please advice how to move from using block device mount as a brick to subdirectory in glusterfs. For example, move all data from /exports/brick1/ (/dev/sdb1 mounted) to /exports/brick1/datadir/ . thanks. because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice. If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it. |