Date: Fri, 13 Jul 2012 06:47:18 -0700 From: Dennis Glatting <freebsd@penx.com> To: Volodymyr Kostyrko <c.kworr@gmail.com> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS hanging Message-ID: <1342187238.60733.27.camel@btw.pki2.com> In-Reply-To: <4FFFE82B.6010109@gmail.com> References: <1341864787.32803.43.camel@btw.pki2.com> <4FFFE82B.6010109@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2012-07-13 at 12:19 +0300, Volodymyr Kostyrko wrote: > Dennis Glatting wrote: > > I have a ZFS array of disks where the system simply stops as if forever > > blocked by some IO mutex. This happens often and the following is the > > output of top: > > Try switching to clang. Some time ago I was hit by different error - > some process hangs indefinitely and can't be killed. After building > system with clang I obtained a core dump at first reboot and research > turned out that there was some broken directory entry in file system. > Recreating damaged zfs filesystem (leaving all other pool intact) solved > my problem completely. > I am using clang except on my CVS mirrors. I found on the mirrors that the mirror itself cannot update from itself but other hosts can update from the mirror. Somewhere in that M3/assembly muck something crashes in the process. The only way around the problem is to compile the /OS/ using GCC. On the system in question(iirc) I rebuilt the pool yesterday -- I'm in the process of updating parts across my systems. I also wanted to fool around with different ZFS architectures. This morning, with a load average throughout the night of 42 on a 32 core system writing 4TB of data, it is still alive and kicking but its early in the run.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1342187238.60733.27.camel>