| Summary: | booster does not work properly with ls | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Krishna Srinivas <krishna> |
| Component: | booster | Assignee: | Shehjar Tikoo <shehjart> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | pre-2.0 | CC: | anush, gluster-bugs, raghavendra |
| 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: | RTNR | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Krishna Srinivas
2009-10-05 08:56:00 UTC
root@halt:/home/krishna/volfiles# cat booster.conf
/home/krishna/volfiles/protocol-client.vol /mnt/glusterfs glusterfs logfile=/tmp/log.log,loglevel=TRACE
root@halt:/home/krishna/volfiles#
do:
export GLUSTERFS_BOOSTER_FSTAB=$(pwd)/booster.conf
export LD_PRELOAD=/opt/glusterfs/lib/glusterfs/glusterfs-booster.so
root@halt:/home/krishna/volfiles# ls
?´?? -client.vol~ -server-2.vol~ -server.vol~ -server2.vol conf~ lient.vol l~ t
-client.vol -server-2.vol -server.vol -server1.vol conf l lient.vol~ nt.vol
root@halt:/home/krishna/volfiles#
root@halt:/home/krishna/volfiles# ls /mnt/glusterfs
aaaaa asd asd2
root@halt:/home/krishna/volfiles#
The problem has most probably got to do with exporting the GLUSTERFS_BOOSTER_FSTAB variable globally and running the ls for a non-booster directory. i.e. Do not expect generic commands to work with booster while not using an absolute path. This is most probably being caused because ls -l opens "." as the path. Will look into this on a low priority basis as getting general core-utils to work with booster is not a priority task right now. *** Bug 333 has been marked as a duplicate of this bug. *** I think we can close this bug, since 333 is fixed. |