| Summary: | distribute option lookup-unhashed should be on by default | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Krishna Srinivas <krishna> |
| Component: | distribute | Assignee: | Krishna Srinivas <krishna> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | mainline | CC: | amarts, gluster-bugs, vijay |
| 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: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Krishna Srinivas
2010-04-16 20:40:57 UTC
distribute option lookup-unhashed should be on by default. Assume the following scenario: * distribute subvolumes expanded * defrag script is run to create new hash ranges, still no link files are created * create of an existing file name is done. This causes the create to succeed as it looks up at a subvol pointed to by new hash range. hence duplicate entries are created. Making lookup-unhashed auto not fix the above problem. lookup-unhashed on will fix. Please reproduce. (In reply to comment #2) > Please reproduce. Krishna, Any updates on this? *** Bug 1166 has been marked as a duplicate of this bug. *** PATCH: http://patches.gluster.com/patch/3752 in master (dht: set 'lookup-unhashed' to ON by default (instead of 'auto').) |