Basil Hendroff
Wizard
- Joined
- Jan 4, 2014
- Messages
- 1,644
This is an extract from the 11.3 release notes...
Yesterday, I did some stress testing simultaneously replicating from two servers to a target server. You can get a sense of what's happening from the image in this post.
In the end, I lost the pool of the target server due to a kernel panic. It's the first time I've seen one of these in the six years I've been working with FreeNAS, so it must be a fairly rare event. Mind you, the conditions were quite unusual for the test. Fortunately, as it was a backup server, no real harm was done. I was at a slightly elevated risk of losing one or more primary datasets while rebuilding the backup server, but all is good now.
Searching the forum for 'kernel panic', where it's occurred, what seems to be a common reason for the kernel panic is a corrupted snapshot. As rare as it is, with this kernel panic issue still in the wild, it's a little worrying that it might rear its ugly head during local replication, which was only introduced in 11.3. It's one thing losing a backup server designed as a replication target; it's quite another thing losing the pool on a primary server due to local replication.
I'm curious to know what community members think about this.
Yesterday, I did some stress testing simultaneously replicating from two servers to a target server. You can get a sense of what's happening from the image in this post.
In the end, I lost the pool of the target server due to a kernel panic. It's the first time I've seen one of these in the six years I've been working with FreeNAS, so it must be a fairly rare event. Mind you, the conditions were quite unusual for the test. Fortunately, as it was a backup server, no real harm was done. I was at a slightly elevated risk of losing one or more primary datasets while rebuilding the backup server, but all is good now.
Searching the forum for 'kernel panic', where it's occurred, what seems to be a common reason for the kernel panic is a corrupted snapshot. As rare as it is, with this kernel panic issue still in the wild, it's a little worrying that it might rear its ugly head during local replication, which was only introduced in 11.3. It's one thing losing a backup server designed as a replication target; it's quite another thing losing the pool on a primary server due to local replication.
I'm curious to know what community members think about this.