glusterfs.git/xlators/cluster/dht/src/dht-diskusage.c, branch v3.3.0qa19

cluster/distribute: Add support for 'min-free-inodes' on each distribute subvolume.

2011-11-23T12:16:16+00:00

This change is required as increasingly large number of small files
would cause inodes to run out before they run out on available disk space.
It is highly necessary to support algorithmic checking of inodes too
just as we do for disk space.

Change-Id: I9b87405328d443825e239ee80ab664aceb50ee68
BUG: 3799
Signed-off-by: Harshavardhana 
Reviewed-on: http://review.gluster.com/730
Tested-by: Gluster Build System 
Reviewed-by: Jeff Darcy 
Reviewed-by: Amar Tumballi

Move some of the messages to log level `TRACE'.

2011-11-16T07:30:22+00:00

Change-Id: I46133b5e2218b9d810251b3dadadd8f157ab07d7
BUG: 3761
Reviewed-on: http://review.gluster.com/643
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

distribute rebalance: handle the open file migration

2011-09-13T06:57:38+00:00

Complexity involved: To migrate a file with open fd, we have to
notify the other client process which has the open fd, and make
sure the write()s happening on that fd is properly synced to the
migrated file. Once the migration is complete, the client
process which has open-fd should get notified and it should
start performing all the operations on the new subvolume,
instead of earlier cached volume.

How to solve the notification part:

We can overload the 'postbuf' attribute in the _cbk() function to
understand if a file is 'under-migration' or 'migration-complete'
state. (This will be something similar to deciding whether a file
is DHT-linkfile by its 'mode').

Overall change includes below mentioned major changes:

1. dht_linkfile is decided by only 2 factors (mode(01000),
   xattr(trusted.glusterfs.dht.linkto)), instead of earlier
   3 factors (size==0)

2. in linkfile self-heal part (in 'dht_lookup_everywhere_cbk()'),
   don't delete a linkfile if there is a open-fd on it. It means,
   there may be a migration in progress.

3. if a file's revalidate fails with ENOENT, it may be due to file
   migration, and hence need a lookup_everywhere()

4. There will be 2 phases of file-migration.

-> Phase 1: Migration in progress
   * The source data file will have SGID and STICKY bit set in its mode.
   * The source data file will have a 'linkto' xattr pointing the
     destination.
   * Destination file will have mode set to '01000', and 'linkto' xattr
     set to itself.

-> Phase 2: File migration Complete
   * The source data file will have mode '01000', and will be 'truncated'
     to size 0.
   * The destination file will have inherited mode from the source. (without
     sgid and sticky bit) and its 'linkto' attribute will be removed.

4. Changes in distribute to work smoothly with a file which is in migration /
   got migrated.

The 'fops' are divided into 3 categories, inode-read, inode-write and others.
inode-read fops need to handle only 'phase 2' notification, where as, the
inode-write fops need to handle both 'phase 1' and phase2. The inode-write
operations will be done on source file, and if any of 'file-migration' procedures
are detected in _cbk(), then the operations should be performed on the destination
too.

when a phase-2 is detected, then the inode-ctx itself should be changed to represent
a new layout.

With these changes, the open file migration will work smoothly with multiple clients.

Change-Id: I512408463814e650f34c62ed009bf2101d016fd6
BUG: 3071
Reviewed-on: http://review.gluster.com/209
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

Change Copyright current year

2011-08-10T17:57:19+00:00

Change-Id: I2d10f2be44f518f496427f257988f1858e888084
BUG: 3348
Reviewed-on: http://review.gluster.com/200
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

LICENSE: s/GNU Affero General Public/GNU General Public/

2011-08-06T13:33:52+00:00

Change-Id: I3914467611e573cccee0d22df93920cf1b2eb79f
BUG: 3348
Reviewed-on: http://review.gluster.com/182
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

dht disk usage: Correct free blk calculation

2011-07-07T11:45:29+00:00

Use f_bavial instead of f_bfree for %free calculation
This fixes mismatch of df output wrt backend and glusterfs

where: f_bfree = /* # free blocks */
       f_bavail; /* free blocks avail to non-superuser */

Signed-off-by: shishir gowda 
Signed-off-by: Anand Avati 

BUG: 3084 (Correcting percent calculation of disk space)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=3084

cluster/dht: log enhancements

2011-03-17T18:59:00+00:00

Signed-off-by: Shishir Gowda 
Signed-off-by: Amar Tumballi 
Signed-off-by: Vijay Bellur 

BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

cluster/dht: whitespace cleanup

2011-03-17T18:58:55+00:00

also fill tabs by spaces (untabify), and indent the code

Signed-off-by: Amar Tumballi 
Signed-off-by: Vijay Bellur 

BUG: 2346 (Log message enhancements in GlusterFS - phase 1)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2346

distribute: bring in statfs normalization

2010-10-27T07:47:59+00:00

We had normalization of statvfs structure in 'cluster/unify' translator,
with distribute, we had this section as 'TODO:'. Now, the same code is
migrated to distribute.

Thanks to  for sending the patches

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

BUG: 1035 (The distribute translator does not handle differently sized block sizes and/or fragment sizes)
URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=1035

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