Red Hat Bugzilla – Bug 848342
Dbench exit with "Bad file descriptor" if the graph-change happens
Last modified: 2014-08-24 20:49:43 EDT
+++ This bug was initially created as a clone of Bug #827405 +++
Description of problem:
Running dbench on geo-rep setup with master config distributed-replicate and slave config distributed-replicat and parallely quota was being set and unset in loop. Dbench exited with "Bad file descriptor"
100 686 4.19 MB/sec execute 174 sec latency 9912.135 ms
100 686 4.16 MB/sec execute 175 sec latency 10343.618 ms
 write failed on handle 10011 (Bad file descriptor)
Child failed with status 1
Version-Release number of selected component (if applicable):3.3.0qa45
Steps to Reproduce:
1.Create geo-rep setup with master as distributed-replicate and slave as distribute-replicate
2.Run dbench in the mount-point
3.enable and disable the quota in loop
Actual results:dbench exits with Bad file descriptor
Expected results:dbench should complete properly.
volume info of the master
Volume Name: master
Volume ID: be06889e-66e2-4398-98be-a904652c7a42
Number of Bricks: 2 x 2 = 4
--- Additional comment from firstname.lastname@example.org on 2012-06-01 07:37:49 EDT ---
Created attachment 588419 [details]
Client log file.
--- Additional comment from email@example.com on 2012-06-01 07:38:54 EDT ---
In the steps to reproduce,
step 2 and step 3 should be done in parallel.
--- Additional comment from firstname.lastname@example.org on 2012-07-11 07:02:11 EDT ---
reducing the priority to medium as 'quota set/unset' in loop is not a practical use case.
This bug is not seen in current master branch (which will get branched as RHS 2.1.0 soon). To consider it for fixing, want to make sure this bug still exists in RHS servers. If not reproduced, would like to close this.
with proper graph change this should be fixed... in upstream we do have support for it.. and need a round of check.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
For information on the advisory, and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.