Test to verify whether the lock is being granted to two diff
clients at the same time.
- Take lock from client 1 => Lock is acquired
- Try taking lock from client 2
- Release lock from client1
- Take lock from client2
- Again try taking lock from client 1

Also, verifying the behaviour with eagerlock and other eagerlock
set of on and off.

Change-Id: Ie839f893f7a4f9b2c6fc9375cdf9ee8a27fad13b
Signed-off-by: Pranav <prprakas@redhat.com>

Steps-
1. Create a disperse volume and start it.
2. Set the eager lock option
3. mount the volume and create a file
4. Check the profile info of the volume for inodelk count.
5. check xattrs of the file for dirty bit.
6. Reset the eager lock option and check the attributes again.

Change-Id: I0ef1a0e89c1bc202e5df4022c6d98ad0de0c1a68
Signed-off-by: Sheetal <spamecha@redhat.com>

Added check to verify the behavior after bringing down the
smallest brick. The available volume size should not be
greater than the initial vol size

Test skipped due to bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1883429

Change-Id: I00c0310210f6fe218cedd23e055dfaec3632ec8d
Signed-off-by: Pranav <prprakas@redhat.com>

Reason : The cd will change the working directory to root
and renames and softlink creations for subsequent files will
fail as seen in the glusto logs.

Change-Id: I174ac11007dc301ba6ec8ccddaeb919a181b1c30
Signed-off-by: srijan-sivakumar <ssivakum@redhat.com>

Extending the existing validation by adding
node restart as a method to bring back
offline bricks along with exiting volume start
approach.

Change-Id: I1291b7d9b4a3c299859175b4cdcd2952339c48a4
Signed-off-by: Pranav <prprakas@redhat.com>

Test Steps:
1. Create a pure-ec volume (say 1x(4+2))
2. Mount volume on two clients
3. Create some files and dirs from both mnts
4. Add bricks in this case the (4+2) ie 6 bricks
5. Create a new dir(common_dir) and in that directory create a distinct
directory(using hostname as dirname) for each client and pump IOs
from the clients(dd)
6. While IOs are in progress replace any of the bricks
7. Check for errors if any collected after step 6

Change-Id: I3125fc5906b5d5e0bc40477e1ed88825f53fa758
Signed-off-by: Bala Konda Reddy M <bala12352@gmail.com>

Problem: Test is failing with below traceback
when ran with python3 as default.
`
Traceback (most recent call last):
  File "<string>", line 1, in <module>
TypeError: a bytes-like object is required, not 'str'
`
Solution:
Added ''.encode() which will fix the issue when ran
using both python2 and python3

Added a check for core file on the client node.

Change-Id: I8f800f5fad97c3b7591db79ea51203e5293a1f69
Signed-off-by: Bala Konda Reddy M <bala12352@gmail.com>

- Remove decimal before passing to `head` command
- Breakup sparsefile into chunks to ~half of brick size
- Whole test has to be skipped due to BZ #1339144

Change-Id: I7a9ae25798b442c74248954023dd821c3442f8f9
Signed-off-by: Leela Venkaiah G <lgangava@redhat.com>

Problem: Creating a third mount obj works for glusterfs
protocol but in future while running for nfs/cifs might
face complications and test might fail.

Solution: Skip test unless three clients are provided
Removing redundant logging and minor fixes.

Change-Id: Ie657975a46b6989cb9f057f5cc337333bbf1010d
Signed-off-by: Bala Konda Reddy M <bala12352@gmail.com>

Test steps:
1. Create a volume, start and mount it on a client
2. Bring down redundant bricks in the subvol
3. Create a file on the volume using "touch"
4. Truncate the file using "O_TRUNC"
5. Bring the brick online
6. Write data on the file and wait for heal completion
7. Check for crashes and coredumps

Change-Id: Ie02a56ab5180f6a88e4499c8cf6e5fe5019e8df1
Signed-off-by: Bala Konda Reddy M <bala12352@gmail.com>