Bug 763576 (GLUSTER-1844) - iozone with add-brick,remove-brick loop
Summary: iozone with add-brick,remove-brick loop
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-1844
Product: GlusterFS
Classification: Community
Component: nfs
Version: 3.1-alpha
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Shehjar Tikoo
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-07 07:22 UTC by Lakshmipathi G
Modified: 2015-12-01 16:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTNR
Mount Type: nfs
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Lakshmipathi G 2010-10-07 04:30:39 UTC
nfs log moved to /share/tickets/1844

Comment 1 Lakshmipathi G 2010-10-07 07:22:16 UTC
running qa41 with 2 dht server and 20 clients .all clients running iozone.
started single add-brick ,remove-brick in loop. after some time all clients iozone terminated with following message.nfs log file available at : 10.194.35.246/root

client mount point didn't hang - its working.

dmesg o/p:
============
eth0: no IPv6 routers present
nfs: server 10.194.35.246 not responding, still trying
nfs: server 10.194.35.246 OK
nfs: server 10.194.35.246 not responding, still trying
nfs: server 10.194.35.246 OK
============
iozone o/p:
===
            4096     128 1076460 1123095  1355368  1671214 1720356 1157693 1334228  1233695  1290120  1062238  1124366 1363935  1325978
            4096     256 1091662 1156441  1308224  1435192 1603122 1130269 1324714  1238965  1805137  1120643  1151836  177408  1569933
            4096     512 1083302 1163937  1331594  1568724 1703133  160401 1373156  1239706  1783196   848899   917355 1348706  1332050
            4096    1024 1066130 1157683  1355342  1481412 1554479 1161673 1368045  1214706  1701781   822838  1057853 1355842  1451955
            4096    2048fsync: Stale NFS file handle

iozone: interrupted

exiting iozone
=========

Comment 2 Shehjar Tikoo 2010-11-16 02:32:43 UTC
Removing a brick for distributed-only config is expected to cause an ESTALE for files that were on the removed brick. Closing...


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