Date: Sat, 19 Mar 2011 16:28:38 +0100 From: Marius Strobl <marius@alchemy.franken.de> To: Roger Hammerstein <cheeky.m@live.com> Cc: pjd@freebsd.org, freebsd-sparc64@freebsd.org, mm@freebsd.org Subject: Re: sparc64 hang with zfs v28 Message-ID: <20110319152838.GA8594@alchemy.franken.de> In-Reply-To: <20110310185423.GA50419@alchemy.franken.de> References: <BAY147-w7342A790723770DCE8BD4F9C00@phx.gbl> <BAY147-w229E76D137B7A0DCEB3696F9C70@phx.gbl> <20110307192239.GA31314@alchemy.franken.de> <BAY147-w5926709E28BF613C663D48F9C90@phx.gbl> <20110310185423.GA50419@alchemy.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 10, 2011 at 07:54:23PM +0100, Marius Strobl wrote: > On Wed, Mar 09, 2011 at 10:03:24AM -0500, Roger Hammerstein wrote: > > > > As for the remaining ZFS hangs you're seeing I can reproduce these > with a r219092 checkout (i.e. right after the ZFS v28 import plus > fixes) and the above patch applied, so this problem appears to be > orthogonal: > v215# kldload zfs.ko > ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present; > to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf. > ZFS filesystem version 5 > ZFS storage pool version 28 > v215# mdconfig -a -t malloc -s 100m > md0 > v215# mdconfig -a -t malloc -s 100m > md1 > v215# zpool create tank mirror /dev/md0 /dev/md1 > ^Z > <hangs here> > > The end of the corresponding ktrace dump is: > <...> > v215# kdump | tail > 1683 initial thread RET madvise 0 > 1683 initial thread CALL close(0x5) > 1683 initial thread RET close 0 > 1683 initial thread CALL __sysctl(0x7fdffff8778,0x2,0x7fdffff8840,0x7fdffff88a8,0x40d41168,0x13) > 1683 initial thread SCTL "sysctl.name2oid" > 1683 initial thread RET __sysctl 0 > 1683 initial thread CALL __sysctl(0x7fdffff8840,0x4,0x40e4f158,0x7fdffff8978,0,0) > 1683 initial thread SCTL "vfs.zfs.version.spa" > 1683 initial thread RET __sysctl 0 > 1683 initial thread CALL ioctl(0x3,0xd5985a00 ,0x7fdffff8a60) > > Please work with the ZFS maintainers (CC'ed) to get this fixed. > Is there any progress regarding this or at least some tips what debug information to provide? Marius
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110319152838.GA8594>