ZFS Panic on zpool import

L

laufdi

Please see the attached image.
If I set
Code: 
readonly=on
I can import it, but then I can't fix it I guess. Any suggestion on how to fix the problem? Other than buy a new disk and copy everything?
There must be something wrong with the pool, as it crashes in another system as well.

Code: 
FreeBSD 10.1-PRERELEASE #16 r273861: Thu Oct 30 15:32:58 CET 2014 XXX:/usr/obj/usr/src/sys/GENERIC amd64
 

Attachments

  • zpoolpanic.jpg
    zpoolpanic.jpg
    237.7 KB · Views: 1,043
Where are you importing zpool from? Which OS, what version of ZFS? ZFS is very picky about versions when it comes to imports. Another thing. I see that you are using 10.1-PRERELEASE. Either your data is not very important or you like playing with fire. I would never use anything but the -STABLE branch and go even further when it comes to imports. Even though I run 10.0 with ZFS in production I would use only 9.3 for import.
 
Originally it crashed on FreeBSD 10.0-RELEASE-pXX which I updated (binary) to p12 but it didn't help (i386 machine). Now I was trying to import on 10.1

It's a 2TB disk:
Code: 
backup  1,82T  1005G  857G  -  0%  53%  1.00x  ONLINE  -
  ada1  1,82T  1005G  857G  -  0%  53%


Code: 
> zpool get all backup
NAME  PROPERTY  VALUE  SOURCE
backup  size  1,82T  -
backup  capacity  53%  -
backup  altroot  -  default
backup  health  ONLINE  -
backup  guid  6347711522145811649  default
backup  version  -  default
backup  bootfs  -  default
backup  delegation  on  default
backup  autoreplace  off  default
backup  cachefile  -  default
backup  failmode  wait  default
backup  listsnapshots  off  default
backup  autoexpand  off  default
backup  dedupditto  0  default
backup  dedupratio  1.00x  -
backup  free  857G  -
backup  allocated  1005G  -
backup  readonly  on  -
backup  comment  -  default
backup  expandsize  -  -
backup  freeing  0  default
backup  fragmentation  0%  -
backup  leaked  0  default
backup  feature@async_destroy  enabled  local
backup  feature@empty_bpobj  enabled  local
backup  feature@lz4_compress  active  local
backup  feature@multi_vdev_crash_dump  enabled  local
backup  feature@spacemap_histogram  disabled  local
backup  feature@enabled_txg  disabled  local
backup  feature@hole_birth  disabled  local
backup  feature@extensible_dataset  disabled  local
backup  feature@embedded_data  disabled  local
backup  feature@bookmarks  disabled  local
backup  feature@filesystem_limits  disabled  local
 
Interesting! I didn't even know that ZFS works at all on i386.
Maybe you try importing it on another i386 system? Perhaps one not updated?
 
Have you compiled a custom kernel to increase the stack size? It's mandatory now to use ZFS on i386.

There's a warning about that in the e-mail for every 10.1-RC that has been released. If you don't increase the stack size, the kernel panics when running ZFS. This is a known regression in 10.x. It's probably listed on the release web page as well. Search for KVA_PAGES.
 
No custom kernel. It's a slow machine so I only updated via freebsd-update and don't want to compile the kernel. So now it is probably an even worse idea to use ZFS on it anyway. I think I will copy the stuff and then use a UFS file system.
 
Yeah, you are most likely SoL for using ZFS on that machine.

You might be able to boot of a 9.x-based LiveCD and import the pool there. If that works, then re-installing the system using 9.3 would be doable. You just won't be able to upgrade it beyond there unless you compile a custom kernel with KVA_PAGES increased.
 
laufdi said:
No custom kernel. It's a slow machine so I only updated via freebsd-update and don't want to compile the kernel. So now it is probably an even worse idea to use ZFS on it anyway. I think I will copy the stuff and then use a UFS file system.
Click to expand...
So Machine is so slow that it can't compile kernel and you want ZFS.:confused:
 
You must log in or register to reply here.
Back
Top