glusterfs.git/xlators, branch v3.0.0

Changed occurrences of Z Research to Gluster

2009-12-07T14:09:02+00:00

Signed-off-by: Vijay Bellur

resolver: include RESOLVE_EXACT type for failure case when inode not found

2009-12-07T13:31:40+00:00

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

BUG: 315 (generation number support)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=315

cluster/afr: Sync the parent directory's mtime during missing entries self-heal.

2009-12-07T13:31:37+00:00

Signed-off-by: Vikas Gorur 
Signed-off-by: Anand V. Avati 

BUG: 137 (Parent directory mtime not reset after a create in self-heal)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=137

cluster/afr: Don't do entry self-heal in the background.

2009-12-07T13:31:32+00:00

Signed-off-by: Vikas Gorur 
Signed-off-by: Anand V. Avati 

BUG: 326 ([2.0.8rc9] Spurious self-heal)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=326

cluster/afr: Hold inode lock on 0-infinity for a flush transaction.

2009-12-07T13:31:29+00:00

Signed-off-by: Vikas Gorur 
Signed-off-by: Anand V. Avati 

BUG: 326 ([2.0.8rc9] Spurious self-heal)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=326

fix typo in 76d6f3fbe

2009-12-07T06:16:58+00:00

Signed-off-by: Csaba Henk 
Signed-off-by: Anand V. Avati 

BUG: 336 (Use lock owner field from fuse in locks)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

Save st_dev properly in stbuf.st_dev from the same subvolume.

2009-12-07T06:16:54+00:00

Signed-off-by: Harshavardhana 
Signed-off-by: Anand V. Avati 

BUG: 433 (Posix conformance test failed on 3.0.0pre2 (Dec 3) release)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=433

Revert "performance/write-behind: Changed default value of option disable-till to 0"

2009-12-06T21:51:03+00:00

This reverts commit e6c35f74ff4a204cf016ebf201a2630b331f9434.

This commit is found to trigger spurious self heal by causing flush and writev to get
reordered. Reverting as a workaround.

fuse-bridge: set lk_owner to -1 for release forged flush.

2009-12-06T20:39:19+00:00

Server would interpret 0 as a sign of us getting disconnected.

Signed-off-by: Csaba Henk 
Signed-off-by: Anand V. Avati 

BUG: 336 (Use lock owner field from fuse in locks)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336

fuse-bridge: make use of lock owner data in a protocol adherent way.

2009-12-06T20:39:15+00:00

No need for pid fallback, for those cases where we use it,
it's always available.

It appears conditionally in read/write/truncate (related to mandatory
locking). There just get it for demonstrative purposes.

Discard it from release, there locking data exists only as a
portability hack, no use of it on Linux.

Signed-off-by: Csaba Henk 
Signed-off-by: Anand V. Avati 

BUG: 336 (Use lock owner field from fuse in locks)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=336