ia64: pcpu.h: No such file or directory

2015-11-05 Thread Anton Shterenlikht
On ia64 10.2-STABLE #17 r289997 I get a panic as soon as I start poudriere bulk I see in core.txt: http://eis.bris.ac.uk/~mexas/core.txt Reading symbols from /boot/kernel/nullfs.ko.symbols...done. Loaded symbols for /boot/kernel/nullfs.ko.symbols #0 doadump (textdump=18810336) at pcpu.h:85 85

unable to boot a healthy zfs pool: all block copies unavailable

2015-11-05 Thread Eugene M. Zheganin
Hi. Today one of my zfs pool disks dies, I was unable to change it on the fly (video board was blocking it) so I powered off, changed disk (not in root pool) and all of a sudden I realized that i cannot boot: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool zroot gptzfsbo

Re: unable to boot a healthy zfs pool: all block copies unavailable

2015-11-05 Thread Andriy Gapon
On 05/11/2015 21:29, Eugene M. Zheganin wrote: > Hi. > > Today one of my zfs pool disks dies, I was unable to change it on the > fly (video board was blocking it) so I powered off, changed disk (not in > root pool) and all of a sudden I realized that i cannot boot: > > ZFS: i/o error - all block

Re: Question about "pcpu" rctl

2015-11-05 Thread Dustin Wenz
As far as I know, pcpu has never worked for limiting beyond a single core. I submitted a patch for kern/kern_racct.c that should fix it: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189870 Please update the bug if it does or doesn't resolve the issue. Maybe that will prompt a committer to

Re: unable to boot a healthy zfs pool: all block copies unavailable

2015-11-05 Thread Michael B. Eichorn
On Fri, 2015-11-06 at 00:29 +0500, Eugene M. Zheganin wrote: > Hi. > > Today one of my zfs pool disks dies, I was unable to change it on the > fly (video board was blocking it) so I powered off, changed disk (not > in > root pool) and all of a sudden I realized that i cannot boot: > > ZFS: i/o er

Re: unable to boot a healthy zfs pool: all block copies unavailable

2015-11-05 Thread Eugene M. Zheganin
Hi. On 06.11.2015 02:58, Andriy Gapon wrote: > > It could be that your BIOS is not able to read past 1TB (512 * INT_MAX). That > seems to be a rather common problem for consumer motherboards. > Here is an example of how it looked for me: > https://people.freebsd.org/~avg/IMAG1099.jpg > Fortunately