read_ssd warnings in log


#1

Hi,

I have a cluster running on ec2 and I noticed that it’s logging the following errors:

Aug 14 2015 16:53:27 GMT: WARNING (drv_ssd): (drv_ssd.c::1171) {mydb} read_ssd: invalid rblock_id <Digest>:0x37b7c0bd3000f5964cf4a7e31e80e1c70a84c074
Aug 14 2015 16:53:27 GMT: WARNING (drv_ssd): (drv_ssd.c::1171) {mydb} read_ssd: invalid rblock_id <Digest>:0x37b7c0bd3000f5964cf4a7e31e80e1c70a84c074
Aug 14 2015 16:53:27 GMT: INFO (drv_ssd): (drv_ssd.c::1278) read_all: failed as_storage_record_read_ssd()
Aug 14 2015 16:53:29 GMT: WARNING (drv_ssd): (drv_ssd.c::1171) {mydb} read_ssd: invalid rblock_id <Digest>:0xa13c8854006e21cdad64ec58f6ac6b621a737c2e
Aug 14 2015 16:53:29 GMT: WARNING (drv_ssd): (drv_ssd.c::1171) {mydb} read_ssd: invalid rblock_id <Digest>:0xa13c8854006e21cdad64ec58f6ac6b621a737c2e
Aug 14 2015 16:53:29 GMT: INFO (drv_ssd): (drv_ssd.c::1278) read_all: failed as_storage_record_read_ssd()
Aug 14 2015 16:53:29 GMT: WARNING (drv_ssd): (drv_ssd.c::1171) {mydb} read_ssd: invalid rblock_id <Digest>:0x0a2981a6b705b5468ad21f2177675cf2e978370c
Aug 14 2015 16:53:29 GMT: WARNING (drv_ssd): (drv_ssd.c::1171) {mydb} read_ssd: invalid rblock_id <Digest>:0x0a2981a6b705b5468ad21f2177675cf2e978370c
Aug 14 2015 16:53:29 GMT: INFO (drv_ssd): (drv_ssd.c::1278) read_all: failed as_storage_record_read_ssd()

What do those mean and is that anything to be concerned about? Initially I did not dd the disks, but even after dd I still see those warnings.

Here’s my basic disk setup:

disks:

NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
xvda    202:0    0    10G  0 disk 
└─xvda1 202:1    0    10G  0 part /
xvdb    202:16   0 745.2G  0 disk 
xvdc    202:32   0 745.2G  0 disk 

config:

namespace mydb {
        replication-factor 2
        memory-size 30G                           
        storage-engine device {     
                device /dev/xvdc   
                device /dev/xvdb
                write-block-size 128K           }
}

Thanks!


#2

These went away after a restart of the aerospike service


#3

Did you start with 2 disks, or did you add xvdc after prior running with only xvdb?

Is this on a community build?


#4

@kporter,

Started with both disks from the beginning. Community build.