Help! two machines ran out of swap and corrupted their zpools!

Steven Hartland killing at multiplay.co.uk
Tue Nov 22 09:43:05 UTC 2016


At one point lz4 wasn't supported on boot, I seem to remember that may 
have been addressed but not 100% sure.

If it hasn't and your kernel is now compressed that may explain it?

Have you tried booting from a live cd and checking the status of the pool?

On 22/11/2016 08:43, Pete French wrote:
>> zpool import -N -O readonly=on -f -R /mnt/somezpoool
>>
>> If that doesn't help try:
>>
>> zpool import -N -O readonly=on -f -R /mnt/somezpoool -Fn
> I got someone to do this (am still having toruble finding time
> as am supposed to be off sick) and it causes instant kernel panic
> on trying to import the pool. Same as it does on boot.
>
>> Drop us a line of your configuration and used ZFS features. Like dedup,
>> snapshots, external l2 logs and caches.
> 10.3-STABLE r303832 from start of August. One simple pool, two
> drives mirrored, GPT formatted drives. No dedup, no snapshots,
> no external logs or caches. We have lz4 comression enabled on the
> filesystem, but apart from that its an utterly bog-standard setup.
>
> Am an leaning towards faulty hardware now actually... seems most likely...
>
> -pete.
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"



More information about the freebsd-stable mailing list