Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Oct 2014 09:36:51 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 194654] New: 10.1-RC3 hangs with simultanious writes
Message-ID:  <bug-194654-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194654

            Bug ID: 194654
           Summary: 10.1-RC3 hangs with simultanious writes
           Product: Base System
           Version: 10.1-RC2
          Hardware: amd64
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: misc
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: FreeBSD@ShaneWare.Biz

Created attachment 148728
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=148728&action=edit
ASUS P8H61-M LE/USB3 dmesg.boot

After almost 3 years of running 9.x on this machine with only manual reboots to
install updates I find that I am unable to keep 10.1 running for more than a
day.

After some trial and error I have found that two simultaneous writes to disk
causes a memory issue that ends with a hang once wired memory usage hits 7GB
(8GB installed) at this stage the reset button is the only thing that still
works.

Under light usage this would appear to build up over the period of a day, while
forced heavy usage causes a hang within a minute. Running two copies of the
attached test.sh while watching top seems normal for a while, then within a
minute the wired memory amount can quickly jump from 3GB to 7GB within 6
seconds. Running two instances of the script simultaneously on a USB memstick
and the zfs filesystem or both on the zfs filesystem produces the same problem.

I have tested this by booting into single user mode, mounting the filesystem
and using screen to run top and two scripts at the same time with the same
result.

Machine is an ASUS P8H61-M LE/USB3 corei5 8GB with 3x 2TB Seagate drives in
raidz. I think the pool was created with 9.2 (possibly with 9.1) and the pool
and bootcode was updated after installing 10.1 just before RC2 was tagged.

FreeBSD leader.local 10.1-RC3 FreeBSD 10.1-RC3 #16 r273471: Thu Oct 23 06:32:33
ACDT 2014     root@leader.local:/usr/obj/usr/src/sys/GENERIC  amd64

In single user mode the following modules were loaded -

kernel
zfs.ko
opensolaris.ko
geom_eli.ko
crypto.ko
geom_journal.ko
geom_mirror.ko
geom_uzip.ko
aio.ko
coretemp.ko
sem.ko
smb.ko
smbus.ko
libiconv.ko
libmchain.ko
cd9660_iconv.ko
ext2fs.ko
msdosfs_iconv.ko
udf.ko
udf_iconv.ko
tmpfs.ko
nvidia.ko
dtraceall.ko
profile.ko
cyclic.ko
dtrace.ko
systrace_freebsd32.ko
systrace.ko
sdt.ko
lockstat.ko
fasttrap.ko
fbt.ko
dtnfscl.ko
dtmalloc.ko

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-194654-8>