> Silly question - have you checked that the swap partition does not
> overlap your boot pool partition? It could well be that the end of
> the swap partition intrudes into the affected ZFS pool
Interesting idea - all partitons were created with gpart add -a 8
but I have explictly checked, and I
> How much trust do you put in your hardware? Have you ever put the
> hardware under full load for extended periods before e.g. run poudriere
> to build pkg repos?
Ah, now that is a good point. There are two drves in each machine, mirrored,
but one of each of the pair is 6 years old. We havent s
> 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
> When I gte the drives back online on a system I will check this though, thanks
Just took a look and the partitions do not overlap. Thanks for the idea
though...
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/fr
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 d
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:
> When you say corrupt what do you mean, specifically what's the output
> from zpool status?
It doesnt get that far - these are the boot pools and it
wont boot, one due to not finding the pool, the other due
to panicing when trying to impport the pool. Attching the discs
to another machine and tr
> At one point lz4 wasn't supported on boot, I seem to remember that may
> have been addressed but not 100% sure.
yes, its been addressed and works fine. Note that these machines booted
fine befroe and I havent chnaged the OS, simply ran a lot
of Apache CGI scripts to force it out of swap, so its
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
On 2016-Nov-22 10:07:49 +, Pete French wrote:
>to another machine and trying to import the pools causes an instant panic.
Can you provide details of the panic, please.
--
Peter Jeremy
signature.asc
Description: PGP signature
___
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"
11 matches
Mail list logo
