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. > > At this point the chgrp -R command is not killable via root kill -9, > and in fact even the command "halt -d" does not do anything. > > In at lest one instance I have seen the chgrp command eventually > respond to the kill command after ~30 minutes, and the pool was > writable again. However, while waiting for this to happen the > kernel was generating "No more processes." when simple commands > where attempted to be run in pre-existing shells, e.g., uname or uptime. ...
> There is nothing in the output of dmesg, svcs -xv, or fmdump associated > with this event. > > 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 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
