zfs:lo lockup
Boris Kochergin
spawk at acm.poly.edu
Sat Sep 5 01:05:24 UTC 2009
It has very likely been fixed in ZFS version 13, which is available in
RELENG_7, RELENG_8, and CURRENT. Have a look at the thread at
http://lists.freebsd.org/pipermail/freebsd-fs/2009-August/006694.html
for more information.
-Boris
rondzierwa at comcast.net wrote:
> I'm running zfs on FreeBSD 7.2-RELEASE-p2. i csup'ed sys src 4 weeks ago. I have
> a 3Ware raid card with 8 1tb drives in raid5. I put the whole space in zfs as a tank and
> created several file systems from it. these are served to windoze clients via samba 3.0.34.
>
> several times a week i have to forcibly reset and reboot the system because one of the
> smbd processes is stuck in zfs:lo state (as displayed by "top"), and cannot be killed.
>
> Typically this happens when there is more than one client machine accessing the zfs
> shares. It happens when they are both accessing the same share, or different ones.
>
> is this something that has already been fixed? if so, what do i have to upgrade to get
> the fix? if not, what information can i provide to help somebody find a fix?
>
> thanks much
> ron.
>
>
>
>
> _______________________________________________
> freebsd-fs at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
>
More information about the freebsd-fs
mailing list