Why is Nexentastor so slow – especially to delete files

Personally, I'd run the bonnie++ benchmark from the command line without the Nexenta wrapper.

First, you'll need to log in as the root user and get into the full command shell mode using:

option expert_mode = 1 followed by !bash

Answer y the prompt that says You are about to enter the Unix ("raw") shell and execute low-level Unix command(s).

From here, you can download and install the proper bonnie++ executable.

# Update the apt package database
root@nyx:/volumes# apt-get update

# Install bonnie++
root@nyx:/volumes# apt-get install bonnie++

# Change to the target directory
root@nyx:/volumes# cd /volumes/Data1/your.cifs.folder

At this point, you can run a bonnie benchmark with or without parameters.
I usually run bonnie++ -u root -n 64:100000:16:64, but you'll be fine running bonnie++ -u root inside of the directory you wish to work in.

Post your results. There are a few tweaks needed for Nexenta when used without SAS or SCSI disks. You should at least see 80-90MB/s sequential write speed to a RAIDZ array. Read speed should be better than that.

The key here was to change to the /var/crash/myhost directory and run the savecore -f vmdump.x command on the crash dump file. That process creates a unix.x file that can be used by the mdb -k unix.x vmcore.x command, where "x" is the core dump number.