Displaying 4 results from an estimated 4 matches for "snv111".
Did you mean:
snv101
2009 Apr 25
0
qemu 0.10.2 and Solaris snv111 64 Bit /"unexpected erratum #100"
Hi
I''ve installed Solaris snv111 in a QEMU virtual machine using qemu
0.10.2 with kqemu 1.4 enabled. The installation worked without problems
but after rebooting from the virtual disk Solaris panics:
qemu usage:
/opt/qemu_0.10.x/bin/qemu-system-x86_64 -net user -net nic -usb
-usbdevice tablet -L /usr/local/share/qemu_0.9.x -...
2010 Aug 21
1
Upgrade Nevada Kernel
Hi,
I hit ZFS bug that it would be resolve in latter snv 134 or latter.
I''m running SNV111
How do I upgrade to latest version ?
THanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100821/7d8eebc1/attachment.html>
2010 Jun 02
11
ZFS recovery tools
Hi,
I have just recovered from a ZFS crash. During the antagonizing time this took, I was surprised to
learn how undocumented the tools and options for ZFS recovery we''re. I managed to recover thanks
to some great forum posts from Victor Latushkin, however without his posts I would still be crying
at night...
I think the worst example is the zdb man page, which all it does is to ask you
2009 Dec 16
27
zfs hanging during reads
...is a 1.5TB drive connected to a Sil3114 controller (backup1 pool)
c3t0-c3t3 are the 4 x 750GB drives connected to the motherboard ports.
As you can see from the iostat above, c3t1d0 is acting differently.
zpool status shows no errors.
I have not upgraded the ZFS pools since I moved from snv101 to snv111.
I''ve booted up snv101 and the problem still exists.
At first I thought it was in some way linked to the file size I was attempting to read/copy, but I get the problem with files under 1GB.
This is a typical output I am seeing from iostat during a file copy:
tim at opensolaris:~$ iostat...