Bug 1159529
Summary: | Can not compile the glusterfs-3.6.0 source bag in a "disperse 5 redundary 2" volume's mountpoint | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | jiademing.dd <iesool> |
Component: | disperse | Assignee: | Xavi Hernandez <jahernan> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.6.0 | CC: | bugs, gluster-bugs, jahernan, lmohanty |
Target Milestone: | --- | Keywords: | Triaged |
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-01-19 14:56:29 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: | 1159471, 1183716 | ||
Bug Blocks: | 1163723 |
Description
jiademing.dd
2014-11-01 09:49:56 UTC
cp -r mountpoint/glusterfs-3.6.0 out from the mountpoint, ./autogen.sh,./configure, make is OK! I tried like this: 1)delete ec_lock_prepare_entry(fop, &fop->loc[1], 1) in ec_manager_rename() 1310 ec_lock_prepare_entry(fop, &fop->loc[0], 1); 1311 // ec_lock_prepare_entry(fop, &fop->loc[1], 1); I know we must lock the new_loc's perent, this just a test. 2)remove O_APPEND flag, refer to bug1161885's patch https://bugzilla.redhat.com/show_bug.cgi?id=1161885 then I can ./autogen.sh,./configure, make the glusterfs-3.6.0 source bag in a "disperse 5 redundary 2“ volume's mountpoint, I think the result of this problem is rename's lock(newloc's parent) in disperse How do you think? @Xavier Hernandez Yes, this problem is initially related to the rename problem, however solving this initial bug may produce crashes because of a timer issue that doesn't have a good solution right now (bug #1163822). This is one of the causes why bug #1159471 is failing and not solved yet. I'm waiting to solve all other detected problems before working on this bug because I think this failure is caused by the combination of some other problems. I've checked this problem with current master and patches 9079, 9407 and 9420 applied and it has compiled successfully. *** This bug has been marked as a duplicate of bug 1161885 *** |