| Summary: | the 'fix.layout' command should happen through 'setxattr', not getxattr(). | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Amar Tumballi <amarts> |
| Component: | distribute | Assignee: | Amar Tumballi <amarts> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | mainline | CC: | aavati, gluster-bugs, jdarcy, lakshmipathi, vraman |
| 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: | Type: | --- | |
| Regression: | RTNR | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 763990 | ||
|
Description
Amar Tumballi
2011-06-23 04:31:47 UTC
I don't disagree, but is there any *particular* reason setxattr would be preferred? (In reply to comment #1) > I don't disagree, but is there any *particular* reason setxattr would be > preferred? We are overhauling gluster volume rebalance. Part of that is to be able to have fine grained control of how a new layout should be. Eg. to span a directory across N nodes, or exclude host XYZ etc. setxattr's value will be used to specify such parameters for the 'fix.layout' key. Avati PATCH: http://patches.gluster.com/patch/7597 in master (distribute: handle 'fix.layout' key in setxattr() instead of getxattr()) verified with 3.2.3qa3 - it didn't show any invalid argument error message. with 3.2.2. #setfattr -n trusted.glusterfs.fix.layout -v something /mnt/ #getfattr -d -m . /mnt gave error message like " [2011-08-19 14:31:59.36928] E [stat-prefetch.c:695:sp_remove_caches_from_all_fds_opened] (-->/opt/glusterfs/3.2.2//lib/glusterfs/3.2.2/xlator/mount/fuse.so(fuse_setxattr_resume+0x427) [0x7f28baa1aec2] (-->/opt/glusterfs/3.2.2//lib/glusterfs/3.2.2/xlator/debug/io-stats.so(io_stats_setxattr+0x2b0) [0x7f28b3df86a2] (-->/opt/glusterfs/3.2.2//lib/glusterfs/3.2.2/xlator/performance/stat-prefetch.so(sp_setxattr+0x151) [0x7f28b804ec22]))) 0-bug764807-stat-prefetch: invalid argument: inode " |