glusterfs.git/xlators/mount/fuse/src/fuse-bridge.h, branch v3.1.1qa8

Copyright changes

2010-10-11T14:31:12+00:00

Signed-off-by: Vijay Bellur 
Signed-off-by: Vijay Bellur 

BUG: 971 (dynamic volume management)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

Change GNU GPL to GNU AGPL

2010-10-04T14:50:05+00:00

Signed-off-by: Pranith Kumar K 
Signed-off-by: Vijay Bellur 

BUG: 1388 ()
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1388

Add log-level option to command volume set

2010-10-04T14:05:39+00:00

log-level option to set brick's log-level
client-log-level to set client's log-level

Signed-off-by: shishir gowda 
Signed-off-by: Vijay Bellur 

BUG: 1789 (add log-level options to volume set)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1789

Changes to replace flock with gf_flock across GlusterFS.

2010-10-01T12:05:53+00:00

Signed-off-by: Pavan Vilas Sondur 
Signed-off-by: Vijay Bellur 

BUG: 865 (Add locks recovery support in GlusterFS)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=865

gfid: set request gfids for new entries in fuse

2010-09-04T08:45:29+00:00

Signed-off-by: Anand V. Avati 
Signed-off-by: Anand V. Avati 
Signed-off-by: Vijay Bellur 

BUG: 971 (dynamic volume management)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=971

Revert "fuse: introduce pre-test micro-framework, check for execve-over-direct-IO"

2010-09-03T09:49:30+00:00

This reverts commit 588d807bdcbf5ed4df4d903428ab701479e9f8ac.

fuse: introduce pre-test micro-framework, check for execve-over-direct-IO

2010-09-02T16:50:11+00:00

The presence of some potential FUSE features in the actual kernel-side FUSE
implementation we run on is not always straightforward. More precisely, it is
straightforward only if there is a dedicated feature flag or protocol revision
number. In the other cases we are left to clumsy and platform specific hacks
which wire in 3rd-party software revision numbers into our source... at least,
if we insist on sticking to (the otherwise venerable) KISS principle.

However, here we go for another route, loosely inspired by the way autotools
provide an abstraction layer for our build system over the gory details of
platform specific build environments.

At start time, we use a preliminary set of FUSE operations which overlay the
standard ones such that apart from the "usual stuff", they also present some
synthetic files to the FUSE client (kernel). Then we spawn some test programs
which perform the needed tests on these synthetic files to evaulate the FUSE
implementation in terms of the features in question. According to the result
of the test programs, we set the respective parameters of the fuse xlator;
when the testing phase is over, the FUSE operation set is replaced by the
standard one.

As of now, we use this approach to test whether execve(2) works with
direct I/O. If yes, and if glusterfs is used with --enable-direct-io-mode,
then we let direct I/O for files opened for reading; if no, then we restrict
direct I/O only to writing files.

Signed-off-by: Csaba Henk 
Signed-off-by: Vijay Bellur 

BUG: 801 (Direct io-mode support and related changes in caching translators.)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=801

check whether xlator is NULL in FUSE_FOP macro

2010-08-21T12:17:14+00:00

Signed-off-by: Raghavendra Bhat 
Signed-off-by: Anand V. Avati 

BUG: 1407 ()
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1407

logging enhancements

2010-08-12T07:45:48+00:00

* per translator loglevel introduced, if set, it will override process
  wide log level.
* with extended attribute 'trusted.glusterfs..set-log-level'
  with the value being '', one can change log level of particular
  translator.
* with extended attribute 'trusted.glusterfs.syslog' with the value
  '', one can enable disable syslog for gluster

Signed-off-by: Amar Tumballi 
Signed-off-by: Anand V. Avati 

BUG: 601 (Enable changing 'log-level' of GlusterFS process at runtime)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=601

fuse resolve related changes

2010-08-12T05:24:38+00:00

Now fuse is fully complaint with DVM, as even if there is a fop
request on inode belonging to old graph, it will be resolved
corresponding to new graph and operations will be performed wrt.
new graph, which makes DVM truely spontaneous.

Signed-off-by: Amar Tumballi 
Signed-off-by: Anand V. Avati 

BUG: 1240 (DVM: after graph change, inodes should resolve to new inode-table)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1240