If you can file a bug, we'll take it from there. Thanks.
Whit Blauvelt wrote:
Hi,
Has anyone even seen this before - an NFS mount through Gluster that gets
the filesystem size wrong and is otherwise garbled and dangerous?
Is there a way within Gluster to fix it, or is the lesson that
On Tuesday 31 May 2011 11:01 PM, John Hanks wrote:
Hi,
I'm setting up gluster for the first time and have a single server
with two bricks set up for testing:
[root@filer-jdn1bp1 etc]# gluster volume info
Volume Name: projects
Type: Distribute
Status: Started
Number of Bricks: 2
The culprit appears to be my source NFS server, looks like some of
it's RAID sets decided they needed to rebuild at about the same time I
was doing my testing. One should never assume that because something
worked well yesterday it will work well today, will retry things with
a different source
With NFS server problems resolved, I'm seeing what I'd hoped for which
is rsync processes being more or less CPU bound with no i/o wait. Will
start doing some more in depth benchmarks and likely be back later
with more questions. Thanks for your help.
jbh
On Wed, Jun 1, 2011 at 8:48 AM, John
Greetings,
I just wanted to take a moment and say hello. I am Gluster's new community guy,
and I wrote up an introduction on the blog:
http://blog.gluster.com/2011/06/please-allow-me-to-introduce-myself/
One of the things I tried to make clear in that post is that I want to know
what we
