Red Hat Bugzilla – Bug 820922
Replace-brick start results in iozone termination with error.
Last modified: 2015-11-03 18:04:25 EST
Description of problem:While running iozone , if replace-brick is started, the iozone exits with an error saying Error writing block 772, fd= 3 write: Transport endpoint is not connected iozone: interrupted exiting iozone Version-Release number of selected component (if applicable):3.3.0qa40 How reproducible: Always. Steps to Reproduce: 1.Create a distributed-stripe volume. 2.Run "iozone -a" on the mount-point 3.While its running, do replace-brick of the first sub-volume. Actual results: Expected results: Additional info:
Volume type such as stripe and distributed stripe, may fail operations on the mount point with EIO if the first subvolume is "down". During a replace-brick operation, src brick is stopped and restarted with pump xlator inserted into the server graph. During which operations running on the mount can fail. This is a known limitation of replace-brick with stripe, distributed stripe type volumes.