I've got a question I haven't really been able to run down. Everything I've read about using a SLOG for assisting with iSCSI combined with sync=always writes are usually regarding largish pools and thus presumably using spinning disks. My question is, would a SLOG still be recommended when the pool is already an SSD? I figured I'd be ok with a low use system using iSCSI on an SSD with no SLOG, but maybe not.
My question stems from a crashing issue I'm having with a pool shared via iSCSI when enabling sync=always. I'll start another thread on that issue once I reproduce it with less steps (right now I can reproduce it with a handful of actions but I think it can be narrowed down). I don't really expect FN to crash due to lack of a SLOG on a sync=always iSCSI share but if it's due to not using best practices for SLOG/iSCSI then I guess I could accept that and not bother troubleshooting.
My question stems from a crashing issue I'm having with a pool shared via iSCSI when enabling sync=always. I'll start another thread on that issue once I reproduce it with less steps (right now I can reproduce it with a handful of actions but I think it can be narrowed down). I don't really expect FN to crash due to lack of a SLOG on a sync=always iSCSI share but if it's due to not using best practices for SLOG/iSCSI then I guess I could accept that and not bother troubleshooting.