glusterfs.git/libglusterfsclient, branch v2.0.5

libglusterfsclient: Avoid overwrite of inode found through ino number

2009-07-23T22:20:16+00:00

In libgf_client_loc_fill, there is a possibility that all
the ino, par and name are specified as non-NULL,non-zero args.

So if an inode is located in the itable using the ino and the
subsequent search for the inode using the par-ino and the file
name does not result in an inode being found, the current
code over-writes the inode that was found through the ino. The
correct behaviour is to stop further searches if inode
was already found using ino.

Signed-off-by: Anand V. Avati 

BUG: 161 (unfs3 crashes on link system call by fileop)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=161

libglusterfsclient: Fill new loc with target's ino on link

2009-07-23T22:20:12+00:00

In the loc_t of the link being created, we must fill in the inode
of the old/target loc since this is a link operation. The
inode_link to the new parent is called in libgf_client_link.

This fixes a crash while running fileop over a fully-loaded
dist-repl vol file.
Ref: Bugzilla 161

Signed-off-by: Anand V. Avati 

BUG: 161 (unfs3 crashes on link system call by fileop)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=161

libglusterfsclient: Fake a fsid for every VMP

2009-07-20T21:29:41+00:00

This is needed to work around the replicate behaviour of
possibly returning device number for the same file from

different subvolumes.

Signed-off-by: Anand V. Avati 

BUG: 148 (replicate: Returns st_dev from different subvols resulting in ESTALE thru unfs3booster)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=148

libglusterfsclient: Move DHT root-lookup workaround to init

2009-07-20T21:29:37+00:00

The workaround for the DHT requirement for a lookup on /
needs to be done only once when the xlator graph is inited.
Doing it on every path's lookup results in a major performance
penalty when using distribute subvolumes upwards of 16, as reported
by Avati.

Ref: bug 152

Signed-off-by: Anand V. Avati 

BUG: 152 (libglusterfsclient: DHT workaround is a major performance bottleneck)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=152

libglusterfsclient: Invalidate not update iattr cache on writev

2009-07-17T19:01:29+00:00

Signed-off-by: Anand V. Avati 

BUG: 149 (libglusterfsclient interacts incorrectly with write-behind on writev)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=149

libglusterfsclient: Update attr cache on read/write

2009-07-07T23:24:53+00:00

We werent updating the attr AKA stat cache on read and write
on files so every stat on the file before the timeout was returning
stale attr from the cache. Yuck!

This fixes it. Turns out there is a good aspect of unfs3's notoriety
when it comes to doing stat()s for every operation.

Signed-off-by: Anand V. Avati

libglusterfsclient: Use O_ACCMODE for access mode checks

2009-07-02T17:14:48+00:00

Ref: http://www.gnu.org/s/libc/manual/html_node/Access-Modes.html

Signed-off-by: Anand V. Avati

libglusterfsclient: Fix glusterfs_mount-vmp search deadlock

2009-06-30T22:24:53+00:00

It is possible that the only translator in the libglusterfsclient
tree is the posix. In that case, inside gluster_init, the graph
init routines will need to call lstat on the posix subdirectory.

Since even the glusterfs stack is running over booster, those
calls will also first require vmp searching. BUT, the vmp lock
is the same as the mount lock that was already taken when we entered
glusterfs_mount, so a deadlock occurs.

Signed-off-by: Anand V. Avati

libglusterfsclient: reset the vmplist and vmpentries to 0 in glusterfs_reset

2009-06-30T21:36:26+00:00

- Generally glusterfs_reset is called after fork in child to empty out
    vmplist.

Signed-off-by: Anand V. Avati

libglusterfsclient: implement glusterfs_fcntl.

2009-06-30T21:36:25+00:00

Signed-off-by: Anand V. Avati