Here's the output. Numbers may be a little off because I'm doing a nightly
build and compressing a crashdump with bzip2 at the same time.
extended device statistics
r/sw/s Mr/s Mw/s wait actv wsvc_t asvc_t %w %b device
3.7 19.40.10.3 3.3 0.0 142.
I'll provide you with the results of these commands soon. But for the record,
solaris does hang (dies out of memory, can't type anything on the console,
etc). What I can do is boot with -k and get to kmdb when it's hung (BREAK over
serial line). I have a crashdump I can upload.
I checked the di
I checked - this system has a UFS root. When installed as snv_84 and then LU'd
to snv_89, and when I fiddled with these packages from various other releases,
it had the stacktrace instead of the ZFS admin GUI (or the well-known
"smcwebserver restart" effect for the older packages).
This system
Just tried SXCE B90 with UFS as root partition in VBOX 1.6 and it works fine,
so ZFS as the root partition might be the cause...
Cheers, JP
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail
On May 30, 2008, at 6:59 PM, Erik Trimble wrote:
> The only drawback of the older Socket 940 Opterons is that they don't
> support the hardware VT extensions, so running a Windows guest
> under xVM
> on them isn't currently possible.
From the VirtualBox manual, page 11
• No hardware virtua
I have the same problem here with https://localhost:6789 ZFS Administration
bombing out with the same error.
I am using SXCE B90 with ZFS as the root partition running in VBOX 1.6.
Any suggestions on next steps?
Cheers, JP
This message posted from opensolaris.org
___
So you are experiencing slow I/O which is making the deletion of this clone
and the replay of the ZIL take forever. It could be because of random I/O ops,
or one of your disks which is dying (not reporting any errors, but very slow
to execute every single ATA command). You provided the output of
This sounds like a pain.
Is it possible that you bought support from SUN on this matter, if this is
really important to you?
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.or
Greetings,
I was experimenting with zfs, and i made the following test, i shutdown the
computer during a write operation
in a mirrored usb storage filesystem.
Here is my configuration
NGS USB 2.0 Minihub 4
3 USB Silicom Power Storage Pens 1 GB each
These are the ports:
hub devices
/---
On Sat, May 31, 2008 at 9:38 PM, Mike Gerdts <[EMAIL PROTECTED]> wrote:
> $ find /ws/mount/onnv-gate/usr/src/uts/sun4u/serengeti/unix
> /ws/mount/onnv-gate/usr/src/uts/sun4u/serengeti/unix
> /ws/mount/onnv-gate/usr/src/uts/sun4u/serengeti/unix/.make.state.lock
> /ws/mount/onnv-gate/usr/src/uts/sun4
On Sun, Jun 1, 2008 at 3:53 AM, Enda O'Connor <[EMAIL PROTECTED]> wrote:
> Jim Litchfield at Sun wrote:
>>
>> I think you'll find that any attempt to make zones (certainly whole root
>> ones) will fail after this.
>>
>
> right, zoneadm install actually copies in the global zones undo.z into the
> l
Jim Litchfield at Sun wrote:
> I think you'll find that any attempt to make zones (certainly whole root
> ones) will fail after this.
>
right, zoneadm install actually copies in the global zones undo.z into
the local zone, so that patchrm of an existing patch will work.
haven't tried out what
I have very little technical knowledge on what the problem is.
Some random things to try:
Make a seperate zpool and filesytem for the swap.
Add more ram to the system.
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discus
13 matches
Mail list logo
