aerospike/act

ACT cannot set the scheduler mode if the device is partitioned using fdisk

Closed this issue · 1 comments

Looks like a bug where ACT cannot set scheduler mode to noop if the device is a partition,

Would be nice if we can find the raw devicename in which the partition belongs and set the scheduler mode for that.

Example output of error:

Aerospike act - device IO test
Copyright 2011 by Aerospike. All rights reserved.

CIO CONFIGURATION
device-names: /dev/sde1
num-devices: 1
queue-per-device: no
num-queues: 2
threads-per-queue: 8
test-duration-sec: 86400
report-interval-sec: 1
read-reqs-per-sec: 2000
large-block-ops-per-sec: 24
read-req-num-512-blocks: 3
large-block-op-kbytes: 128
use-valloc: no
num-write-buffers: 1024
scheduler-mode: noop

ERROR: couldn't open /sys/block/sde1/queue/scheduler
/dev/sde1 size = 101146235904 bytes, 197551104 512-byte blocks, 771684 large blocks

Yes, I wrote code for this some time back (still have a local copy, but never checked in). It's a bit of a hack -- assumes certain partition naming convention -- but we can decide whether to use it or not.