search for: knfs

...>> capture_nfssucceed.pcap has the results from the successful touch >> experiment >> >> The brick log files are there too. > > Thanks for sharing. Looks like the error is not generated > @gluster-server side. The permission denied error was caused by either > kNFS or by fuse-mnt process or probably by the combination. > > To check fuse-mnt logs, please look at > /var/log/glusterfs/<fuse_mnt_direcotry>.log > > For eg.: if you have fuse mounted the gluster volume at /mnt/fuse-mnt > and exported it via kNFS, the log location for that f...

...s from the failed touch experiment > capture_nfssucceed.pcap has the results from the successful touch > experiment > > The brick log files are there too. Thanks for sharing. Looks like the error is not generated @gluster-server side. The permission denied error was caused by either kNFS or by fuse-mnt process or probably by the combination. To check fuse-mnt logs, please look at /var/log/glusterfs/<fuse_mnt_direcotry>.log For eg.: if you have fuse mounted the gluster volume at /mnt/fuse-mnt and exported it via kNFS, the log location for that fuse_mnt shall be at /var/lo...

...pcap has the results from the successful touch >>> experiment >>> >>> The brick log files are there too. >> >> Thanks for sharing. Looks like the error is not generated >> @gluster-server side. The permission denied error was caused by >> either kNFS or by fuse-mnt process or probably by the combination. >> >> To check fuse-mnt logs, please look at >> /var/log/glusterfs/<fuse_mnt_direcotry>.log >> >> For eg.: if you have fuse mounted the gluster volume at /mnt/fuse-mnt >> and exported it via kNFS, the...

...the successful touch >>>> experiment >>>> >>>> The brick log files are there too. >>> >>> Thanks for sharing. Looks like the error is not generated >>> @gluster-server side. The permission denied error was caused by >>> either kNFS or by fuse-mnt process or probably by the combination. >>> >>> To check fuse-mnt logs, please look at >>> /var/log/glusterfs/<fuse_mnt_direcotry>.log >>> >>> For eg.: if you have fuse mounted the gluster volume at /mnt/fuse-mnt >>> and exp...

Hi Soumya, When I originally did the tests I ran tcpdump on the client. I have rerun the tests, doing tcpdump on the server tcpdump -i any -nnSs 0 host 172.16.1.121 -w /root/capture_nfsfail.pcap The results are in the same place http://mseas.mit.edu/download/phaley/GlusterUsers/TestNFSmount/ capture_nfsfail.pcap has the results from the failed touch experiment capture_nfssucceed.pcap has

...t;>>> experiment >>>>> >>>>> The brick log files are there too. >>>> >>>> Thanks for sharing. Looks like the error is not generated >>>> @gluster-server side. The permission denied error was caused by >>>> either kNFS or by fuse-mnt process or probably by the combination. >>>> >>>> To check fuse-mnt logs, please look at >>>> /var/log/glusterfs/<fuse_mnt_direcotry>.log >>>> >>>> For eg.: if you have fuse mounted the gluster volume at /mnt/fuse-mnt...

Hello, I'm designing a 2-node, HA NAS that must support NFS. I had planned on using GlusterFS native NFS until I saw that it is being deprecated. Then, I was going to use GlusterFS + NFS-Ganesha until I saw that the Ganesha HA support ended after 3.10 and its replacement is still a WIP. So, I landed on GlusterFS + kernel NFS + corosync & pacemaker, which seems to work quite well. Are

We have here an knfs fileserver running ext3 on 2.4.18 kernel with three filesystems: <CLIP> Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda3 10080520 3609632 6368476 37% / /dev/hda4 16437332 12295408 3974932 76% /home /dev/md1 1024872060...

Help please- I am running 3.3.1 on Centos using a 10GB network. I get reasonable write speeds, although I think they could be faster. But my read speeds are REALLY slow. Executive summary: On gluster client- Writes average about 700-800MB/s Reads average about 70-80MB/s On server- Writes average about 1-1.5GB/s Reads average about 2-3GB/s Any thoughts? Here are some additional details: