Bug 999414 - cluster.nufa :- if RHSS has more than one brick/sub-vol and nufa is on , than any files created from that RHSS mount point are stored only on brick/sub-vol
Summary: cluster.nufa :- if RHSS has more than one brick/sub-vol and nufa is on , than...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterfs
Version: 2.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-21 09:45 UTC by Rachana Patel
Modified: 2015-11-27 10:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-27 10:49:53 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Rachana Patel 2013-08-21 09:45:22 UTC
Description of problem:
cluster.nufa :- if RHSS has more than one brick/sub-vol and nufa is on , than any files created from that RHSS mount points are stored only on brick/sub-vol

Version-Release number of selected component (if applicable):
3.4.0.20rhs-2.el6rhs.x86_64

How reproducible:
always

Steps to Reproduce:
1.create DHT volume having more than one brick on one RHSS node and turn on cluster.nufa; mount that volum eon same RHSS node

[root@DVM1 ~]# gluster v info nufa
 
Volume Name: nufa
Type: Distribute
Volume ID: ec850869-99e9-497c-b650-b5c1443acb3d
Status: Started
Number of Bricks: 3
Transport-type: tcp
Bricks:
Brick1: 10.70.37.128:/rhs/brick3/n1
Brick2: 10.70.37.128:/rhs/brick3/n2
Brick3: 10.70.37.192:/rhs/brick3/n1
Options Reconfigured:
cluster.nufa: on
[root@DVM1 ~]# mkdir /mnt/nufa
[root@DVM1 ~]# mount -t glusterfs 10.70.37.192:/nufa /mnt/nufa


2. create files from mount point
[root@DVM1 ~]# cd /mnt/nufa
[root@DVM1 nufa]# touch f{1..20}


3. check on all bricks that where files are actually stored
[root@DVM1 nufa]# ls -l /rhs/brick3/n1
total 0
-rw-r--r-- 2 root root 0 Aug 21 07:10 f1
-rw-r--r-- 2 root root 0 Aug 21 07:10 f10
-rw-r--r-- 2 root root 0 Aug 21 07:10 f11
-rw-r--r-- 2 root root 0 Aug 21 07:10 f12
-rw-r--r-- 2 root root 0 Aug 21 07:10 f13
-rw-r--r-- 2 root root 0 Aug 21 07:10 f14
-rw-r--r-- 2 root root 0 Aug 21 07:10 f15
-rw-r--r-- 2 root root 0 Aug 21 07:10 f16
-rw-r--r-- 2 root root 0 Aug 21 07:10 f17
-rw-r--r-- 2 root root 0 Aug 21 07:10 f18
-rw-r--r-- 2 root root 0 Aug 21 07:10 f19
-rw-r--r-- 2 root root 0 Aug 21 07:10 f2
-rw-r--r-- 2 root root 0 Aug 21 07:10 f20
-rw-r--r-- 2 root root 0 Aug 21 07:10 f3
-rw-r--r-- 2 root root 0 Aug 21 07:10 f4
-rw-r--r-- 2 root root 0 Aug 21 07:10 f5
-rw-r--r-- 2 root root 0 Aug 21 07:10 f6
-rw-r--r-- 2 root root 0 Aug 21 07:10 f7
-rw-r--r-- 2 root root 0 Aug 21 07:10 f8
-rw-r--r-- 2 root root 0 Aug 21 07:10 f9
[root@DVM1 nufa]# ls -l /rhs/brick3/n2
total 0
---------T 2 root root 0 Aug 21 07:10 f12
---------T 2 root root 0 Aug 21 07:10 f13
---------T 2 root root 0 Aug 21 07:10 f17
---------T 2 root root 0 Aug 21 07:10 f4
---------T 2 root root 0 Aug 21 07:10 f8


[root@DVM4 ~]# ls -l /rhs/brick3/n1
total 0
---------T 2 root root 0 Aug 21 07:10 f11
---------T 2 root root 0 Aug 21 07:10 f14
---------T 2 root root 0 Aug 21 07:10 f15
---------T 2 root root 0 Aug 21 07:10 f16
---------T 2 root root 0 Aug 21 07:10 f3
---------T 2 root root 0 Aug 21 07:10 f6
---------T 2 root root 0 Aug 21 07:10 f7
---------T 2 root root 0 Aug 21 07:10 f9

Actual results:
files are stored only on one brick

Expected results:
files should be distributed on all bricks which are present on that RHSS.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.