glusterfs.git/tests/basic/volume-status.t, branch v7.1

tests: add .t file to increase cli code coverage

2019-04-24T14:04:35+00:00

updates: bz#1693692

Change-Id: I848e622d7b8562e864f0e208aafdc21d9cb757d3
Signed-off-by: Sanju Rakonde

tests: run nfs tests only if --enable-gnfs is provided

2019-01-24T15:18:00+00:00

Fixes: bz#1665358
Change-Id: Idbf88ec3ac683733b32c313377eeb72f2819bf0d
Signed-off-by: Amar Tumballi

stripe: remove the translator from build and glusterd

2018-10-31T02:24:49+00:00

Based on the proposal to remove few features as they are not
actively maintained [1], removing stripe translator from the
build. Also make sure there are no regression tests involving
stripe translator.

[1] https://lists.gluster.org/pipermail/gluster-users/2018-July/034400.html

Note that this patch aims at removing the translator from build, and
a followup patch is needed to remove the code from repository.

Updates: bz#1364707
Change-Id: I235b305338f138e29e9f30cba65bc0dadbebbbd5
Signed-off-by: Amar Tumballi

glusterd: volume inode/fd status broken with brick mux

2018-04-19T02:54:50+00:00

Problem:
The values for inode/fd was populated from the ctx received
from the server xlator.
Without brickmux, every brick from a volume belonged to a
single brick from the volume.
So searching the server and populating it worked.

With brickmux, a number of bricks can be confined to a single
process. These bricks can be from different volumes too (if
we use the max-bricks-per-process option).
If they are from different volumes, using the server xlator
to populate causes problem.

Fix:
Use the brick to validate and populate the inode/fd status.

Signed-off-by: hari gowtham 

Change-Id: I2543fa5397ea095f8338b518460037bba3dfdbfd
fixes: bz#1566067

Tests: disabling the check for volume client-list

2017-09-19T10:42:30+00:00

The client-list command is broken for brick-multiplexed.
Disabling it until the fix is in so that the regression test
can be resumed for the other test cases.

Change-Id: Idcb5a09db0eb46fbe71c215109b5c55924cc1209
BUG: 1492542
Signed-off-by: hari gowtham 
Reviewed-on: https://review.gluster.org/18308
Smoke: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Tested-by: Atin Mukherjee 
CentOS-regression: Gluster Build System

Command to identify client process

2017-09-06T11:52:40+00:00

command: gluster volume status  client-list

output:
Client connections for volume v1
Name                                                       count
-----                                                     ------
fuse                                                           2
tierd                                                          1

total clients for volume v1 : 3
-----------------------------------------------------------------

Client connections for volume v2
Name                                                       count
-----                                                     ------
tierd                                                          1
fuse.gsync                                                     1

total clients for volume v2 : 2
-----------------------------------------------------------------

Updates: #178
Change-Id: I0ff2579d6adf57cc0d3bd0161a2ec6ac6c4747c0
Signed-off-by: hari gowtham 
Reviewed-on: https://review.gluster.org/18095
Smoke: Gluster Build System 
Tested-by: hari gowtham 
CentOS-regression: Gluster Build System 
Reviewed-by: Atin Mukherjee

glusterd: default value of nfs.disable, change from false to true

2016-04-27T07:59:30+00:00

Next step in eventual deprecation of glusterfs nfs server in favor
of ganesha.nfsd.

Also replace several open-coded strings with constant.

Change-Id: If52f5e880191a14fd38e69b70a32b0300dd93a50
BUG: 1092414
Signed-off-by: Kaleb S KEITHLEY 
Reviewed-on: http://review.gluster.org/13738
NetBSD-regression: NetBSD Build System 
Smoke: Gluster Build System 
CentOS-regression: Gluster Build System 
Reviewed-by: Atin Mukherjee 
Tested-by: Atin Mukherjee 
Reviewed-by: Niels de Vos

glusterd: nfs,shd,quotad,snapd daemons refactoring

2015-02-20T12:04:08+00:00

This patch ports nfs, shd, quotad & snapd with the approach suggested in
http://www.gluster.org/pipermail/gluster-devel/2014-December/043180.html

Change-Id: I4ea5b38793f87fc85cc9d2cf873727351dedffd2
BUG: 1191486
Signed-off-by: Atin Mukherjee 
Signed-off-by:  Krishnan Parthasarathi 
Reviewed-on: http://review.gluster.org/9428
Tested-by: Gluster Build System 
Reviewed-by: Anand Nekkunti

gNFS : mount fails if connection to brick(s) is not established yet.

2014-10-31T08:14:03+00:00

       Connection between gluster-nfs and brick process requires
       time (especially for rdma).During that time when we try to
       mount using nfs ,it will fail saying that volume not found.
       So we need a check using 'is_nfs_export_available'before
       mounting to ensure volume is available.This patch will provide
       the check before nfs mount if it is not given in the test files

Change-Id: I242eb6e3118ebaca1df46314302a203a0c9738a8
BUG: 1158831
Signed-off-by: jiffin tony thottan 
Reviewed-on: http://review.gluster.org/9011
Reviewed-by: Meghana M 
Tested-by: Gluster Build System 
Reviewed-by: Niels de Vos

porting: various fixes regression tests OSX/FreeBSD

2014-08-29T16:13:02+00:00

- `wc -l` on OSX/FreeBSD adds spurious spaces, this clobbers
  up TAP output parsers - fix it.
- `umount -l` doesn't exist on OSX/FreeBSD use 'umount -f' if
   available.
- Add check for 'file' version, to handle mime type variations
  across versions
- Converge 'glusterfs --attribute-timeout=0 --entry-timeout=0'
  into '$GFS'
- Modify remaining 'mount -t nfs' to use 'mount_nfs'
- Update sha1sum for OSX to use 'openssl sha1'.

Change-Id: Id1012faa5d67a921513d220e7fa9cebafe830d34
BUG: 1131713
Signed-off-by: Harshavardhana 
Reviewed-on: http://review.gluster.org/8501
Tested-by: Gluster Build System 
Reviewed-by: Kaleb KEITHLEY