- "Raja" wrote:
Can you please send me the output of this command run as root?
# getfattr -d -m '.*' -e hex zip/tba48701ma141232158444.zip
(The getfattr tool is part of the 'attr' package in Debian/Ubuntu.
Source can be found here: http://packages.debian.org/lenny/attr)
Vikas
--
Engineer
Hi,
I am sending the output of command that i have executed.
r...@web2cokma /opt/home/storage# getfattr -d -m
'.*' -e hex zip/tba48701ma141232158444.zip
# file: zip/tba48701ma141232158444.zip
trusted.glusterfs.afr.data-pending=0x
Regards,
- "Raja" wrote:
Can you ple
- "Raja" wrote:
The problem is being caused by extended attributes that are left over
from the previous version of GlusterFS that you were using.
When migrating to 2.0.1, please run the script 'backend-xattr-sanitize.sh'
on both your backend export directories. You can find the script
in th
Hi Vikas,
Thank you. It works fine, now i can copy the file using apache user.
I need one more help, while i am mounting
gluster its shows the whole path ( in GlusterFS-2.0.1).
glusterfs -f /etc/glusterfs/glusterfs.vol /opt/home/storage/
df -h shows
/etc/glusterfs/glusterfs.vol 137G
- "Raja" wrote:
> Hi Vikas,
>
> Thank you. It works fine, now i can copy the file using apache user.
>
> I need one more help, while i am mounting
> gluster its shows the whole path ( in GlusterFS-2.0.1).
>
> glusterfs -f /etc/glusterfs/glusterfs.vol /opt/home/storage/
This is by desig
Hi,
Thanks for the reply.Have a nice day.
Regards,
- "Raja" wrote:
> Hi Vikas,
>
> Thank you. It works fine, now i can copy the file using apache user.
>
> I need one more help, while i am mounting
> gluster its shows the whole path ( in GlusterFS-2.0.1).
>
> glusterfs -f /etc/glusterf
Hello all,
I am evaluating glusterfs currently and therefore use a testbed consisting of
four (real) boxes, two configured as fileservers, two as clients, see configs
below.
All I have to do to make the fs hang on both clients (sooner or later) is to
run bonnie (a simple fs check program) constant
Stephan von Krawczynski wrote:
Hello all,
I am evaluating glusterfs currently and therefore use a testbed consisting of
four (real) boxes, two configured as fileservers, two as clients, see configs
below.
All I have to do to make the fs hang on both clients (sooner or later) is to
run bonnie (a
elb...@host1:~$ dpkg -l|grep glusterfs
ii glusterfs-client
1.3.8-0pre2 GlusterFS fuse client
ii glusterfs-server
1.3.8-0pre2 GlusterFS fuse server
ii libglusterfs0
1.3.8-0pre2
Also, in the logfiles on the clients, it looks like I get these types
of messages whenever I try to access a file that is no longer
accessible.
2009-06-11 07:58:24 E [fuse-bridge.c:675:fuse_fd_cbk] glusterfs-fuse:
22068570: /hourlogs/myDir0/1243432800.log => -1 (5)
2009-06-11 07:58:24 E [fu
- "Elbert Lai" wrote:
> elb...@host1:~$ dpkg -l|grep glusterfs
> ii glusterfs-client
> 1.3.8-0pre2 GlusterFS fuse client
> ii glusterfs-server
> 1.3.8-0pre2 GlusterFS fuse server
> ii libglusterfs0
Vikas,
Thanks you for responding. I am recommending that the first thing we
do before spending more time troubleshooting this is to upgrade. I
found that someone else reported something quite similar back in
January.
Here the "selfheal complete" is acutaly "selfheal complete
unsuccessfull
12 matches
Mail list logo
