search for: blasingam

I''m curious to know what files are being used from a NFS server perspective. I''m unable to trace the client because it is in the boot phase. Looking at the io provider, I believe it does not allow you to look at what files are being requested. That would lead me to the fbt provider. Does anyone know what fbt provides the file handle for NFS client request on the NFS

I posted this on the www.nexentastor.org forums, but no answer so far, so I apologize if you are seeing this twice. I am also engaged with nexenta support, but was hoping to get some additional insights here. I am running nexenta 3.0.3 community edition, based on 134. The box crashed yesterday, and goes into a reboot loop (kernel panic) when trying to import my data pool, screenshot attached.

I''m getting an odd behavior while trying to trace a mysql process using the -p flag on a Sun Cluster. This fails # dtrace -n ''pid$target::*mysql_parse*:entry {}'' -p `pgrep -x mysqld` dtrace: failed to grab pid 16537: process is traced Yet this works # dtrace -n ''pid$1::*mysql_parse*:entry {}'' `pgrep -x mysqld` dtrace: description

Hello. I have a Solaris 11/11 x86 box (which I migrated from SolEx 11/10 a couple of weeks ago). Without no obvious reason (at least for me), after an uptime of 1 to 2 days (observed 3 times now) Solaris sets arc_no_grow to 1 and then never sets it back to 0. ARC is being shrunk to less than 1 GB -- needless to say that performance is terrible. There is not much load on this system. Memory

I''m trying to install CiscoWorks 2.5 on Solaris 10 update 1, and after the install when I try to start the daemon, it errors: # /opt/CSCOpx/objects/dmgt/dmgtd.sol ERROR: open file dmgtd failedERROR >>>>>>>>>>>>> open msg catalog failed. NLSPATH incorrect or objects/share/nls/C/dmgtd.cat is missing. # echo $NLSPATH

Hi, I just had my Dell R610 reboot with a kernel panic when I threw a couple of zfs clone commands in the terminal at it. Now, after the system had rebooted zfs will not import my pool anylonger and instead the kernel will panic again. I have had the same symptom on my other host, for which this one is basically the backup, so this one is my last line if defense. I tried to run zdb -e