From owner-freebsd-current@FreeBSD.ORG Thu May 28 10:18:03 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6C60106564A for ; Thu, 28 May 2009 10:18:03 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from conversation.bsdunix.ch (ns1.bsdunix.ch [82.220.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id 806B08FC1C for ; Thu, 28 May 2009 10:18:03 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from localhost (localhost [127.0.0.1]) by conversation.bsdunix.ch (Postfix) with ESMTP id 21EFA5D5D; Thu, 28 May 2009 12:18:02 +0200 (CEST) X-Virus-Scanned: by amavisd-new at mail.bsdunix.ch Received: from conversation.bsdunix.ch ([127.0.0.1]) by localhost (conversation.bsdunix.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id QBUEgSMXB-mQ; Thu, 28 May 2009 12:18:00 +0200 (CEST) Received: from [192.168.1.3] (home.bsdunix.ch [82.220.17.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by conversation.bsdunix.ch (Postfix) with ESMTP id 41F2E5D26; Thu, 28 May 2009 12:18:00 +0200 (CEST) Message-Id: <899031B0-FB4E-4490-A4AC-0703FAD99E44@bsdunix.ch> From: Thomas Vogt To: Thomas Backman In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Thu, 28 May 2009 12:17:59 +0200 References: <4A1DB307.70007@bsdunix.ch> X-Mailer: Apple Mail (2.935.3) Cc: FreeBSD Current Subject: Re: ZFS Crash with latest current from May 26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 May 2009 10:18:04 -0000 Hi Thomas Am 28.05.2009 um 09:40 schrieb Thomas Backman: > > On May 27, 2009, at 11:39 PM, Thomas Vogt wrote: > >> Hi >> >> I updated today to latest current (from a current system late >> april). Now, the system is very unstable. >> b> bt >> Tracing pid 5142 tid 100159 td 0xffffff0032172720 >> bcopy() at bcopy+0x16 >> dnode_set_blksz() at dnode_set_blksz+0x2ae >> dmu_object_set_blocksize() at dmu_object_set_blocksize+0x4c >> zfs_grow_blocksize() at zfs_grow_blocksize+0x45 >> zfs_freebsd_write() at zfs_freebsd_write+0x9e6 >> VOP_WRITE_APV() at VOP_WRITE_APV+0xfe >> vn_write() at vn_write+0x221 >> dofilewrite() at dofilewrite+0x85 >> kern_writev() at kern_writev+0x60 >> write() at write+0x54 >> syscall() at syscall+0x1bf >> Xfast_syscall() at Xfast_syscall+0xd0 >> --- syscall (4, FreeBSD ELF64, write), rip = 0x80073616c, rsp = >> 0x7fffffffe068, rbp = 0x7fffff > This looks like the panic I've been getting when I don't set my > arc_max really, really low (about 30M on a 1GB RAM system). Since > then, no more crashes. arc_max and arc_min was enabled a few hours ago. But after a few crashes i started to try some "new" options, to see if it helps. Wihtout any luck. Regards, Thomas