Hide Forgot
(In reply to comment #0) > 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# same with rm: root@halt:/home/krishna/volfiles# rm /mnt/glusterfs/asd rm: cannot remove `/mnt/glusterfs/asd': No such file or directory root@halt:/home/krishna/volfiles#
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.
*** This bug has been marked as a duplicate of bug 333 ***