issue 9
(Unable to mount chiron-ctl) commented on by tiago.tuxkiller
- gdavis33,
Please, create this directory before and try again:
# mkdir /var/run/chironctl
# chironfs.....
I got this problem and this solved!
Regards
gdavis33,
Please, create this directory before and try again:
# mkdir /var/run/chironctl
# chironfs.....
I got this problem and this solved!
Regards
issue 12
(/var/run/chironctl and /etc/fstab) reported by tiago.tuxkiller
- What steps will reproduce the problem?
1. Use "ctl" option using /etc/fstab
2. Look at /var/run/chironctl
What is the expected output? What do you see instead?
/var/run/chironctl working with FUSE :)
/var/run/chironctl not working, only if I don't use /etc/fstab to mount:
# chironfs /real1=/real2 /virtual --fuseoptions allow_other --ctl
/var/run/chironctl --log /var/log/chironfs.log
# df -h
Filesystem Size Used Avail Use% Mounted on
/real1=/real2 5.0G 500M 4.2G 11% /virtual
fuse 4.0G 0 4.0G 0% /var/run/chironctl
What version of the product are you using? On what operating system?
I'm using ChironFS 1.1.1 on RHEL 5.2 x86_64.
More details:
http://groups.google.com/group/chironfs-forum/browse_thread/thread/2b2ce1e2fb5cf119
What steps will reproduce the problem?
1. Use "ctl" option using /etc/fstab
2. Look at /var/run/chironctl
What is the expected output? What do you see instead?
/var/run/chironctl working with FUSE :)
/var/run/chironctl not working, only if I don't use /etc/fstab to mount:
# chironfs /real1=/real2 /virtual --fuseoptions allow_other --ctl
/var/run/chironctl --log /var/log/chironfs.log
# df -h
Filesystem Size Used Avail Use% Mounted on
/real1=/real2 5.0G 500M 4.2G 11% /virtual
fuse 4.0G 0 4.0G 0% /var/run/chironctl
What version of the product are you using? On what operating system?
I'm using ChironFS 1.1.1 on RHEL 5.2 x86_64.
More details:
http://groups.google.com/group/chironfs-forum/browse_thread/thread/2b2ce1e2fb5cf119
Jul 30, 2008
issue 11
(ChironFS log file) reported by tiago.tuxkiller
- What steps will reproduce the problem?
1. Create one /virtual with /real1 and /real2
2. Write on /virtual like this:
# for i in `seq 1 5`; do dd if=/dev/zero of=/virtual/`echo $RANDOM` bs=1k
count=`echo $RANDOM`; done
3. Write on /real1 like step #2 and see the logs
What is the expected output? What do you see instead?
I'm seeing this:
2008/07/30 16:46 getattr failed accessing /real1 No such file or directory
2008/07/30 16:46 getattr failed accessing /real1 No such file or directory
2008/07/30 16:46 getattr failed accessing /real1 No such file or directory
2008/07/30 16:46 unlink failed accessing /real1 No such file or directory
I would like to see the name of file that was not found.
What version of the product are you using? On what operating system?
ChironFS 1.1.1 em RHEL 5.2 x86_64
What steps will reproduce the problem?
1. Create one /virtual with /real1 and /real2
2. Write on /virtual like this:
# for i in `seq 1 5`; do dd if=/dev/zero of=/virtual/`echo $RANDOM` bs=1k
count=`echo $RANDOM`; done
3. Write on /real1 like step #2 and see the logs
What is the expected output? What do you see instead?
I'm seeing this:
2008/07/30 16:46 getattr failed accessing /real1 No such file or directory
2008/07/30 16:46 getattr failed accessing /real1 No such file or directory
2008/07/30 16:46 getattr failed accessing /real1 No such file or directory
2008/07/30 16:46 unlink failed accessing /real1 No such file or directory
I would like to see the name of file that was not found.
What version of the product are you using? On what operating system?
ChironFS 1.1.1 em RHEL 5.2 x86_64
Jul 29, 2008
issue 10
(1.0.0 fails to exec file) reported by eliterr
- What steps will reproduce the problem?
1. make 3 empty dirs: r1, r2 and r
2. chironfs r1=r2 r
3. cat >> r/tst.sh
#!/bin/sh
echo "OK"
4. chmod u+x r/tst.sh
5. execute ./r/a.sh
What is the expected output? What do you see instead?
Expected: OK
I see: bash: ./r/tst.sh: /bin/sh: bad interpreter: Bad address
What version of the product are you using? On what operating system?
official packages onup-to-date Debian sid and RHEL5
Please provide any additional information below.
I also had a look on chironfs-1.1.1 and didn't find this bug there.
What steps will reproduce the problem?
1. make 3 empty dirs: r1, r2 and r
2. chironfs r1=r2 r
3. cat >> r/tst.sh
#!/bin/sh
echo "OK"
4. chmod u+x r/tst.sh
5. execute ./r/a.sh
What is the expected output? What do you see instead?
Expected: OK
I see: bash: ./r/tst.sh: /bin/sh: bad interpreter: Bad address
What version of the product are you using? On what operating system?
official packages onup-to-date Debian sid and RHEL5
Please provide any additional information below.
I also had a look on chironfs-1.1.1 and didn't find this bug there.
issue 3
(Problems with ChironFS over sshFS) commented on by meyerbro
- Hi Luis, do you know if Leo Eraly already has the Suse RPM ChironFS package for the
1.1.1 version?
Thanks,
Felipe
Hi Luis, do you know if Leo Eraly already has the Suse RPM ChironFS package for the
1.1.1 version?
Thanks,
Felipe