zfs zpool import fails 9.2-beta2
steps: glabel drives glabel label disk00 da0 glabel label disk01 da1 glabel label disk02 da2 glabel label disk03 da3 gnop create -S 4096 (4k align drives) gnop create -S 4096 /dev/label/disk0[0-3] create a new zpool with nop device zpool create ztemp raidz2 label/disk00.nop label/disk01.nop label/disk02.nop label/disk03.nop log gpt/zil.nop export newly created zpool zpool export zpool destroy the 4k nop devices gnop destroy /dev/label/disk0[0-3].nop try to import the zpool zpool import -d /dev/label -d /dev/gpt ztemp cannot import 'ztemp': pool is formatted using a newer ZFS version ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: RaspberryPi crash/freez random time after ~r253751
On Sat, 2013-08-03 at 03:40 +0400, Andrey Fesenko wrote: > On Fri, Aug 2, 2013 at 5:09 PM, Andrey Fesenko wrote: > > Hello, > > > > System work stable after migration EABI ~r20130716 (+fix build perl port) > > after make new images r253751 and r253847 system (RPi) freez after > > random time building ports. > > > > got to collect a backtrace log http://pastebin.com/Bbn9ka4N > > > >> uname -a > > FreeBSD raspberry-pi 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r253847M: > > Thu Aug 1 03:54:07 MSK 2013 > > andrey@my_book.local:/home/andrey/obj/arm.armv6/usr/src/sys/RPI-B-IPv6 > > arm > > after patch http://people.freebsd.org/~andrew/trapframe_align.diff > system boot, random time building ports crash system > bt log http://pastebin.com/jBJFf8Zt That is a very strange backtrace. login: panic: vm_fault: fault on nofault entry, addr: db02d000 The page that faulted was db02d000. The stack on entry to the exception handler was db02d008. The exception handling was able to use the stack in the previous page without double-faulting -- it counts down into db02cfxx and lower just fine as the exception handling proceeds. I don't know what to make of it, but I thought I'd mention the oddity in case it triggers ideas for someone else. -- Ian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: RaspberryPi crash/freez random time after ~r253751
On Fri, Aug 2, 2013 at 5:09 PM, Andrey Fesenko wrote: > Hello, > > System work stable after migration EABI ~r20130716 (+fix build perl port) > after make new images r253751 and r253847 system (RPi) freez after > random time building ports. > > got to collect a backtrace log http://pastebin.com/Bbn9ka4N > >> uname -a > FreeBSD raspberry-pi 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r253847M: > Thu Aug 1 03:54:07 MSK 2013 > andrey@my_book.local:/home/andrey/obj/arm.armv6/usr/src/sys/RPI-B-IPv6 > arm after patch http://people.freebsd.org/~andrew/trapframe_align.diff system boot, random time building ports crash system bt log http://pastebin.com/jBJFf8Zt ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Fwd: Problem with curret in vmware
2013/8/2 Attilio Rao > On Fri, Aug 2, 2013 at 8:27 PM, Alexander Yerenkow > wrote: > > > > That was their official tools, which are came from ISO which mounted with > > command "install/upgrade client tools". > > There is not much I can do then, unless they update their source-code. > Or do you have any pointer? > No, I just poked here, maybe there is someone who connected with them somehow. Currently I'm switched to open-vm tools and wrote in wiki about this caveat. Probably this is the only way for some time for me :) > Attilio > > > -- > Peace can only be achieved by understanding - A. Einstein > -- Regards, Alexander Yerenkow ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Fwd: Problem with curret in vmware
On Fri, Aug 2, 2013 at 8:27 PM, Alexander Yerenkow wrote: > > That was their official tools, which are came from ISO which mounted with > command "install/upgrade client tools". There is not much I can do then, unless they update their source-code. Or do you have any pointer? Attilio -- Peace can only be achieved by understanding - A. Einstein ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Fwd: Problem with curret in vmware
That was their official tools, which are came from ISO which mounted with command "install/upgrade client tools". 2013/8/2 Attilio Rao > On Tue, Jul 30, 2013 at 5:55 PM, John Baldwin wrote: > > On Tuesday, July 30, 2013 5:25:06 am Alexander Yerenkow wrote: > >> Hello all. > >> I have panics in vmware with installed vmwaretools (they are guessed > >> culprit). > >> Seems that memory balooning (or using more memory in all vms than there > is > >> in host) > >> produces some kind of weird behavior in FreeBSD. > >> This vm aren't shutted down now, is there somethin I can do to help > >> investigate this? > >> > >> Panic screens: > >> http://gits.kiev.ua/FreeBSD/panic1.png > >> http://gits.kiev.ua/FreeBSD/panic2.png > > > > Looks like their code needs to be updated to work with locking changes in > > HEAD. Attilio is probably the best person to ask. > > Exactly which is the ports you installed? > > Attilio > > > -- > Peace can only be achieved by understanding - A. Einstein > -- Regards, Alexander Yerenkow ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Fwd: Problem with curret in vmware
On Tue, Jul 30, 2013 at 5:55 PM, John Baldwin wrote: > On Tuesday, July 30, 2013 5:25:06 am Alexander Yerenkow wrote: >> Hello all. >> I have panics in vmware with installed vmwaretools (they are guessed >> culprit). >> Seems that memory balooning (or using more memory in all vms than there is >> in host) >> produces some kind of weird behavior in FreeBSD. >> This vm aren't shutted down now, is there somethin I can do to help >> investigate this? >> >> Panic screens: >> http://gits.kiev.ua/FreeBSD/panic1.png >> http://gits.kiev.ua/FreeBSD/panic2.png > > Looks like their code needs to be updated to work with locking changes in > HEAD. Attilio is probably the best person to ask. Exactly which is the ports you installed? Attilio -- Peace can only be achieved by understanding - A. Einstein ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RaspberryPi crash/freez random time after ~r253751
Hello, System work stable after migration EABI ~r20130716 (+fix build perl port) after make new images r253751 and r253847 system (RPi) freez after random time building ports. got to collect a backtrace log http://pastebin.com/Bbn9ka4N > uname -a FreeBSD raspberry-pi 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r253847M: Thu Aug 1 03:54:07 MSK 2013 andrey@my_book.local:/home/andrey/obj/arm.armv6/usr/src/sys/RPI-B-IPv6 arm ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: CURRENT (r253862): buildworld fails in libexec/atf/atf-check: ... /usr/obj/usr/src/tmp/usr/bin/ld: 6: invalid DSO for symbol `__cxa_call_unexpected@@CXXABI_1.3'
On Fri, 2 Aug 2013 08:26:01 +0100 David Chisnall wrote: > On 1 Aug 2013, at 20:10, Baptiste Daroussin wrote: > > > Thay is with the new ld behaviour, it seems like for some reason, > > when linking with libc++ it lacks an explicit link on libcxxrt, I > > ll let c++ people find out why. > > I think dim was planning on adding a libc++ linker script that would > fix this. > > David > Sounds great. Thanks. Oliver signature.asc Description: PGP signature
Re: CURRENT (r253862): buildworld fails in libexec/atf/atf-check: ... /usr/obj/usr/src/tmp/usr/bin/ld: 6: invalid DSO for symbol `__cxa_call_unexpected@@CXXABI_1.3'
On 1 Aug 2013, at 20:10, Baptiste Daroussin wrote: > Thay is with the new ld behaviour, it seems like for some reason, when linking > with libc++ it lacks an explicit link on libcxxrt, I ll let c++ people find > out > why. I think dim was planning on adding a libc++ linker script that would fix this. David signature.asc Description: Message signed with OpenPGP using GPGMail
mountroot error 5
Hi. Today I've upgraded one of my test machines from FreeBSD 9-STABLE to today's CURRENT. On a reboot I got: Solaris: cannot find the pool label for 'zfsroot' Mounting from zfs:zfsroot failed with error 5. When I boot from 9.0-RELEASE DVD1 and use Live Disk, I can see that the pool is available and healthy (version is still 28, I didn't upgrade it). It can be imported (it's not exported when mountroot tries to mount it) and read/written. Can this be resolved somehow ? I recreated cachefile (when on Live CD) and replaced with it the old one, but this didn't seem to change anything (still same error). I've also installed today's CURRENT (from the same obj/src tree) to an USB stick and when booting from it (on this troubled machine) it claims there's no zfs pools at all. I think these events may be connected. Thanks. Eugene. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ia64 r252055: panic: _mtx_lock_sleep: recursed on non-recursive mutex process lock @ /usr/src/sys/ia64/ia64/trap.c:562
This happened when exiting from cssh session: panic: _mtx_lock_sleep: recursed on non-recursive mutex process lock @ /usr/src/ sys/ia64/ia64/trap.c:562 cpuid = 1 KDB: enter: panic [ thread pid 52881 tid 100409 ] Stopped at kdb_enter+0x92: [I2]addl r14=0xffe29320,gp ;; db> show msgbuf msgbufp = 0xe040fffbffb8 magic = 63062, size = 98232, r= 17481, w = 17615, ptr = 0xe040fffa8000, cksu m= 1385682 panic: _mtx_lock_sleep: recursed on non-recursive mutex process lock @ /usr/src/ sys/ia64/ia64/trap.c:562 db> show thread Thread 100409 at 0xe001c8033200: proc (pid 52881): 0xe001c8284de0 name: perl stack: 0xa000be90a000-0xa000be911fff flags: 0x4 pflags: 0 state: RUNNING (CPU 1) priority: 133 container lock: sched lock 1 (0x9ffc00c4c780) db> show proc Process 52881 (perl) at 0xe001c8284de0: state: NORMAL uid: 1001 gids: 1001, 0, 1003 parent: pid 34291 at 0xe0001b9e04a0 ABI: FreeBSD ELF64 arguments: /usr/local/bin/perl threads: 1 100409 Run CPU 1 perl db> thread 100409 [ thread pid 52881 tid 100409 ] kdb_enter+0x92: [I2]addl r14=0xffe29320,gp ;; db> bt trap(0x14, 0xa000be910c00) at trap+0x980 ivt_Data_TLB() at ivt_Data_TLB+0x1d0 --- trapframe at 0xa000be910c00 strlen() at strlen+0x20 kvprintf(0x9ffc00b0f35a, 0x9ffc00b56e60, 0xa000be911230, 0xa, 0xa000 be911300) at kvprintf+0xc80 vprintf(0x9ffc00b0f358, 0xa000be9112f8) at vprintf+0xa0 printf(0x9ffc00b0f358, 0x9ffc00b10660, 0xa0202400, 0x8, 0xa0 207700, 0xae, 0x8, 0xae) at printf+0x80 _isitmyx(0xa0202400, 0xa0207700, 0x1, 0x9ffc00b10660) at _is itmyx+0x260 isitmychild(0xa0202400, 0xa0207700, 0x9ffc00531370, 0xb9d, 0 x7fffd6f0) at isitmychild+0x30 witness_checkorder(0xe0001ba04ca8, 0x9, 0x9ffc00b062f8, 0x28e, 0x0) at w itness_checkorder+0x7b0 __mtx_lock_flags(0xe0001ba04ca8, 0x0, 0x9ffc00b062f8, 0x28e) at __mtx_lo ck_flags+0x190 kern_sigaction(0xe001c8284de0, 0x14, 0x0, 0xa000be911380, 0x9ffc00b0 62f8) at kern_sigaction+0x90 sys_sigaction(0xe001c8033200, 0xa000be9114e8, 0x0, 0xa000be911380) a t sys_sigaction+0xb0 syscall(0xe001c8284de0, 0x0, 0x7fffd6a0, 0xe001c8033200, 0x0, 0x 0, 0x9ffc00991900, 0x8) at syscall+0x5e0 --More-- epc_syscall_return() at epc_syscall_return db> ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
