Hi Shehjar,
Answers:
1.) Filesystem is default ext3 mounted with "defaults,noatime"
2.) I think it how it was becouse I always put io-threads as top(or near
top) translator. Iin TEST5 "iot" can be ignored.
3.) Server(brick) iscsi2 was also client on which I was running the test
and it was also a Xen guest.
One more thing I'd like to point out. In documentation I miss
information of best practices which translators should be put
before/after other translators.
Example: should one put io-threads before or after io-cache? What does
it mean if you configure either way.
Regards,
Marko
Shehjar Tikoo wrote:
Marko wrote:
this document is made for my personal reference so it's a little raw.
A few questions:
1. What was the on-disk file system and the disk organization under the
file system?
2. In the TEST5 volfile, the volume iot is dangling. Is that how it
actually was during the test or was it interposed between volume wb and
volume AFR?
On Wed, Apr 8, 2009 at 6:18 PM, Marko <[email protected]
<mailto:[email protected]>> wrote:
Hello,
To clearify: * im testing with gluisterfs-2.0.0rc7 * all bricks are
on same physical server(Xen guests). It's a testing environment.
Were the client side tests( i.e., both the test program like
make-many-files and the corresponding glusterfs client..) also running
in a Xen guest?
Thanks
Shehjar
_______________________________________________
Gluster-users mailing list
[email protected]
http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users
