Bug 969403 - DHT - while renaming file, got 'Remote I/O error' (all bricks where up and peers are in connected state)
DHT - while renaming file, got 'Remote I/O error' (all bricks where up and pe...
Status: CLOSED DEFERRED
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: distribute (Show other bugs)
2.0
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Nithya Balachandran
Matt Zywusko
:
Depends On:
Blocks: 1286086
  Show dependency treegraph
 
Reported: 2013-05-31 07:23 EDT by Rachana Patel
Modified: 2015-11-27 05:42 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1286086 (view as bug list)
Environment:
Last Closed: 2015-11-27 05:41:19 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Rachana Patel 2013-05-31 07:23:22 EDT
Description of problem:
DHT - while renaming file, got 'Remote I/O error' (all bricks where up and peers are in connected state)

Version-Release number of selected component (if applicable):
3.3.0.10rhs-1.el6.x86_64

How reproducible:
not always

Steps to Reproduce:
1.had a peer of 3 cluster and DHt volume having 4 bricks. executed remove-brick start  on RHS server and from mount point executed rename operation for multiple files.


[root@rhsauto027 dist-nfs]# for i in {1..30}; do for j in {1..100}; do mv d$j/file$i d$j/d$j/file1new$i; done; mv f$i filenew$i ; done
...
mv: cannot stat `d99/file5': No such file or directory
mv: cannot stat `d100/file5': No such file or directory
mv: cannot stat `f5': No such file or directory
mv: cannot move `d1/file6' to `d1/d1/file1new6': Remote I/O error              <-----------------
...

[root@rhsauto027 dist-nfs]# ls -l d1/file6
-rw-r--r--. 1 root root 1048576 May 31  2013 d1/file6
[root@rhsauto027 dist-nfs]# ls -l d1/d1/file6
ls: cannot access d1/d1/file6: No such file or directory

Actual results:
got 'Remote I/O error' for one file. (all bricks where up and peers were in connected state)

Expected results:


Additional info:

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