search for: swrand

I have one thing happening now at boot which must have happened during the migration to zfs boot. I get an error message about /dev/random: "No randomness provider enabled for /dev/random. Use cryptoadm to provide one." Does anyone know how to fix this? Another thing: Is it possible to upgrade to a higher build when using zfs boot? Is this what LiveUpgrade does? And is there a step by

...date: usr/src/lib/pkcs11/pkcs11_softtoken/common/softRandom.h update: usr/src/uts/common/crypto/api/kcf_random.c update: usr/src/uts/common/crypto/core/kcf_callprov.c update: usr/src/uts/common/crypto/io/crypto.c update: usr/src/uts/common/crypto/io/dprov.c update: usr/src/uts/common/crypto/io/swrand.c update: usr/src/uts/common/io/random.c update: usr/src/uts/common/sys/crypto/impl.h update: usr/src/uts/common/sys/crypto/ops_impl.h update: usr/src/uts/common/sys/crypto/spi.h update: usr/src/uts/common/sys/random.h

I just had a quick play with gzip compression on a filesystem and the result was the machine grinding to a halt while copying some large (.wav) files to it from another filesystem in the same pool. The system became very unresponsive, taking several seconds to echo keystrokes. The box is a maxed out AMD QuadFX, so it should have plenty of grunt for this. Comments? Ian

Hi Folks, I''ve got a 3.9 Tb zpool, and it is casing kernel panics on my Solaris 10 280r (SPARC) server. The message I get on panic is this: panic[cpu1]/thread=2a100a95cc0: zfs: freeing free segment (offset=423713792 size=1024) This seems to come about when the zpool is being used or being scrubbed - about twice a day at the moment. After the reboot, the scrub seems to have