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 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 the pool stop, and the pool starts exclusively running a slow >>> background task of 1kB reads. >>> Is this a known issue or should I open a new case with Sun? >> 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 <stop-A> sync, <break> sync, or >> >> reboot -dq >> > > In previous attempts, neither "halt -d" nor reboot (with no arguments) > where able to shutdown the machine. Is "reboot -dq" really a bigger hammer > than "halt -d"?
Kindasorta - the q option tells reboot to do its stuff with all guns blazing, as it were. > Sorry to be pedantic, but what is the exact key sequence on a Sun > USB keyboard one should use to force a kernel dump on Solx86? > Since there is no OBP on an X4500 where do I type the sync command? first, either boot with "-k" or shortly after you get to multiuser, run "mdb -K" on the console (and hit :c <enter>). Then you can use <F1>A to drop to kmdb, and then run ::systemdump or 0>rip :c :c or for 32bit mode 0>eip :c :c cheers, James C. McPherson -- Solaris kernel software engineer Sun Microsystems _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
