When you say corrupt what do you mean, specifically what's the output
from zpool status?
One thing that springs to mind if zpool status doesn't show any issues, and:
1. You have large disks
2. You have performed an update and not rebooted since.
You may be at the scenario where there's enough data on the pool such
that the kernel / loader are out range of the BIOS.
All depends on exactly what you're seeing?
On 21/11/2016 17:47, Pete French wrote:
So, I am off sick and my colleagues decided to load test our set of five
servers excesively. All ran out of swap. So far so irritating, but whats has
happened is that twoof them now will not boot, as it appears the ZFS pool
they are booting from has become corrupted.
One starts to boot, then crases importing the root pool. The other doenst
even get that far with gptzfsboot saying it can't find the pool to boot from!
Now I can recover these, but I am a bit worried, that it got like this at
all, as I havent ever seen ZFS corrupt a pool like this. Anyone got any
insights,
or suggstions as to how to stop it happening again ?
We are swapping to a separate partition, not to the pool by theway.
-pete.
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
_______________________________________________
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
