[root@lab0-v3 ~]# mount -t nfs -o tcp,nfsvers=3 localhost:/images /mnt
[root@lab0-v3 ~]# cd /mnt
[root@lab0-v3 mnt]# time bash -c 'tar xf /root/linux-3.3.tar ; sync ;
rm -rf linux-3.3'
real2m26.698s
user0m0.334s
sys 0m6.943s
On Wed, Mar 21, 2012 at 6:22 AM, David Coulson
Weird - Actually slower than fuse. Does the 'nolock' nfs mount option
make a difference?
On 3/21/12 1:22 PM, Bryan Whitehead wrote:
[root@lab0-v3 ~]# mount -t nfs -o tcp,nfsvers=3 localhost:/images /mnt
[root@lab0-v3 ~]# cd /mnt
[root@lab0-v3 mnt]# time bash -c 'tar xf /root/linux-3.3.tar ;
[root@lab0-v3 ~]# mount -t nfs -o tcp,nfsvers=3,nolock localhost:/images /mnt
[root@lab0-v3 ~]# cd /mnt
[root@lab0-v3 mnt]# time bash -c 'tar xf /root/linux-3.3.tar ; sync ;
rm -rf linux-3.3'
real2m26.758s
user0m0.353s
sys 0m7.101s
[root@lab0-v3 mnt]#
On Wed, Mar 21, 2012 at 10:27
Hey all -
Anyone running Gluster on AWS EC2 instances out there?
I'm having some issues using Gluster on EC2 instances. I saw an old
thread titled ec2 peers but didn't see a solution posted as part of
that thread.
Here's my problem -
If I stop/start a single EC2 instance, usually its
Hi everyone,
Hope anyone can shed some light on some strange behavior we've just
having with Gluster.
Last night, while using gluster3.3b2, we came up with some errors, after
running tests for several days.
We're running the test in a striped 4 disk volume:
# gluster volume info data
Volume
