similar to: failmode= continue prevents zpool processes from hanging and being unkillable?

Hi all, I'm currently trying to bootstrap llvm-gcc-4.2 from the latest stable LLVM release 2.6 on Solaris SPARC. The compilation with a self-build gcc-4.2.4 goes pretty well, however, I hit a seemingly widely know error during llvm-gcc's bootstrap in getting an assertion during the compile of /data/LLVM/src/GCC/RELEASE_26/gcc/libgcc2.c: /data/LLVM/src/GCC/RELEASE_26/gcc/libgcc2.c: In

Hi Anton, thanks for the fast response. Ty->dump() prints "{double, double}" in the failing case (just before my introduced assert). HTH, and regards, Juergen On 10/30/09 16:19, Anton Korobeynikov wrote: > Hello, Juergen > >> With the full patch, I get the assertion of the 'unhandled REAL_TYPE!', >> so I wonder what needs to be done in order to get

Hi, I'm almost finished to get a complete and seemingly working build of LLVM-GCC (trunk) for SPARC (32-bit only, for now). The only remaining problem is the code generation for one single file (namely cp-demangle.c) where some labels are not put into the assembler/object file due to some (until now) unknown inconsistencies with 'isOnlyReachableByFallthrough' and (most likely) the

Hi * got a (hopefully) simple question: How do I get the trap number if the trap probe fires? (i.e. the sw_trap_number in the description of the Tcc mnemonic) TIA Martin -- Martin M?ller martin.mueller at sun.com Ambassador Datacenter Tel.: +49 2102 45 11740 Sun Microsystems GmbH Fax: +49 2102 499516 D-40880 Ratingen Mobil: +49 172 861 8483 Sitz

Anton, I went with the first alternative with some success. However, now I get some errors during the build of libgcc with 'multiply defined symbols'. One thing I noticed is the following fact: Definition in unwind-pe.h: static const unsigned char * read_sleb128 (const unsigned char *p, _Unwind_Sword *val) --- GCC 4.2.4 bootstrapped on Solaris/SPARC -bash-3.00$ nm unwind-dw2.o | grep

Hi, one quick&dirty way of backing up a pool that is a mirror of two devices is to zpool attach a third one, wait for the resilvering to finish, then zpool detach it again. The third device then can be used as a poor man''s simple backup. Has anybody tried it yet with a striped mirror? What if the pool is composed out of two mirrors? Can I attach devices to both mirrors, let them

Hi there ! I'm just building OpenSSH 3.1 and just found out that the 'configure' script seems to have the same bug as the one provided with 3.0.1: the resulting Makefile has a wrong entry in the include list (.../lib instead of .../include). Looking at the prefix, I suppose this is caused by either '--with-zlib' or '--with-ssl-dir' but I didn't check this in detail

OK, I''ve been putting off this question for a while now, but it eating at me, so I can''t hold off any more. I have a nice 8 gig memory stick I''ve formated with the ZFS file system. Works great on all my Solaris PC''s, but refuses to work on my Sparc processor. So I''ve formated it on my Sparc machine (Blade 2500), works great there now, but not on

Hi, Can I use some commands or scripts to get CPU temperature on Solaris(10 or snv, whatever)? My laptop is Lenovo T61. Great Thanks Jason

Hello, Juergen > With the full patch, I get the assertion of the 'unhandled REAL_TYPE!', > so I wonder what needs to be done in order to get LLVM to produce > code for 'TREE_CODE(type) == REAL_TYPE' in the 'HandleArgument' function. > > > Does anyone have an idea? And why does this only happen on SPARC? What is the value of "Ty" in your case?

Hello, Juergen > Ty->dump() prints "{double, double}" in the failing case (just before my > introduced assert). The answer is simple. The code in question contains extended IEEE FP argument / return type (aka 'long double'). By default it's lowered into struct {double, double} as you already saw and sparc currently does not provide any argument layout hooks. There

Author: cth Repository: /hg/zfs-crypto/gate Revision: fbe522b794de2e79f3275980ba899d96a35e1f2e Log message: 4988141 modunload(1M) can race with di_ioctl(DINFOLODRV) Files: update: usr/src/uts/common/os/modctl.c update: usr/src/uts/common/sys/modctl.h

I''m looking for an easy way to use dtrace on _init() for a kernel module but hitting some roadblocks. This doesn''t work: ::xxx:_init { self->follow=1; } :::_fini { self->follow=0; } Because there''s no "xxx" when dtrace runs. The best way I can see is to use fbt:modinstall:entry, tell dtrace about the modctl struct and match by the name

I''m pretty sure this is my fault but I need some help in fixing the system. It was installed at one point with snv_29 with the pre integration SUNWzfs package. I did a live upgrade to snv_42 but forgot to remove the old SUNWzfs before I did so. When the system booted up got complaints about kstat install because I still had an old zpool kernel module lying around. So I did pkgrm

Hello folks, I have a question and a small problem... I did try to replicate my zfs with all the snaps, so I did run few commands: time zfs send mypool/d at 2006_month_10 | zfs receive mypool2/d at 2006_month_10 real 6h35m12.34s user 0m0.00s sys 29m32.28s zfs send -i mypool/d at 2006_month_10 mypool/d at 2006_month_12 | zfs receive mypool/d at 2006_month_12 real 4h49m27.54s user

I have a shiny new Ultra 40 running S10U3 with 2 x 250Gb disks. I want to make best use of the available disk space and have some level of redundancy without impacting performance too much. What I am trying to figure out is: would it be better to have a simple mirror of an identical 200Gb slice from each disk or split each disk into 2 x 80Gb slices plus one extra 80Gb slice on one of the

Hi all, we have discovered a segfault in nsd-patch when renaming slave zone in nsd config file if some data for this zone still exists in the IXFR diff database. In my case, the zone "black" was renamed to "blackinwhite": > root at ggd115:/cage/nsd/var/nsd/zones#nsd-patch -c > /cage/nsd/etc/nsd-dns-slave.conf > reading database > reading updates to database >

Author: cth Repository: /hg/zfs-crypto/gate Revision: aa8a0144b9e633c0b75e73f05f38c116e2cb69b9 Log message: 4994268 device configuration failure can corrupt parent''s devinfo reference count Files: update: usr/src/uts/common/os/modctl.c

Author: ahl Repository: /hg/zfs-crypto/gate Revision: a2677fc0a5fb6895ed56fc4698646ece44978a48 Log message: 4970475 There should be a stackdepth equivalent for userland 5084954 value of dip can be incorrect in autovec 6181505 dtrace sysinfo:::modload probe does not fire when using ''modload'' 6265417 schedctl-yield isn''t listed in sdt_subr.c 6272558 gcc and dtrace

We''re planning to build a ZFS-based Solaris NFS fileserver environment with the backend storage being iSCSI-based, in part because of the possibilities for failover. In exploring things in our test environment, I have noticed that ''zpool import'' takes a fairly long time; about 35 to 45 seconds per pool. A pool import time this slow obviously has implications for how fast