Hi Mark,
Try the latest giant branch. I believe we've fixed this with 7272bb8.
My test cluster is passing read tests now.
Mark
On 10/24/2014 05:45 PM, Mark Kirkwood wrote:
Interestingly, I first encountered this on (what I think is) 0.86
release (0.86-1precise). I wonder if you had a bigger rbd cache on the
release cluster you tested?
As mentioned in the same named thread on -users, disabling the rbd cache
stops the hang.
Regards
Mark
On 25/10/14 03:09, Mark Nelson wrote:
More info:
I went back and tested fio versions back to 2.1.10 and still encountered
the issue. I then went back and tested the v0.86 release versus giant
and was able to get through a 4MB read test without error. I suspect
this is not an fio problem. I'll try to narrow down the commit after
0.86 that is causing this.
Mark
On 10/24/2014 08:19 AM, Mark Nelson wrote:
FWIW we are seeing this at Redhat/Inktank with recent fio from master
and ceph giant branch as well.
Mark
On 10/24/2014 01:17 AM, Mark Kirkwood wrote:
On 24/10/14 18:35, Jens Axboe wrote:
CC'ing relevant parties, leaving email intact.
Note that the 'Killed' is because I killed the run - it hangs and
appears to be non interruptable. I missed that when pasting, sorry!
$ fio read-test.fio # attached
rbd_thread: (g=0): rw=read, bs=2M-2M/2M-2M/2M-2M, ioengine=rbd,
iodepth=32
fio-2.1.13-88-gb2ee7
Starting 1 process
rbd engine: RBD version: 0.1.8
Killed1 (f=1): [R(1)] [inf% done] [0KB/0KB/0KB /s] [0/0/0 iops] [eta
1158050441d:06h:59m:33s]
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe fio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html