summaryrefslogtreecommitdiffstats
path: root/xlators
Commit message (Collapse)AuthorAgeFilesLines
* cluster/afr: Perform conservative merge on dir with xattr split-brainv3.2.6p3Pranith Kumar K2012-03-143-10/+60
| | | | | | | | | Change-Id: I314cf7bbc8a451e42b6addf367f55e431ab0a85c BUG: 802637 Signed-off-by: Pranith Kumar K <pranithk@gluster.com> Reviewed-on: http://review.gluster.com/2945 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* cluster/afr: Handle files w.o. xattrs and size mismatch.v3.2.6p2Pranith Kumar K2012-03-132-10/+44
| | | | | | | | | Change-Id: I31458538c738c85a026994584c937c99538fe069 BUG: 802637 Signed-off-by: Pranith Kumar K <pranithk@gluster.com> Reviewed-on: http://review.gluster.com/2932 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* cluster/afr: Mark zero size file as sink in absense of xattrs.Pranith Kumar K2012-03-132-2/+53
| | | | | | | | | Change-Id: Ic9381f9caa7021a629afb7401e51a29686880bfe BUG: 802637 Signed-off-by: Pranith Kumar K <pranithk@gluster.com> Reviewed-on: http://review.gluster.com/2931 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* replicate: backport of 0783ca994d9ea95fd9ab3dd95d6407918f19f255Anand Avati2012-03-124-45/+30
| | | | | | | | | | | This is a backport of patch 0783ca994d9ea95fd9ab3dd95d6407918f19f255 which is a fix for bug 798874 Change-Id: I0edac430b2f22dce121ff4889b563cbef14b09cd BUG: 798874 Reviewed-on: http://review.gluster.com/2928 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Anand Avati <avati@redhat.com>
* cluster/afr: Handle split-brain/all-fool xattrs for directoryPranith Kumar K2012-03-126-176/+158
| | | | | | | | | | | | In case of split-brain/all-fool xattrs perform conservative merge. Don't treat ignorant subvol as fool. Change-Id: I3044d388d816d79268fec170d202ef23e7d5bf1c BUG: 765528 Signed-off-by: Pranith Kumar K <pranithk@gluster.com> Reviewed-on: http://review.gluster.com/2674 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Anand Avati <avati@redhat.com>
* geo-rep / gsyncd: fix cleanup of temporary mountsv3.2.6qa6v3.2.6Csaba Henk2012-03-091-13/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "finally" clause that was meant to cleanup after the temp mount has not covered the case of getting signalled (eg. by monitor, upon worker timing out). So here we "outsource" the cleanup to an ephemeral child process. Child calls setsid(2) so it won't be bothered by internal process management. We use a pipe in between worker and the cleanup child; when child sees the worker end getting closed, it performs the cleanup. Worker end can get closed either because worker closes it (normal case), or because worker has terminated (faulty case) -- thus as bonus, we get a nice uniform handling with no need to differentiate between normal and faulty cases. The faulty case that was seen IRL -- ie., users of maintainance mounts hang in chdir(2) to mount point -- can be simulated for testing purposes by applying the following patch: diff --git a/xlators/mount/fuse/src/fuse-bridge.c b/xlators/mount/fuse/src/fuse-bridge.c index acd3c68..1ce5dc1 100644 --- a/xlators/mount/fuse/src/fuse-bridge.c +++ b/xlators/mount/fuse/src/fuse-bridge.c @@ -2918,7 +2918,7 @@ fuse_init (xlator_t *this, fuse_in_header_t *finh, void *msg) if (fini->minor < 9) *priv->msg0_len_p = sizeof(*finh) + FUSE_COMPAT_WRITE_IN_SIZE; #endif - ret = send_fuse_obj (this, finh, &fino); + ret = priv->client_pid_set ? 0 : send_fuse_obj (this, finh, &fino); if (ret == 0) gf_log ("glusterfs-fuse", GF_LOG_INFO, "FUSE inited with protocol versions:" Change-Id: I1172bf16ac1006bad48958655572155820e5138d BUG: 786291 Signed-off-by: Csaba Henk <csaba@redhat.com> Reviewed-on: http://review.gluster.com/2908 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Venky Shankar <vshankar@redhat.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* gsyncd: geo-rep: Reduce excessive verbosity in loggingv3.2.6qa5Venky Shankar2012-03-061-8/+23
| | | | | | | | | | | | | Backport logging enhancement from master. This patch reduces per-second logging to per-minute logging during crawl Change-Id: Ie51207e6dd8a0257e59f90239cc6960803673223 BUG: 789078 Signed-off-by: Venky Shankar <vshankar@redhat.com> Reviewed-on: http://review.gluster.com/2879 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* xlator/lib: Drain out sent requests to avoid multiple STACK_UNWINDsVijay Bellur2012-03-062-14/+25
| | | | | | | | | Change-Id: Id48c468934ac64ec52e279ded8949c2a7a760598 BUG: 789078 Signed-off-by: Vijay Bellur <vijay@gluster.com> Reviewed-on: http://review.gluster.com/2871 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Venky Shankar <vshankar@redhat.com>
* Refactor xlator/lib for better readability & maintainability.v3.2.6qa4Vijay Bellur2012-03-022-202/+161
| | | | | | | | | Change-Id: I26532f1bf7cab58b5870a6117f2a62288ee1f23d BUG: 789078 Signed-off-by: Vijay Bellur <vijay@gluster.com> Reviewed-on: http://review.gluster.com/2859 Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com> Tested-by: Gluster Build System <jenkins@build.gluster.com>
* geo-rep / syncdaemon: make the timeout for establishing the connection to ↵Csaba Henk2012-03-012-1/+2
| | | | | | | | | | | | | | slave configurable It can be set through the connection-timeout tunable but we keep it hidden, intended as a workaround for some special scenarios not for general use. Change-Id: I31f9fa3873afa7babc2106ee34484123a01bdc57 BUG: 789078 Signed-off-by: Csaba Henk <csaba@redhat.com> Reviewed-on: http://review.gluster.com/2840 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* protocol/client: writev(): don't unwind if rpc_submit failedAmar Tumballi2012-02-201-2/+9
| | | | | | | | | | | | because rpc_submit does call 'cbk()' from inside if sending fails. no need to unwind in higher layers Change-Id: I08611ce742fba7032f68e3fe0f52a78a18a5714e Signed-off-by: Amar Tumballi <amar@gluster.com> BUG: 767359 Reviewed-on: http://review.gluster.com/2770 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* nfs/server: Add counters for hard resolutionv3.2.6qa3Vijay Bellur2012-02-143-4/+85
| | | | | | | | | Change-Id: Id7b26731b750b63d645222dde18cd9fe4ed54018 BUG: 785314 Signed-off-by: Vijay Bellur <vijay@gluster.com> Reviewed-on: http://review.gluster.com/2745 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Anand Avati <avati@redhat.com>
* support for nano second resolution for mtime,ctime,atime attributes.v3.2.6qa2krishna2012-02-082-22/+23
| | | | | | | | | Change-Id: Id5078f270d0fec280b53d4aa7b16bbaf42a2df05 BUG: 784095 Signed-off-by: krishna <ksriniva@redhat.com> Reviewed-on: http://review.gluster.com/2729 Reviewed-by: Anand Avati <avati@gluster.com> Tested-by: Gluster Build System <jenkins@build.gluster.com>
* Fixes bug-765574, failure to build from hardened sourceLouis Zuckerman2012-01-261-2/+2
| | | | | | | | | | | | | | | | | | | | | | | Glusterfs 3.2.5 failed to build on Debian which prevented the Debian project from updating their package to the latest release version. There were two changes needed, in both cases just adding a printf format string argument to a call to gf_log. The compiler error was that the argument was neither a string literal nor a format string. It was instead a pointer to a string. The obvious solution was to add a format argument of "%s" before the string pointer argument. This has been tested successfully on Debian Sid. Change-Id: I62c8a46938184c8a37224c2481bd1de00369ab19 Signed-off-by: louis zuckerman <glusterbugs@louiszuckerman.com> Reviewed-on: http://review.gluster.com/2598 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Kaleb KEITHLEY <kkeithle@redhat.com> Reviewed-by: Amar Tumballi <amar@gluster.com>
* mgmt/glusterd: do not assert if op_ctx is NULLRaghavendra Bhat2012-01-241-1/+0
| | | | | | | | | | | | | | In glusterd_op_send_cli_response we are asserting if op_ctx is NULL. But in handler functions of different ops, we are sending op_ctx NULL which is valid, but still glusterd will assert. Change-Id: I37824c694d14e87a234389d639dfb000592f9513 BUG: 783913 Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com> Reviewed-on: http://review.gluster.com/2678 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Krishnan Parthasarathi <kp@gluster.com> Reviewed-by: Anand Avati <avati@gluster.com>
* cluster/dht: Exit clean when assert_no_child_down is enabledVijay Bellur2012-01-241-1/+2
| | | | | | | | | Change-Id: If90b1080edcf3792f8590492b585a6dd48fac18e BUG: 783249 Signed-off-by: Vijay Bellur <vijay@gluster.com> Reviewed-on: http://review.gluster.com/2682 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Anand Avati <avati@gluster.com>
* features/marker: xtime should not be updated for modifications done by ↵Junaid2012-01-241-1/+7
| | | | | | | | | | | special client. Change-Id: I4b34d449b3ab08e2189fe1ff088299617b640206 BUG: 769494 Signed-off-by: Junaid <junaid@redhat.com> Reviewed-on: http://review.gluster.com/2564 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Csaba Henk <csaba@redhat.com>
* performance/io-cache: if the reconfigure option given is wrong, then unlock ↵Raghavendra Bhat2012-01-191-9/+10
| | | | | | | | | | | | | | | | and return In io-cache reconfigure we take the lock on ioc_table_t, and then get the options from the dict. If some value of some option given is wrong, we are returning without unlocking, leading to the hang. Change-Id: I5b3ebf0a8e9e2470d240b503167ff1731ff1b613 BUG: 782286 Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com> Reviewed-on: http://review.gluster.com/2649 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Harshavardhana <fharshav@redhat.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* cluster/stripe: Fix block size reported in pathinfo xattrVenky Shankar2012-01-031-16/+54
| | | | | | | | | | | | | | | | Block size (or stripe size) is reported when request is made for pathinfo xattr (trusted.glusterfs.pathinfo) for a striped volume. When the block size is changed, the new block size is reported for files created with older block size. This can be confusing ( or even erroneous ) for applications relying on pathinfo xattr to find chunks in backend. Change-Id: I79cb6721bbd33f44c3fada4dd52e459d2c128e24 BUG: 766530 Signed-off-by: Venky Shankar <vshankar@redhat.com> Reviewed-on: http://review.gluster.com/2549 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Shishir Gowda <shishirng@gluster.com>
* cluster/stripe: copy the gfid from the dentry structure to locshishir gowda2012-01-031-0/+2
| | | | | | | | | | | | | | | | In stripe_readdirp_cbk we used to send stat call on each of the entry we have got from readdirp, by creating a new inode (but without setting the gfid in loc). Protocol/client asserts if it cannot find gfid in either loc or loc->inode. This patch copies the gfid of the entry from the stat structure to loc. Change-Id: I3f124fb816fc6e3f9239a24fc657b1dbee34d3a2 BUG: 768840 Signed-off-by: shishir gowda <shishirng@gluster.com> Signed-off-by: Raghavendra Bhat <raghavendrabhat@gluster.com> Reviewed-on: http://review.gluster.com/2544 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* Cluster/stripe setattr: Wind only to first_child for special filesshishir gowda2012-01-031-1/+9
| | | | | | | | | Change-Id: Ia60207199ee702f22222b67a1f1d62b8093e871c BUG: 765539 Signed-off-by: shishir gowda <shishirng@gluster.com> Reviewed-on: http://review.gluster.com/723 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* storage/posix: posix getxattr log enhancementRajesh Amaravathi2011-11-301-4/+4
| | | | | | | | | | | | | | Now the key is logged with getxattr failure. BUG: 3283 Change-Id: Idc09b26c9196dded314df78ce3c765573160452b Reviewed-on: http://review.gluster.com/373 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Anand Avati <avati@gluster.com> Reviewed-on: http://review.gluster.com/755 Reviewed-by: Harshavardhana <fharshav@redhat.com> Tested-by: Harshavardhana <fharshav@redhat.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* features/marker-quota: Use stack_wind_cookie in place of stack_wind to ↵v3.2.5qa9v3.2.5Junaid2011-11-111-11/+12
| | | | | | | | | | | | | preserve the cookie value. In marker_rename, some of the call back functions make use of cookies sent by the calling functions. In case of stack_wind the frame->cookie is over written with the address of new frame. Change-Id: I8ec98f3305700e2c3295a10dff159ca6a19a380a BUG: 3808 Reviewed-on: http://review.gluster.com/717 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* cluster/afr: honor the xattr set by data-self-healPranith Kumar K2011-11-112-1/+4
| | | | | | | | Change-Id: I2b8c3a2d7771463ef94892f2a78fc464aba703ee BUG: 3805 Reviewed-on: http://review.gluster.com/708 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* cluster/distribute: Trigger selfheal only if rmdir succeeded onceshishir gowda2011-11-112-3/+7
| | | | | | | | | | | A EACCES error also should not trigger a selfheal. Only if rmdir succeeded on any subvol, a selfheal should be triggered Change-Id: I1dd39db830e9396b1dc6d6edbaa6de6ea83e9070 BUG: 3786 Reviewed-on: http://review.gluster.com/715 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Amar Tumballi <amar@gluster.com>
* afr: Fixed backgroundness detection in self-heal algo.Krishnan Parthasarathi2011-11-101-0/+1
| | | | | | | | Change-Id: I9888d8a0b86fdaf6589885766f2de7222d8c8ba2 BUG: 3802 Reviewed-on: http://review.gluster.com/705 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
* cluster/distribute lookup: Request layout info for dir'sv3.2.5qa8shishir gowda2011-11-101-6/+6
| | | | | | | | Change-Id: I17e40beb2c6e77a802fb987bed6f0e4be8010ef6 BUG: 3803 Reviewed-on: http://review.gluster.com/707 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Amar Tumballi <amar@gluster.com>
* cluster/afr: Handle split-brain/all-fool xattrs for directoryv3.2.5qa7Pranith Kumar K2011-11-095-35/+67
| | | | | | | | Change-Id: I058ed91494e1a9bbcf5e6e6c49e8ee4f7e014e23 BUG: 3796 Reviewed-on: http://review.gluster.com/695 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Anand Avati <avati@gluster.com>
* cluster/distribute stat: Take ref on inode before to prevent crash.shishir gowda2011-11-091-16/+21
| | | | | | | | | | | | | | | | Possible situation is a forget call which unref's the inode, and the layout gets freed before we access it in stat. By taking a ref before we call ctx get, the layout is going to be persistent till we unref it. Also use local call_cnt var instead of layout->cnt when wind is involved Change-Id: Ie04a7afd9e2c89cc14c08dd923d06c5f0193beb8 BUG: 3730 Reviewed-on: http://review.gluster.com/687 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Amar Tumballi <amar@gluster.com>
* cluster/distribute lookup: send revalidate calls to all subvols for directoriesshishir gowda2011-11-091-0/+11
| | | | | | | | | | | | | | If mkdir fails on a subvolume, layout is set taking into account only the subvols where it was successful. stat does not trigger selfheal, as its layout based. Revalidate on directories needs to be sent to all subvols, to fix the error, and not just on the layout. Change-Id: Ia3ce2e5a042b2d55cddd7bd8cf31a94de6023234 BUG: 3793 Reviewed-on: http://review.gluster.com/688 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Amar Tumballi <amar@gluster.com>
* stripe read: Wipe stat in reply to prevent truncated error.shishir gowda2011-11-082-1/+2
| | | | | | | | | | | | | | If the read request, does not fall to the subvolume with the largest file size set, then we never return the correct size. This leads to clients seeing a truncated file error. The work around is to wipe stat being returned as part of read call. Change-Id: I4e76d09d7919fd0be616fe140e08f89a0dbcc444 BUG: 3774 Reviewed-on: http://review.gluster.com/682 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Amar Tumballi <amar@gluster.com>
* cluster/replicate: no more 'itransform' required for inode numbersAmar Tumballi2011-11-085-123/+0
| | | | | | | | | | as posix layer itself sends inode numbers based on gfid now Change-Id: I184d4598cf541eadb0471c39e598f14d6ac9390a BUG: 3042 Reviewed-on: http://review.gluster.com/632 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* cluster/afr: Handle absence of gfid in lookupv3.2.5qa6Pranith Kumar K2011-11-051-3/+15
| | | | | | | | Change-Id: I57fe8db82425a064ca01b23a47baca297c67560c BUG: 3783 Reviewed-on: http://review.gluster.com/676 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* cluster/afr: unwind instead of returning directly if no open is required on ↵v3.2.5qa5Raghavendra Bhat2011-11-041-0/+1
| | | | | | | | | | | | | | | any child Currently if no open is required on any child of replicate, we are returning directly instead of unwinding and returning. This is leading to the frame loss, which results in application hang. Unwind and then return if no open is to be done on any child. Change-Id: Ib59535b63751d9e98a4ceca39b4b73b14d850680 BUG: 3443 Reviewed-on: http://review.gluster.com/674 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* dht,afr: Fixed gfid problemsPranith Kumar K2011-11-046-50/+53
| | | | | | | | | | | *) removed uuid_generate usage in pump and afr *) filled the gfids for the fops which were sending no gfid in loc Change-Id: Id6780da76c3ae18ae5130368b687ea026e338ac0 BUG: 3760 Reviewed-on: http://review.gluster.com/673 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* fuse resolve: send mapping 'gfid' in lookup for deep path resolve along with ↵Amar Tumballi2011-11-042-1/+26
| | | | | | | | | | | | | inode without which, the 1:1 mapping of inode from old graph to new graph is not complete Change-Id: Idea14bc65ff74aa13fc53ebe2caa50410ccefc44 BUG: 3770 Reviewed-on: http://review.gluster.com/658 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* nfs: do not return -1 (error), if the transmission buffer list is emptyRaghavendra Bhat2011-11-041-0/+7
| | | | | | | | | | | | | | In the rpc implementation of nfs suppose the transmission buffer list is empty for the nfs server, -1 is being returned which is treated as an error and the socket fd is closed to handle it. Because of this the reply submission of the server will be failed. Thus if the transmission buffer list is empty error should not be returned. Change-Id: I42d0dada8fe0473daf4db085da10681d4926e1ae BUG: 3765 Reviewed-on: http://review.gluster.com/671 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* cli: add geo-replication log-rotate commandVenky Shankar2011-11-048-19/+428
| | | | | | | | | | | | | | | | | | | | | | | | | Rotating geo-replication master/monitor log files from cli. On invocation, the log file for a given master-slave session is backed up with the current timestamp suffixed to the file name and signal is sent to gsyncd to start logging to a new log file. Sample commands: * Rotate log file for this <master>:<slave> session: gluster volume geo-replication <master> <slave> log-rotate * Rotate log files for all session for master volume <master> gluster volume geo-replication <master> log-rotate * Rotate log files for all sessions: gluster volume geo-replication log-rotate Change-Id: If801743e9f37bd282e68d262203141626ce77e55 BUG: 3519 Reviewed-on: http://review.gluster.com/653 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Csaba Henk <csaba@gluster.com>
* performance/write-behind: queue setattr fop with writes always.Raghavendra G2011-11-031-8/+1
| | | | | | | | | | | | stat returned in setattr_cbk can be cached by the kernel. Hence it is always necessary that we return correct stat, which implies that setattr should not be out of order with respect to write fops. Change-Id: Iaac1c79545760ac77ba3eae1ac2fee9f4e446fb9 BUG: 3711 Reviewed-on: http://review.gluster.com/665 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Anand Avati <avati@gluster.com>
* stripe readv_cbk: Propogate the correct size and blk cnt in stbufshishir gowda2011-11-031-0/+5
| | | | | | | | | | | | | | | We were passing the stbuf returned by the first child/index, which can be different to the size/blocks returned by stat. This led to applications viewing the file as being truncated. The stbuf size needs to be the largest of all results, and blocks the aggregation from all subvolumes. (similar to stat) Change-Id: I0782f2d0d48b53c5c507a2b1fc62a6132a31ce12 BUG: 3774 Reviewed-on: http://review.gluster.com/664 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Amar Tumballi <amar@gluster.com>
* glusterd rebalance: fail rebalance command on non-distribute volumesAmar Tumballi2011-11-031-0/+11
| | | | | | | | Change-Id: Id8cf3cbc8297b5f24f67c152d789b7c2ac299ccc BUG: 3729 Reviewed-on: http://review.gluster.com/652 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* storage/posix: assign ino as -1 if gfid is missingPranith Kumar K2011-11-031-8/+14
| | | | | | | | | Change-Id: Ib99f751d9404d9369944475bb0c70ec001857c94 BUG: 3767 Reviewed-on: http://review.gluster.com/661 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Amar Tumballi <amar@gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* cluster/dht: set gfid in lookup locPranith Kumar K2011-11-031-0/+2
| | | | | | | | Change-Id: Ic7a7b344bc62bf4c78e092c34c4c9cb3e0ba6cdc BUG: 3770 Reviewed-on: http://review.gluster.com/660 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Amar Tumballi <amar@gluster.com>
* cluster/afr: Modify finding gfid in lookup fopPranith Kumar K2011-11-031-3/+8
| | | | | | | | | Change-Id: I1d3b2028f1db7db32266827bd0ba9b2a73474e3e BUG: 3770 Reviewed-on: http://review.gluster.com/659 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Amar Tumballi <amar@gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* cluster/afr : Remove wrong log message in afr-open.cKaushal M2011-11-031-7/+0
| | | | | | | | | | Removes a wrong and unneeded log message in afr-open.c Change-Id: I682c9e1281867e6ccbed7099268e4015f9783ccd BUG: 3443 Reviewed-on: http://review.gluster.com/648 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
* cluster/afr : Fix self-heal of special filesKaushal M2011-10-313-11/+37
| | | | | | | | | | | | | | | | Fixes self-heal of special files like device files, fifo files, socket files etc. Does it by doing the following: * Prevent setting of pending data xattr on a special file during entry self-heal when a new file is created. * Allow data self-heal to be started on all file types other than directories. During data self-heal, for special files just erase pending xattrs, if those xattrs were set by previous releases of glusterfs. Change-Id: I1a36670b7287292d579b53852e25cdd452d55605 BUG: 3525 Reviewed-on: http://review.gluster.com/647 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Pranith Kumar Karampuri <pranithk@gluster.com>
* Move some of the messages to log level `TRACE'.Sachidananda Urs2011-10-304-8/+8
| | | | | | | | Change-Id: I41e6f39c5d0621942a310f550250034fd520ec76 BUG: 3761 Reviewed-on: http://review.gluster.com/644 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Amar Tumballi <amar@gluster.com>
* glusterd: Fixed volume profile's "are all bricks down?" algo.Krishnan Parthasarathi2011-10-281-1/+9
| | | | | | | | | | | | "count" key is not set if no brick in the volume (located across peers) is running. Sending "count" even when zero bricks are running from originator glusterd to client, simplifies "are all bricks down?" algo. Change-Id: I3a8db48c4c61cd31ba96031638a3c3d26efd2887 BUG: 3553 Reviewed-on: http://review.gluster.com/641 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* protocol/client: print remote operation failure logs in error mode instead ↵v3.2.5qa4Raghavendra Bhat2011-10-281-24/+24
| | | | | | | | | | | if info Change-Id: Ic4cd16618925656a12049f28f9b30bcac2242d4b BUG: 2346 Reviewed-on: http://review.gluster.com/621 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Amar Tumballi <amar@gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
* glusterd: Removing delayed moving of op sm for stop vol/remove brick op.Krishnan Parthasarathi2011-10-284-60/+4
| | | | | | | | | | | | | Earlier we would wait until brick disconnect or 5s whichever was earlier, before we move op sm from brick op stage to commit stage. This involves a race where both the above mentioned events can happen 'concurrently' and result in double free of the event context. Change-Id: Ia369994448e71a052679d2373b8ab9177d56a541 BUG: 3700 Reviewed-on: http://review.gluster.com/626 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>