Out of disk space scenario

[dennisl@IKEA]

What is the recommended recovery procedure from an out-of-disk-space scenario?

I'm short on disk space at the moment and until I've expanded my storage I will run in to some out-of-disk-space incidents for my "soft" dedup iSCSI target devices.
When the disk space is out, Star Wind seems to block further writing to the devices not to corrupt the it.

After I've cleaned up the volume containing the "soft" dedup device, I don't really now how to reenable to blocked dedup device.
I've tried restarting the StarWind service, which just time out. So my current procedure has been to reboot the entire StarWind node

Surely there must be a better way?

[Max (staff)]

Hi Dennis!
When the disk is full StarWind just blocks the device, so you can be sure that the data is safe.
A way out if you've reached the disk limit is to add more storage to the volume, so if you initialized as GPT - you have an option to extend the partition with dd files.
Also, if you stop the service, rename the spbitmap file, and then restart the service your DD device will automount in readonly mode.
But the best way to go is to avoid "out of space" errors by enabling alerts for the disk space and extending storage before it gets full.
We're going to release a re-defined Deduplication engine really soon, so stay tuned, I saw the inside demo of the engine and it's capabilities are absolutely enormous!

[dennisl@IKEA]

Kewl
But why is the service taking for ever shutting down, in out of disk scenarios?

[Anatoly (staff)]

Well, the time is taken by the flushing of the data from cache to disk. I guess you have a lot of data:)