On Mon, Jul 16, 2007 at 09:36:06PM -0700, Stuart Anderson wrote:
> Running Solaris 10 Update 3 on an X4500 I have found that it is possible
> to reproducibly block all writes to a ZFS pool by running "chgrp -R"
> on any large filesystem in that pool. As can be seen below in the zpool
> iostat outp
Hello Stuart,
Looks like crash dumped went ok.
Check logs after system booted up again if there's a warning that
there's no enough space in /var/crash/x4500gc to save crashdump.
When using zfs on a file servers crashdumps usually will be almost
of server's memory size...
Eventually ju
It looks like there is a problem dumping a kernel panic on an X4500.
During the self induced panic, there where additional syslog messages
that indicate a problem writing to the two disks that make up
/dev/md/dsk/d2 in my case. It is as if the SATA controllers are being
reset during the crash dump
On Tue, Jul 17, 2007 at 03:08:44PM +1000, James C. McPherson wrote:
> >>Log a new case with Sun, and make sure you supply
> >>a crash dump so people who know ZFS can analyze
> >>the issue.
> >>
> >>You can use sync, sync, or
> >>
> >>reboot -dq
> >>
That does appear to have caused a panic/kernel
[EMAIL PROTECTED] wrote on 17/07/2007 02:36:06 PM:
> Running Solaris 10 Update 3 on an X4500 I have found that it is possible
> to reproducibly block all writes to a ZFS pool by running "chgrp -R"
> on any large filesystem in that pool. As can be seen below in the zpool
> iostat output below, aft
I found a very nice doc. that describes the steps to create a kernel dump:
"The Solaris Operating System on x86 Platforms - Crashdump Analysis
Operating System Internals"
http://opensolaris.org/os/community/documentation/files/book.pdf
-> 7.2.2.Forcing system crashdumps
Rayson
On 7/17/07, Ja
Stuart Anderson wrote:
> On Tue, Jul 17, 2007 at 02:49:08PM +1000, James C. McPherson wrote:
>> Stuart Anderson wrote:
>>> Running Solaris 10 Update 3 on an X4500 I have found that it is possible
>>> to reproducibly block all writes to a ZFS pool by running "chgrp -R"
>>> on any large filesystem in
On Tue, Jul 17, 2007 at 02:49:08PM +1000, James C. McPherson wrote:
> Stuart Anderson wrote:
> >Running Solaris 10 Update 3 on an X4500 I have found that it is possible
> >to reproducibly block all writes to a ZFS pool by running "chgrp -R"
> >on any large filesystem in that pool. As can be seen b
Stuart Anderson wrote:
> Running Solaris 10 Update 3 on an X4500 I have found that it is possible
> to reproducibly block all writes to a ZFS pool by running "chgrp -R"
> on any large filesystem in that pool. As can be seen below in the zpool
> iostat output below, after about 10-sec of running th
Running Solaris 10 Update 3 on an X4500 I have found that it is possible
to reproducibly block all writes to a ZFS pool by running "chgrp -R"
on any large filesystem in that pool. As can be seen below in the zpool
iostat output below, after about 10-sec of running the chgrp command all
writes to t
10 matches
Mail list logo
