Aerospike DRAM TO DRIVE movement



I am new for Aerospike I have configured multinode aerospike labsetup with 2 nodes in community version 3.12.1 I have faced one major problem while change the storage location from DRAM to DRIVE kernel got crashed (i/o error occur ) .I have stopped the services before changing the configuration kindly give me the solution for avoid the critical issue in future


Can you provide any detail on the crash? Such as logs?


find the errror message i cant fetch the log because filesystem crashed


Please post your aerospike.conf, seems like you may have used your root device as the device for a namespace.

# Aerospike database configuration file.

service {
	user root
	group root
	paxos-single-replica-limit 1 # Number of nodes where the replica count is automatically reduced to 1.
        #paxos-protocol v4
	pidfile /var/run/aerospike/
	proto-fd-max 15000

logging {
	# Log file must be an absolute path.
	file /var/log/aerospike/aerospike.log {
		context any info

network {
	service {
		address any
		port 3000

	heartbeat {
		mode mesh
		port 3002
                mesh-seed-address-port 3002
		# To use  unicast-mesh heartbeats, remove the 3 lines above, and see
		# aerospike_mesh.conf for alternative.

		interval 250
		timeout 25

	fabric {
		port 3001

	info {
		port 3003

namespace test {
	replication-factor 2
	memory-size 16G
	default-ttl 30d # 30 days, use 0 to never expire/evict.

	storage-engine memory

#namespace bar {
#	replication-factor 2
#	memory-size 4G
#	default-ttl 30d # 30 days, use 0 to never expire/evict.
#	storage-engine memory

	# To use file storage backing, comment out the line above and use the
	# following lines instead.
#        storage-engine device {
#           file /opt/aerospike/data/bar.dat
#        	filesize 16G
#		data-in-memory true # Store data in memory in addition to file.
#	}


hi kindly find the conf fle I configured initialy in in RAM storage location when i chnaged to drive filesystem crashed


Did you at any point use device instead of file? A mistake I have seen in the past is users passing root mount as the device and wiping their OS.

These IO errors arent being generated by Aerospike, you may want to check the health of your disks. Smartctl may be a good place to start.