Aerospike service cold start failed

My aerospike service cold start failed, with the following logging:

Nov 03 2019 15:48:25 GMT+0800: INFO (config): (cfg.c:4010) node-id bb918f461b92600
Nov 03 2019 15:48:25 GMT+0800: INFO (namespace): (namespace_ce.c:87) {serve_ssd} beginning cold start
Nov 03 2019 15:48:25 GMT+0800: INFO (drv_ssd): (drv_ssd.c:3402) opened device /dev/sdb: usable size 999653638144, io-min-size 512
Nov 03 2019 15:48:25 GMT+0800: INFO (hardware): (hardware.c:2674) set scheduler for /dev/sdb to noop
Nov 03 2019 15:48:25 GMT+0800: INFO (drv_ssd): (drv_ssd.c:3316) usable device size must be header size 8388608 + multiple of 131072, rounding down
Nov 03 2019 15:48:25 GMT+0800: FAILED ASSERTION (drv_ssd): (drv_ssd.c:3352) /dev/sdc1: read failed at all sizes from 512 to 4096 bytes
Nov 03 2019 15:48:25 GMT+0800: WARNING (as): (signal.c:209) SIGUSR1 received, aborting Aerospike Community Edition build 4.3.1.4 os el7
Nov 03 2019 15:48:25 GMT+0800: WARNING (as): (signal.c:211) stacktrace: registers: rax 0000000000000000 rbx 0000000002165cf0 rcx ffffffffffffffff rdx 000000000000000a rsi 0000000000003a47 rdi             0000000000003a47 rbp 00007ffd36235410 rsp 00007ffd36234ef8 r8 0000000000000000 r9 0000000000000086 r10 00007ffd36234ac0 r11 0000000000000206 r12 0000000000000001 r13 0000000000000000 r14 0000000000000012 r15 0000000000000087 rip 00007f7dd933849b
Nov 03 2019 15:48:25 GMT+0800: WARNING (as): (signal.c:211) stacktrace: found 10 frames: 0x490a20 0x7f7dd93385d0 0x7f7dd933849b 0x52f43b 0x511213 0x511cbe 0x5076fa 0x440570 0x7f7dd813d3d5 0x441017 offset 0x400000
Nov 03 2019 15:48:25 GMT+0800: WARNING (as): (signal.c:211) stacktrace: frame 0: /usr/bin/asd(as_sig_handle_usr1+0x10e) [0x490a20]
Nov 03 2019 15:48:25 GMT+0800: WARNING (as): (signal.c:211) stacktrace: frame 1: /lib64/libpthread.so.0(+0xf5d0) [0x7f7dd93385d0]
Nov 03 2019 15:48:25 GMT+0800: WARNING (as): (signal.c:211) stacktrace: frame 2: /lib64/libpthread.so.0(raise+0x2b) [0x7f7dd933849b]
Nov 03 2019 15:48:25 GMT+0800: WARNING (as): (signal.c:211) stacktrace: frame 3: /usr/bin/asd(cf_fault_event+0x1f0) [0x52f43b]
Nov 03 2019 15:48:25 GMT+0800: WARNING (as): (signal.c:211) stacktrace: frame 4: /usr/bin/asd(ssd_init_devices+0x2b9) [0x511213]
Nov 03 2019 15:48:25 GMT+0800: WARNING (as): (signal.c:211) stacktrace: frame 5: /usr/bin/asd(as_storage_namespace_init_ssd+0x2a) [0x511cbe]
Nov 03 2019 15:48:25 GMT+0800: WARNING (as): (signal.c:211) stacktrace: frame 6: /usr/bin/asd(as_storage_init+0x2a) [0x5076fa]
Nov 03 2019 15:48:25 GMT+0800: WARNING (as): (signal.c:211) stacktrace: frame 7: /usr/bin/asd(main+0x2d0) [0x440570]
Nov 03 2019 15:48:25 GMT+0800: WARNING (as): (signal.c:211) stacktrace: frame 8: /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f7dd813d3d5]
Nov 03 2019 15:48:25 GMT+0800: WARNING (as): (signal.c:211) stacktrace: frame 9: /usr/bin/asd() [0x441017]

Could some give me some help? Thank you.

Does that device/partition (/dev/sdc1) exist? Is it healthy?

Assuming the device exists, could you run:

cat /sys/block/sdc1/queue/minimum_io_size

Thanks for reply. The reason has been found that the device was broken down.

Alb0t via Aerospike aerospike@discoursemail.com 于2019年11月4日周一 上午5:50写道:

1 Like
© 2015 Copyright Aerospike, Inc. | All rights reserved. Creators of the Aerospike Database.