<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
On 18/03/2010 09:46, Amar Tumballi wrote:
<blockquote
cite="mid:9e85838d1003180246neb6eba4jb19ee4847788b22@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
did anybody know how i do an entry for glusterfs in fstab with options
like = (--disable-direct-io-mode)?<br>
<br>
is this correct?<br>
<br>
fstab:<br>
/etc/glusterfs/mount-backup01-client_repl.vol /GFS/backup01
glusterfs defaults,--disable-direct-io-mode 0 0<br>
<br>
</blockquote>
<div><br>
</div>
<div>The above is not correct. The correct entry in /etc/fstab (as of
today)is </div>
<div><br>
</div>
<div>/etc/glusterfs/mount-backup01-client_repl.vol /GFS/backup01
glusterfs defaults,direct-io-mode=disable 0 0</div>
<div><br>
</div>
<div>Regards,</div>
<div>Amar</div>
<div><br>
</div>
</div>
</blockquote>
<br>
Amar's suggestion is good if you have the vol definitions on the
client. We have 2 bricks and lots of clients, so it's more convenient
to keep the vol config on the bricks. The fstab entry can then be (in
our case)<br>
<br>
<tt>brick.my.domain:data_scripts /data/scripts glusterfs
disable-direct-io-mode,noatime 0 0<br>
</tt><br>
[aside: We also use dynamic dns to keep "brick.my.domain" up to date.]<br>
<br>
In /etc/glusterfs/glusterfsd.vol have something like<br>
<br>
<tt>volume dir_data_scripts<br>
type storage/posix<br>
option directory /gfs/data/scripts/export<br>
end-volume<br>
<br>
volume lock_data_scripts<br>
type features/locks<br>
subvolumes dir_data_scripts<br>
end-volume<br>
<br>
volume export_data_scripts<br>
type performance/io-threads<br>
option thread-count 128 # default is 1<br>
subvolumes lock_data_scripts<br>
end-volume<br>
<br>
volume server-tcp<br>
type protocol/server<br>
option transport-type tcp<br>
option transport.socket.nodelay on<br>
option auth.addr.export_data_scripts.allow *<br>
option volume-filename.data_scripts /etc/glusterfs/data_scripts.vol<br>
subvolumes export_data_scripts<br>
end-volume</tt><br>
<br>
We then put our client vol config in the file
/etc/glusterfs/data_scripts.vol on the bricks.<br>
<br>
Ian<br>
<br>
</body>
</html>