From owner-freebsd-fs@freebsd.org Sun Oct 16 05:56:24 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 867FDC14006 for ; Sun, 16 Oct 2016 05:56:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6B9AAB13 for ; Sun, 16 Oct 2016 05:56:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9G5uNVt070160 for ; Sun, 16 Oct 2016 05:56:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 213507] [msdosfs] [patch]: Prevent occasional directory corruption while extending it to another cluster Date: Sun, 16 Oct 2016 05:56:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2016 05:56:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213507 Konstantin Belousov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kib@FreeBSD.org --- Comment #1 from Konstantin Belousov --- Right after the both branches of the if() statement, one of which you patch= ed, there is vfs_bio_clrbuf() call to clear the buffer. Due to this, I highly doubt that the patch changes anything, i.e. the bug m= ust be elsewere. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 16 06:09:10 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A397EC1421A for ; Sun, 16 Oct 2016 06:09:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 92FC9FC4 for ; Sun, 16 Oct 2016 06:09:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9G69Ae6056010 for ; Sun, 16 Oct 2016 06:09:10 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 213507] [msdosfs] [patch]: Prevent occasional directory corruption while extending it to another cluster Date: Sun, 16 Oct 2016 06:09:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: vladislav.movchan@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2016 06:09:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213507 --- Comment #2 from Vladislav Movchan --- (In reply to Konstantin Belousov from comment #1) While debugging I checked content of newly allocated cluster right after vfs_bio_clrbuf() call. So after execution of vfs_bio_clrbuf() it is possibl= e to see junk/random data in bp->b_data. I just rechecked it once again to make sure - sometimes newly allocated clu= ster contains just zeroes, but sometimes there are random data. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 16 06:16:15 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F9C6C14355 for ; Sun, 16 Oct 2016 06:16:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 645FA315 for ; Sun, 16 Oct 2016 06:16:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9G6GEoe044381 for ; Sun, 16 Oct 2016 06:16:15 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 213507] [msdosfs] [patch]: Prevent occasional directory corruption while extending it to another cluster Date: Sun, 16 Oct 2016 06:16:14 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2016 06:16:15 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213507 --- Comment #3 from Konstantin Belousov --- (In reply to Vladislav Movchan from comment #2) vfs_bio_clrbuf() zeroes invalid chunks of the buffer pages, leaving the val= id chunks alone, for VMIO buffers. If there are (partially) valid pages in the newly extended denode, this means that, most likely, some other code left t= he garbage on the vnode vm_object' page queue. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 16 06:25:12 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13C0CC14572 for ; Sun, 16 Oct 2016 06:25:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 030F297E for ; Sun, 16 Oct 2016 06:25:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9G6PBYK076966 for ; Sun, 16 Oct 2016 06:25:11 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 213507] [msdosfs] [patch]: Prevent occasional directory corruption while extending it to another cluster Date: Sun, 16 Oct 2016 06:25:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: vladislav.movchan@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2016 06:25:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213507 --- Comment #4 from Vladislav Movchan --- (In reply to Konstantin Belousov from comment #3) Thanks for the explanation. I'll get back if I manage to find true reason w= hat causes this. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 16 06:34:53 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4274EC147F8 for ; Sun, 16 Oct 2016 06:34:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 312D5D3E for ; Sun, 16 Oct 2016 06:34:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9G6YqWJ095906 for ; Sun, 16 Oct 2016 06:34:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 213507] [msdosfs] [patch]: Prevent occasional directory corruption while extending it to another cluster Date: Sun, 16 Oct 2016 06:34:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2016 06:34:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213507 --- Comment #5 from Konstantin Belousov --- (In reply to Vladislav Movchan from comment #4) You could try to check my hypothesis by catching the garbage buffer _before_ the vfs_bio_clrbuf() call and see if any page forming the buffer has valid = bits set. Look at the vfs_bio_clrbuf() code to see what I mean. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 16 12:15:02 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25310C13F0A for ; Sun, 16 Oct 2016 12:15:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1405D1A21 for ; Sun, 16 Oct 2016 12:15:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9GCF1rL008821 for ; Sun, 16 Oct 2016 12:15:01 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 213507] [msdosfs] [patch]: Prevent occasional directory corruption while extending it to another cluster Date: Sun, 16 Oct 2016 12:15:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: vladislav.movchan@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2016 12:15:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213507 --- Comment #6 from Vladislav Movchan --- Created attachment 175818 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D175818&action= =3Dedit Updated patch --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 16 12:16:08 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A5A0C13F70 for ; Sun, 16 Oct 2016 12:16:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 099AD1AA9 for ; Sun, 16 Oct 2016 12:16:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9GCG7Kn054555 for ; Sun, 16 Oct 2016 12:16:07 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 213507] [msdosfs] [patch]: Prevent occasional directory corruption while extending it to another cluster Date: Sun, 16 Oct 2016 12:16:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: vladislav.movchan@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2016 12:16:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213507 --- Comment #7 from Vladislav Movchan --- (In reply to Konstantin Belousov from comment #5) I confirmed your hypothesis - sometimes buffer pages have valid bits set and sometimes they don't. Original problem occurs only in cases when valid bits are set, so vfs_bio_clrbuf() don't zero random data in buffer. Also I went through history and found that originally buffer data was always zeroed by call to clrbuf() macro and in base r171522 it was changed to vfs_bio_clrbuf() as an optimization. I suppose what I see is just a regression of this optimization and it was n= ot noticed since then as "directory extension to another cluster" is a rare operation. I attached another patch which restores original behaviour just for the "directory grows" case. With this patch I'm no longer able to reproduce this problem. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 16 15:20:12 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EFB9C14BBC for ; Sun, 16 Oct 2016 15:20:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5E7381FA7 for ; Sun, 16 Oct 2016 15:20:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9GFKCdv095691 for ; Sun, 16 Oct 2016 15:20:12 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 90815] [smbfs] [patch] SMBFS with character conversions sometimes hangs Date: Sun, 16 Oct 2016 15:20:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 6.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: junchoon@dec.sakura.ne.jp X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2016 15:20:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D90815 --- Comment #6 from Tomoaki AOKI --- (In reply to Andrey V. Elsukov from comment #5) With my patch, if smb_copy_iconv() is called recursively, you're right. If not, my patch can be better, as whole src is kept unchanged if iconv_con= v() returns -1. *According to the prototype of iconv_conv() in src/sys/sys/iconv.h, src is constant, so shouldn't be changed at all by iconv_conv(). With my patch, if modified code path is executed, cp would copy with origin= al filename unchanged and succeeds, while with yours the file is skipped. Anyway, your patch would be safer and cp didn't hang for me, at least for n= ow, while my patch can be more convenient if iconv implementation is problematic and the src string should be safe for dst. Will need another eye to proceed. By the way, your patch couldn't be applied (incomplete and need fix). Sorry for delay. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 16 15:31:09 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B730C14116 for ; Sun, 16 Oct 2016 15:31:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6AFD918E4 for ; Sun, 16 Oct 2016 15:31:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9GFV9rn044866 for ; Sun, 16 Oct 2016 15:31:09 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 90815] [smbfs] [patch] SMBFS with character conversions sometimes hangs Date: Sun, 16 Oct 2016 15:31:09 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 6.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: junchoon@dec.sakura.ne.jp X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2016 15:31:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D90815 --- Comment #7 from Tomoaki AOKI --- Created attachment 175826 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D175826&action= =3Dedit Andrey's patch modified to be applicable Andrey's patch fixed to be applicable. *Added truncated tail portion. *Some space to tab conversion. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 16 21:00:34 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7B435C14C17 for ; Sun, 16 Oct 2016 21:00:34 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 724DB179B for ; Sun, 16 Oct 2016 21:00:34 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9GL01cI044653 for ; Sun, 16 Oct 2016 21:00:34 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201610162100.u9GL01cI044653@kenobi.freebsd.org> From: bugzilla-noreply@FreeBSD.org To: freebsd-fs@FreeBSD.org Subject: Problem reports for freebsd-fs@FreeBSD.org that need special attention Date: Sun, 16 Oct 2016 21:00:34 +0000 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Oct 2016 21:00:34 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 203492 | mount_unionfs -o below causes panic Open | 136470 | [nfs] Cannot mount / in read-only, over NFS Open | 139651 | [nfs] mount(8): read-only remount of NFS volume d Open | 140068 | [smbfs] [patch] smbfs does not allow semicolon in Open | 144447 | [zfs] sharenfs fsunshare() & fsshare_main() non f Open | 203419 | solaris assert: (dn->dn_phys->dn_nlevels == 0 && Open | 211491 | System hangs after "Uptime" on reboot with ZFS 7 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Mon Oct 17 09:37:59 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87D26C15D9A for ; Mon, 17 Oct 2016 09:37:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 772B5186F for ; Mon, 17 Oct 2016 09:37:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9H9bwOS072362 for ; Mon, 17 Oct 2016 09:37:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 213507] [msdosfs] [patch]: Prevent occasional directory corruption while extending it to another cluster Date: Mon, 17 Oct 2016 09:37:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2016 09:37:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213507 --- Comment #8 from Konstantin Belousov --- (In reply to Vladislav Movchan from comment #7) I probably was not clear enough. The problem is that a previous operation left the pages on the vnode page q= ueue behind the directory denode end. The damage is not limited to the situatio= n of extending the directory, it might have other consequences with varying severity. E.g., if the issue also happens for regular files, then extending file might result in the garbage or some previously removed unrelated disk = file content to appear in the extended portion, readable by user. That said, your patch seems to only paper over the real problem. Right thi= ng to do is to track the location where the damage happens. E.g., UFS also had similar problems, where failed file extension (e.g., for lack of free space) was followed by an incomplete cleanup and dandling buffers and pages. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Oct 17 21:45:24 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7CCB8C16643 for ; Mon, 17 Oct 2016 21:45:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6C36FDBC for ; Mon, 17 Oct 2016 21:45:24 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9HLjNDj005313 for ; Mon, 17 Oct 2016 21:45:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 211013] Write error to UFS filesystem with softupdates panics machine Date: Mon, 17 Oct 2016 21:45:24 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-BETA1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2016 21:45:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211013 --- Comment #8 from commit-hook@freebsd.org --- A commit references this bug: Author: mckusick Date: Mon Oct 17 21:44:41 UTC 2016 New revision: 307533 URL: https://svnweb.freebsd.org/changeset/base/307533 Log: MFC r304230: Add two new macros, SLIST_CONCAT and LIST_CONCAT. MFC r304239: Bug 211013 reports that a write error to a UFS filesystem running with softupdates panics the kernel. PR: 211013 Changes: _U stable/11/ stable/11/share/man/man3/queue.3 stable/11/sys/sys/queue.h stable/11/sys/ufs/ffs/ffs_softdep.c stable/11/sys/ufs/ffs/softdep.h --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Oct 17 21:50:27 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6847DC167A0 for ; Mon, 17 Oct 2016 21:50:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 55E6E1AC for ; Mon, 17 Oct 2016 21:50:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9HLoQTj011551 for ; Mon, 17 Oct 2016 21:50:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 211013] Write error to UFS filesystem with softupdates panics machine Date: Mon, 17 Oct 2016 21:50:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-BETA1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2016 21:50:27 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211013 --- Comment #9 from commit-hook@freebsd.org --- A commit references this bug: Author: mckusick Date: Mon Oct 17 21:49:55 UTC 2016 New revision: 307534 URL: https://svnweb.freebsd.org/changeset/base/307534 Log: MFC r304230: Add two new macros, SLIST_CONCAT and LIST_CONCAT. MFC r304239: Bug 211013 reports that a write error to a UFS filesystem running with softupdates panics the kernel. PR: 211013 Changes: _U stable/10/ stable/10/share/man/man3/queue.3 stable/10/sys/sys/queue.h stable/10/sys/ufs/ffs/ffs_softdep.c stable/10/sys/ufs/ffs/softdep.h --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Oct 17 22:43:56 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2ADBFC15C0E for ; Mon, 17 Oct 2016 22:43:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1A333E5C for ; Mon, 17 Oct 2016 22:43:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9HMht08068900 for ; Mon, 17 Oct 2016 22:43:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 211013] Write error to UFS filesystem with softupdates panics machine Date: Mon, 17 Oct 2016 22:43:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-BETA1 X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: mckusick@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2016 22:43:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211013 Kirk McKusick changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|In Progress |Closed --- Comment #10 from Kirk McKusick --- With MFC to stable-10 and stable-11 this bug report can be closed. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Oct 18 06:06:07 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2B973C1671C; Tue, 18 Oct 2016 06:06:07 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E32B58DF; Tue, 18 Oct 2016 06:06:06 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u9I64SGL013639 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 17 Oct 2016 23:04:31 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: zfs crash on FreeBSD 10.3 To: =?UTF-8?Q?Trond_Endrest=c3=b8l?= References: <55fa7ab0-2a65-6a3c-4b19-49c2588b5911@freebsd.org> Cc: "freebsd-fs@freebsd.org" , freebsd-current From: Julian Elischer Message-ID: Date: Tue, 18 Oct 2016 14:04:22 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 06:06:07 -0000 On 14/10/2016 6:31 PM, Trond Endrestøl wrote: > On Fri, 14 Oct 2016 00:19-0700, Julian Elischer wrote: > >> I attempted to add a second partition to an existing FS pool in FreeBSD 10.3 >> and the result was a crash.. >> >> is there anyone out there with a scratch system (10.3) (or two spare drives) >> who can show me this working? >> >> Does it look familiar to anyone? >> >> The drive 'boot0' is being used as the root drive, but we are in single user >> mode, so its' read-only at this stage. >> >> =============== cut-n-paste ============= >> >> [boot -s] >> >> [...] >> >> Trying to mount root from zfs:p8/image1 []... >> Enter full pathname of shell or RETURN for /bin/sh: >> PS1="# " >> # >> # >> # ls /dev/gpt >> boot0 boot1 >> # zpool attach -f p8 gpt/boot0 gpt/boot1 > Do you really need to force zpool to attach the second partition? > What happens if you omit the -f flag? from memory, it does nothing I can't test it now but I know the example I saw on the internet gave '-f , and when I tried to leave it out, it didn't work. I vaguely remember that it complained about the filesystem being in use. I will try it again some time when I have the setup running and get back to you. > >> Fatal trap 12: page fault while in kernel mode >> cpuid = 1; apic id = 01 >> fault virtual address = 0x50 >> fault code = supervisor read data, page not present >> instruction pointer = 0x20:0xffffffff81717063 >> stack pointer = 0x28:0xfffffe0169bfc640 >> frame pointer = 0x28:0xfffffe0169bfc9a0 >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 0, pres 1, long 1, def32 0, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 3 (txg_thread_enter) >> trap number = 12 >> Panic:Thought about setting the watchdog to 10 Minutes >> panic: page fault >> cpuid = 1 >> >> KDB: stack backtrace: >> stack1 db_trace_self_wrapper+0x2a >> kdb_backtrace+0x37 vpanic+0xf7 >> panic+0x67 trap_fatal+0x264 >> trap_pfault+0x1c2 >> trap+0x38c >> calltrap+0x8 >> dsl_scan_sync+0x2f3 >> spa_sync+0x328 >> txg_sync_thread+0x140 >> fork_exit+0x135 >> fork_trampoline+0xe >> >> KDB: enter: panic >> [ thread pid 3 tid 100328 ] >> Stopped at kdb_enter+0x50: movq $0,0x6bd5cd(%rip) >> db> reboot >> >> I will add that after this, every boot hits this problem. (same stack trace). >> the box is effectively bricked >> (or would be if it weren't just a bhyve image) From owner-freebsd-fs@freebsd.org Tue Oct 18 15:30:08 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C83BC17767 for ; Tue, 18 Oct 2016 15:30:08 +0000 (UTC) (envelope-from ardovm@yahoo.it) Received: from nm16-vm4.bullet.mail.ir2.yahoo.com (nm16-vm4.bullet.mail.ir2.yahoo.com [212.82.96.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1E3EB83F for ; Tue, 18 Oct 2016 15:30:07 +0000 (UTC) (envelope-from ardovm@yahoo.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.it; s=s2048; t=1476804436; bh=OlkCLEvgFHR4SBcQ4krIFYX8/TXrg9R9bVHkQ2QsHl4=; h=Date:From:To:Subject:From:Subject; b=sWHJ5Vu+o+uDmiMSp04v13NTKX8NVD7RAYC9pka51ksHP1kTQsrP4g4xyYXX63sDfbXNocW1X+N+wYrlICA4zj9jb2zheuSkKGsMrMG+9RUhrrWAbCwxlw6Tj82D6cG7+WMx6Da+rI+CYDo0ISQ3mItUkrRG+lMUOsU6717CiE/MYoocqi+ktUeoN9QLwiCqJJ3p19+io0JZEew4tzPtjQuVDfKg3XTDZ2DRgr91wSf+bVBOAFMRYgWEyk1qWdZvuBO+NwzZFL/M4h1RpUBkrw/dWcRllr4vOXdFHMK03fIkhB/E52JjDJ8js07wH6DxBqtjhjCjybv+IR3UQRFHcw== Received: from [212.82.98.124] by nm16.bullet.mail.ir2.yahoo.com with NNFMP; 18 Oct 2016 15:27:16 -0000 Received: from [46.228.39.98] by tm17.bullet.mail.ir2.yahoo.com with NNFMP; 18 Oct 2016 15:27:16 -0000 Received: from [127.0.0.1] by smtp135.mail.ir2.yahoo.com with NNFMP; 18 Oct 2016 15:27:16 -0000 X-Yahoo-Newman-Id: 433388.14901.bm@smtp135.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: hz3Xv9AVM1kvWDKemb.aWLfXpMf6DVpjrv.4h1_x1VllNQ1 oPEuzA4HoPc88JeI4.rBHrKKC2UBHXdPjaUY9PZ0egqG6LMO1yCxb5m6sUvA hUrgjPs51b38YgMw_XV98y3.6XT32uF5yIjI5.LDunljdpFNhu9s_kFRComc rTpBul.Dvovfc_Gs.Dl_XWyxN82tq8dskqt4KSqBTiZCLQj6ookDSbnekdFJ QUPiNZwg4ujd5w88._BF19uSy4Mc.XnBqXMN4ZXJsgYOBWA_rCdV2qIJrQaG ufpxrmfR08kGll45rSWDQA.uPb7Zcs2ZjZ_aX_pxfc2P39_RMkvTgV6oJH7w TxmWb9jalkgbX_GUkmWxgX3Uy9fpJuETObLrwvU4ZGb6Cr3XwTJnp.91_a2_ WaPhSxG4W3Ox5tgDLZ38LKg0qyQ74ooqdDnL7PmHB5dAg3YlEq.bSaGBazwy r3bF9ed11VbHL2UdIDxYmjqUnzrG6cwQJ.F53JiK8jVxmVVWifl7g46QjRmp wex4DhZLtodc5a_43CLp1f8xj6BJ.n2ngdQGVYXBFkELPYqYi X-Yahoo-SMTP: WU.IBxeswBAAnLcBZV3tEZIK0A-- Received: by nuvolo.localdomain (Postfix, from userid 1001) id 37D491AF109; Tue, 18 Oct 2016 17:27:15 +0200 (CEST) Date: Tue, 18 Oct 2016 17:27:15 +0200 From: Arrigo Marchiori To: freebsd-fs@freebsd.org Subject: Random truncated files on USB hard disk with timeouts; how to debug? Message-ID: <20161018152715.GC89691@nuvolo> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.7.0 (2016-08-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 15:30:08 -0000 Hello List, I am encountering a strange problem, that happens seldom and randomly, and I don't know how to address it. Short description: some files sometimes become ``sort of truncated'': ls(1) tells me their size is not zero, but cat(1), less(1) and vi(1) show they are empty. The system is a 11-0 STABLE amd64, r307550, with GENERIC kernel. CPU: Intel Core 2 Duo. Ram: 2 GB. The root filesystem is mounted from a USB hard drive, with MBR partitioning scheme, formatted with ufs, SU+J enabled. The USB hard drive occasionally times out for ~10 seconds. But I do not see any warning or error messages in dmesg, that suggest that such timeouts could lead to broken files. In fact, dmesg(8) does not show anything at all about those timeouts, without tweaking the standard kernel verbosity options. If I set hw.usb.ehci.debug to 1, then I see ehci_timeout indications. If I set the sysctl to any bigger value, the console is flooded by messages. The problem appears while the computer is under heavy load: building world or ports. When this problem appears, the compilations stop with funny errror messages: the source files are empty!... Running truss(1) on cat(1) shows that the read(2) library function returns 0 bytes. I tried to disable journaling, but the problem still appears, apparently with the same frequency. Once the problem appears, I can reboot the system normally. I see no errors either during shutdown and the next startup. The filesystem is considered clean, and no fsck is run (BTW I disabled background fsck). The funny part is that after rebooting, the file contents are visible! I can resume the port compilation as if nothing ever happened. What can I do to get more information on this problem? Is there a well-known stress test I could run to exploit this problem more frequently? I am considering this a big problem, because I have no indications from the system logs that anything is going bad. If the HDD was broken, I would expect the kernel to yell it loud and often. Please add me in cc, as I am not subscribed to this list. Thank you in advance! -- rigo http://rigo.altervista.org From owner-freebsd-fs@freebsd.org Tue Oct 18 17:09:39 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7DE3DC17E8E for ; Tue, 18 Oct 2016 17:09:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6AC128E5 for ; Tue, 18 Oct 2016 17:09:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9IH9dsH081212 for ; Tue, 18 Oct 2016 17:09:39 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 90815] [smbfs] [patch] SMBFS with character conversions sometimes hangs Date: Tue, 18 Oct 2016 17:09:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 6.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ae@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 17:09:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D90815 --- Comment #8 from Andrey V. Elsukov --- (In reply to Tomoaki AOKI from comment #6) > (In reply to Andrey V. Elsukov from comment #5) >=20 > With my patch, if smb_copy_iconv() is called recursively, you're right. > If not, my patch can be better, as whole src is kept unchanged if > iconv_conv() returns -1. >=20 > *According to the prototype of iconv_conv() in src/sys/sys/iconv.h, > src is constant, so shouldn't be changed at all by iconv_conv(). >=20 > With my patch, if modified code path is executed, cp would copy with > original filename unchanged and succeeds, while with yours the file is > skipped. mb_put_mem() can allocate new mbuf and link it with existent. Imagine that = one mbuf will be not enough to store converted name. In such case smb_copy_icon= v() will be called several times for one name (to convert parts of name stored = in different mbufs). So, it is possible, that first part will be converted correctly, but second call will fail. In such case I think it is not correc= t to just copy part of name as is. But I don't know how real this scenario can be :) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Oct 18 17:43:53 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D93A1C17970 for ; Tue, 18 Oct 2016 17:43:53 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id A3A46651 for ; Tue, 18 Oct 2016 17:43:53 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id E5745273C2; Tue, 18 Oct 2016 17:43:45 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u9IHhiUK051998; Tue, 18 Oct 2016 17:43:44 GMT (envelope-from phk@phk.freebsd.dk) To: Arrigo Marchiori , Arrigo Marchiori via freebsd-fs Subject: Re: Random truncated files on USB hard disk with timeouts; how to debug? In-reply-to: <20161018152715.GC89691@nuvolo> From: "Poul-Henning Kamp" References: <20161018152715.GC89691@nuvolo> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <51996.1476812624.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Tue, 18 Oct 2016 17:43:44 +0000 Message-ID: <51997.1476812624@critter.freebsd.dk> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2016 17:43:53 -0000 -------- In message <20161018152715.GC89691@nuvolo>, Arrigo Marchiori via freebsd-f= s wri tes: >The USB hard drive occasionally times out for ~10 seconds. = When you say "hard drive" do you mean actually rotating platters or do you mean a flash-based device ? -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= . From owner-freebsd-fs@freebsd.org Wed Oct 19 06:20:10 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD1FFC185B1 for ; Wed, 19 Oct 2016 06:20:10 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 58DAA18C for ; Wed, 19 Oct 2016 06:20:10 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id z189so31210874wmb.1 for ; Tue, 18 Oct 2016 23:20:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=SWMi3vgzpniuKlOO1mUVTIh1sl8QtjfPE1EjEkn6RMM=; b=KtAIzWiCofR2tmuWwFyafJ4AKYUqDP7WUSoDrcSA5FDHGB8GUaDFNGKMCkl8fjywfy +Ru3CCWDvNi6cHye6VML5fueKVYqXU/pb83RdTFZSmHLWlTshL+Z/xXmn/us0+uPRhHI an9B4hvVpCnTXCrQf5xev37Jl9pA+3XqurK+2S5oQfi0uuXxiVPJuZ+qLwcjqVa1pTSu PJnSAeoqhJCA/YmrgiMjmLsyBwgoYRRta1Gau/dJTzRYspkvEfMx9B3lLZ5+Q/T98doP 52sLeB8nSF2MKEe85NssGwJYmKucwWpJoJpP1VbBVtqkyTRwlItl9slflMZ4gzLq9x+k x/kA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=SWMi3vgzpniuKlOO1mUVTIh1sl8QtjfPE1EjEkn6RMM=; b=gwO+kvM3OTfuVrmZbLZTJeBcwrNS3c99RLuKAv3o9mpDhd8uWRTRqkGBBp9kHzjC7B dJ0g5wYlDYzXS8x0Thw7B0cdVutQSdr/jEQY5kXVQTw5a1rL2rSqYqdZI4l4bMlVVVYD AwU11dU093VYPOET4fFx5ouDyk9CeRBv3r/iV0JZJbpHcPHtUFZCQhrGZAuZ04Nlx+ej 5jD2U7ftnwOJlKPD4+PRPgLnzxD678t/kZT1uYzMAxoClz2/+wQdLRx+bIrrfZu2kWCK /kLidQsGlpHR0oQqgIvZmlsnsdTWLChdNVkEvG8yEhem9EmuyLCYIKIqPRBaH6sdqRJv U+bg== X-Gm-Message-State: AA6/9Rm39+QZJqRGq+/j7gvDv1iqRRjDQX+gsDARAaZ/tVOU3Pph++i6oVdUzsVabkQ1xQ== X-Received: by 10.28.15.202 with SMTP id 193mr3883729wmp.62.1476858008594; Tue, 18 Oct 2016 23:20:08 -0700 (PDT) Received: from macbook-air-de-benjamin.home (LFbn-1-7159-4.w90-116.abo.wanadoo.fr. [90.116.90.4]) by smtp.gmail.com with ESMTPSA id n68sm3177871wmn.1.2016.10.18.23.20.07 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 18 Oct 2016 23:20:07 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Recommended HBA for ZFS, contemporary From: Ben RUBSON In-Reply-To: <376FE1E5-42BD-4878-8441-DA912E4ECB5B@gmail.com> Date: Wed, 19 Oct 2016 08:20:09 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <70B75F18-056B-49E5-9CDE-E8CCEA405CE8@gmail.com> References: <306ccab3-4c78-751a-2258-54701a64ab4b@internetx.com> <41DE4DAA-B5E1-4BB9-AF54-780236A901EF@gmail.com> <059af3ed-71b3-b31d-893c-732121989cee@kateley.com> <633311CF-ADF2-479F-AFB9-E9265C101302@gmail.com> <376FE1E5-42BD-4878-8441-DA912E4ECB5B@gmail.com> To: FreeBSD FS X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 06:20:10 -0000 Any feedback ? Many thanks ! Ben > On 13 Oct 2016, at 10:53, Ben RUBSON wrote: >=20 > What would you recommend for those who want a 12Gb/s SAS HBA ? > LSI 3008 ? > As reliable as LSI 2008 ? >=20 > Thank you ! >=20 > Ben >=20 >=20 >=20 >> On 22 Aug 2016, at 18:14, InterNetX - Juergen Gotteswinter = wrote: >>=20 >> LSI SAS 2008 Based HBA, there are dozens of OEM available for Budget = Prices >> With the IT firmware. >>=20 >> Am 22.08.2016 um 18:08 schrieb Dmitry Morozovsky: >>> Dear colleagues, >>>=20 >>> what is the list of preferred disk controllers to build storage = server, say >>> 12-24 amd more 3.5" disks? Not too much IOPS are expected, and some = could be >>> mitigated with L2ARC with only metadata cached, I suppose. >>>=20 >>> Two usage schemes are file server for big files (mostly cold = storage) and >>> backup/surveillance server (constant stream writes, occasional = random reads) >>>=20 >>> Any hints? Thanks! From owner-freebsd-fs@freebsd.org Wed Oct 19 06:24:52 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4504AC1870C for ; Wed, 19 Oct 2016 06:24:52 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F14FA6C0 for ; Wed, 19 Oct 2016 06:24:51 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: by mail-vk0-x22c.google.com with SMTP id q126so18462959vkd.2 for ; Tue, 18 Oct 2016 23:24:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=icUQMLnt5F9nLMhf3w1w3xXXYenk267ROIm9I4kJRnM=; b=gI9TespAFKVSGiZiYg39QPesNYgd35FnfijBQW+WtcE0aGbNEUt/aSYlLYXg2qynMK mnMwPp7/DGTulQCi6jVzhe0nszF+ysA2mgwTQ4rbDIr5H5Mf4ByxsIguf2pVy4nBxoyB FGSfiLqRd35r+3k/AG3cBuHhk4Re365VsuBJshKXZ+UsECc1jsdJAV3UbC2eAqd4WJzI hqdfbLUljj0uHSXEuXDuj9WoIHlW6LqoklkNCxpcvd9YbbXw0coLcwVXrpP6wRTPtIHN ZWzibHXQvmJBBZHbfnZTovRvQtvfHQqftfN4yR1mu58ndAgktR2jIPPeNYp+Mc+RqddG 97ag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=icUQMLnt5F9nLMhf3w1w3xXXYenk267ROIm9I4kJRnM=; b=ZafHPkPRbN6v65laco9MEkK+/ynZew6BLSBHPDKtGeXvo5RdxsSOM/OgTOLLN3aHMa H2FbumPmPV4/IzyKCVM5/ymvkgXPPQp/Im6maqS/nOHaeFCqNrSo3w8I3EZlWxe3zIP6 0/Z7Nu/8SVTHrVRCCNLkdT66VnV/5ec/dGKC0ihulS0w9q/WGsy87leWsFPE5TX+qppY wO0pNceUUppCk+FlBG7nh868JqXrP/pXl2xiiwW/7OjPSHOflEuxOC3saTBRxyDELEsY o3Q+QoXNhRnuM9Mm6R6QDUzBf8HOi1a6GhtgxQQo3pjHuHJBl3sEmZIsNqx3qyhLtnOd 17Bg== X-Gm-Message-State: AA6/9RkbmegDtbOGTdCOMBZrevIXCT1EnDroy3x4rxpCvMOzpomfhcdMdfDEwihaxoIAS5e/uIymFQw70qXOmg== X-Received: by 10.31.141.5 with SMTP id p5mr4257118vkd.136.1476858290863; Tue, 18 Oct 2016 23:24:50 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.72.141 with HTTP; Tue, 18 Oct 2016 23:24:49 -0700 (PDT) In-Reply-To: <70B75F18-056B-49E5-9CDE-E8CCEA405CE8@gmail.com> References: <306ccab3-4c78-751a-2258-54701a64ab4b@internetx.com> <41DE4DAA-B5E1-4BB9-AF54-780236A901EF@gmail.com> <059af3ed-71b3-b31d-893c-732121989cee@kateley.com> <633311CF-ADF2-479F-AFB9-E9265C101302@gmail.com> <376FE1E5-42BD-4878-8441-DA912E4ECB5B@gmail.com> <70B75F18-056B-49E5-9CDE-E8CCEA405CE8@gmail.com> From: Rich Date: Wed, 19 Oct 2016 02:24:49 -0400 Message-ID: Subject: Re: Recommended HBA for ZFS, contemporary To: freebsd-fs Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 06:24:52 -0000 AFAIK, the only two vendors in the space with 12Gb HBAs are PMC-Sierra and LSI/Avago. I can attest that the LSI 12Gb HBAs generally work as intended, though I can't attest to that specifically on FreeBSD. When I last looked at this, PMC's 12Gb HBAs weren't out yet, so I have no personal anecdata for you. - Rich On Wed, Oct 19, 2016 at 2:20 AM, Ben RUBSON wrote: > Any feedback ? > > Many thanks ! > > Ben > > > > > On 13 Oct 2016, at 10:53, Ben RUBSON wrote: > > > > What would you recommend for those who want a 12Gb/s SAS HBA ? > > LSI 3008 ? > > As reliable as LSI 2008 ? > > > > Thank you ! > > > > Ben > > > > > > > >> On 22 Aug 2016, at 18:14, InterNetX - Juergen Gotteswinter < > juergen.gotteswinter@internetx.com> wrote: > >> > >> LSI SAS 2008 Based HBA, there are dozens of OEM available for Budget > Prices > >> With the IT firmware. > >> > >> Am 22.08.2016 um 18:08 schrieb Dmitry Morozovsky: > >>> Dear colleagues, > >>> > >>> what is the list of preferred disk controllers to build storage > server, say > >>> 12-24 amd more 3.5" disks? Not too much IOPS are expected, and some > could be > >>> mitigated with L2ARC with only metadata cached, I suppose. > >>> > >>> Two usage schemes are file server for big files (mostly cold storage) > and > >>> backup/surveillance server (constant stream writes, occasional random > reads) > >>> > >>> Any hints? Thanks! > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@freebsd.org Wed Oct 19 06:28:23 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A8F6C18779 for ; Wed, 19 Oct 2016 06:28:23 +0000 (UTC) (envelope-from ardovm@yahoo.it) Received: from nm40-vm7.bullet.mail.ir2.yahoo.com (nm40-vm7.bullet.mail.ir2.yahoo.com [212.82.97.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7D7957A7 for ; Wed, 19 Oct 2016 06:28:21 +0000 (UTC) (envelope-from ardovm@yahoo.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.it; s=s2048; t=1476858494; bh=BiX2V52BVJn+4omHppXbRIQAGPoiPvCD4ru304NzlxY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From:Subject; b=IoxHJL2Ru9pAETpfu10tyFNo+Oo3m86l7MVAsKUJIfznOp0YUCgKuuW6pAUisX4KmsCPGsG18D4+Oc9EJmFVS4HwsI4cAOtVg5WB8ODOOk4wlESCFifHUDERdOROYTeZe6/dzuC/PndTfBX4hpBZOwPwC+UO6T1rOIU/R2k/GUXyZZxgVqhOKgGr1BbPrfDCJPNq8BXk5x5CV0MsCkJYiq24g+rNH4dDK49SU0ISW8mskpy9hgfE9qb0I2TL7TH9cliQd1g6IS6pmNVggsv899uegdOuL++NgQkors8PayyabXjQhGR35ZfoKNnb1wpieVaI+0pftZPqVboBfOIwTg== Received: from [212.82.98.58] by nm40.bullet.mail.ir2.yahoo.com with NNFMP; 19 Oct 2016 06:28:14 -0000 Received: from [46.228.39.107] by tm11.bullet.mail.ir2.yahoo.com with NNFMP; 19 Oct 2016 06:28:14 -0000 Received: from [127.0.0.1] by smtp144.mail.ir2.yahoo.com with NNFMP; 19 Oct 2016 06:28:14 -0000 X-Yahoo-Newman-Id: 185603.87791.bm@smtp144.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: DWnnSbAVM1nc4A9OT6ghCG8PuzJ_.iIe3QSCzn7JVgNKT1L XoHZ6uKm_SAQ_BBbZlCQaZGO2zT2zKSsScYe81nU2nbJnS90begeq6FNXues pb.mJjE6xDkQ.DBN1sXQ_LYZoqIdH9Eq1Fev6CYLWlTd5ato0VXmmMr_asvb .vnGjI4GDfpoqBLog6zM_oNfoRUIPYEwJsQ67UspDXH2h_bmuMMXdmnkGSO5 UgB7dDeta.PzYbhV1fBXkUj3EQ9vwlZrvI0HEtN_tp2.0kQgKoGZSXf2gBez I7pU7ALU8PZN0fPxBfE6IW6YANXxntBQcNLoh_eudcRgVL8szEX5G8KNmExt 6vRV.dblXxVkziLqv7haMEOB2S7Nwtdn9FnX5tCjIWidFNynVrnbtL70UJYK NNBWKwo6hnO9u8PWOC4_..r_yLwiaEXxO_hkAbZ_4_Cirtu.3plfQkPwdA5u Yc9zBAz8XpRRbV_sCGLi_FUGQXf1jI2LT4wKJ4mtEdi2cIdYwdmGegByadvl _ky1VgKYZN.KwX3XvuYsZwN2TAaFqLGP2TdeZ8z7C6__Ludeb X-Yahoo-SMTP: WU.IBxeswBAAnLcBZV3tEZIK0A-- Received: by nuvolo.localdomain (Postfix, from userid 1001) id 4C1681AF109; Wed, 19 Oct 2016 08:28:12 +0200 (CEST) Date: Wed, 19 Oct 2016 08:28:12 +0200 From: Arrigo Marchiori To: Poul-Henning Kamp Cc: Arrigo Marchiori via freebsd-fs Subject: Re: Random truncated files on USB hard disk with timeouts; how to debug? Message-ID: <20161019062812.GA93031@nuvolo> References: <20161018152715.GC89691@nuvolo> <51997.1476812624@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <51997.1476812624@critter.freebsd.dk> User-Agent: Mutt/1.7.0 (2016-08-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 06:28:23 -0000 Hello Poul, thank you for replying. On Tue, Oct 18, 2016 at 05:43:44PM +0000, Poul-Henning Kamp wrote: > -------- > In message <20161018152715.GC89691@nuvolo>, Arrigo Marchiori via freebsd-fs wri > tes: > > >The USB hard drive occasionally times out for ~10 seconds. > > When you say "hard drive" do you mean actually rotating platters > or do you mean a flash-based device ? It is a USB disk bought some years ago, that contains actually rotating platters. It has a Y-shaped cable, to get power from two ports. usbconfig(8) says: ----8<--------8<--------8<--------8<--------8<--------8<--------8<--------- ugen6.2: at usbus6, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (2mA) ----8<--------8<--------8<--------8<--------8<--------8<--------8<--------- And the relevant lines from dmesg(1) are the following (verbose boot): ----8<--------8<--------8<--------8<--------8<--------8<--------8<--------- ugen6.2: at usbus6 umass0 on uhub6 umass0: on usbus6 umass0: SCSI over Bulk-Only; quirks = 0x8100 umass0:4:0: Attached to scbus4 random: harvesting attach, 8 bytes (4 bits) from umass0 mountroot: waiting for device /dev/da0s2a... pass2 at umass-sim0 bus 0 scbus4 target 0 lun 0 pass2: Fixed Direct Access SCSI-2 device pass2: Serial Number 19CD0594134F pass2: 40.000MB/s transfers GEOM: new disk da0 da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number 19CD0594134F da0: 40.000MB/s transfers da0: 238475MB (488397168 512 byte sectors) da0: quirks=0x2 da0: Delete methods: ----8<--------8<--------8<--------8<--------8<--------8<--------8<--------- I hope this helps. Best regards, -- rigo http://rigo.altervista.org From owner-freebsd-fs@freebsd.org Wed Oct 19 06:33:24 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68249C189F6 for ; Wed, 19 Oct 2016 06:33:24 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 34CAFB11 for ; Wed, 19 Oct 2016 06:33:23 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 1A2AC273F6; Wed, 19 Oct 2016 06:33:22 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u9J6XLnb007760; Wed, 19 Oct 2016 06:33:21 GMT (envelope-from phk@phk.freebsd.dk) To: Arrigo Marchiori cc: Arrigo Marchiori via freebsd-fs Subject: Re: Random truncated files on USB hard disk with timeouts; how to debug? In-reply-to: <20161019062812.GA93031@nuvolo> From: "Poul-Henning Kamp" References: <20161018152715.GC89691@nuvolo> <51997.1476812624@critter.freebsd.dk> <20161019062812.GA93031@nuvolo> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7758.1476858801.1@critter.freebsd.dk> Date: Wed, 19 Oct 2016 06:33:21 +0000 Message-ID: <7759.1476858801@critter.freebsd.dk> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 06:33:24 -0000 -------- In message <20161019062812.GA93031@nuvolo>, Arrigo Marchiori writes: >It is a USB disk bought some years ago, that contains actually >rotating platters. It has a Y-shaped cable, to get power from two >ports. Y-cables are a big warning sign. You can try plugging the "power-only" plug into a high quality 1 ampere USB charger, but that is no guarantee for success. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-fs@freebsd.org Wed Oct 19 06:45:19 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B691C18D57 for ; Wed, 19 Oct 2016 06:45:19 +0000 (UTC) (envelope-from ardovm@yahoo.it) Received: from nm26-vm7.bullet.mail.ir2.yahoo.com (nm26-vm7.bullet.mail.ir2.yahoo.com [212.82.97.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7E58A5E2 for ; Wed, 19 Oct 2016 06:45:18 +0000 (UTC) (envelope-from ardovm@yahoo.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.it; s=s2048; t=1476859397; bh=lc2snpW1iuswNeXHlKM5kmNdqxRKUsBccfNLiyQ0k6k=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From:Subject; b=Bq+LjduA9wf+G8ajbc5Rs+uVO9rAwxnuXo7in8tGPG+OqAta7X3ZQH1nEi59wJHezFSy87Lxu6sRstGCf3xL3drsUFQWI74yfMqSHlnUxyGHL0d/D6nTYOfxcBkkHnGtLbGCRHS6r71OESsL3Igy/yprK8KckKdyDdLcvalWwuAhQR4DELsSWNGfUNBAuuW1SC4XD53/yIxRHnybAenRlkBZn/EF8rC8XGtw81q8CzD7WIJWn07p+vxYqkSWc6hsA7Jv5ZhqUZyb4i7+KyE9/GFVGnRbk4lNYWLWondW8AuXER4SrFxGcP05LHlEtdAtmCn1ggaY8r5l+oB4lob7bg== Received: from [212.82.98.50] by nm26.bullet.mail.ir2.yahoo.com with NNFMP; 19 Oct 2016 06:43:17 -0000 Received: from [46.228.39.80] by tm3.bullet.mail.ir2.yahoo.com with NNFMP; 19 Oct 2016 06:43:17 -0000 Received: from [127.0.0.1] by smtp117.mail.ir2.yahoo.com with NNFMP; 19 Oct 2016 06:43:17 -0000 X-Yahoo-Newman-Id: 464571.71886.bm@smtp117.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: rXFCcpcVM1nIOuzUy4Q_NzyWJPI_9dO3hb8vXFI0kOPIV3X OXaclh5kbydx8_ZrepQBtITgmdZ9jOkSBucxzFPCF6QP04fwMYOxmWT8bmrW VY16ItgMFDkHztPtKjIzCIveKbGklhsq1wGlXFIN6yEkROiNXjPRPv0zhYc1 9K31vvCA55rVmbeGOIsBGXFMsclUO4TZGw6SGYXJOoeXi0dvdAmKXd4vTbkt ojj5.jbH8EWgx.gwuRh5dSc1uQB1ydVHR98Ce4h.9yKxKgHq2Zai4srNvgaP 5IzhcYcFX_K8iRIUoom3aikSC.HljXF3BL88gIewAVTCXDBteoSmKi6nLfgZ LQGGhvUshvw4NI5gRMl3ftIo7pflbaIHxavTREUNUaVL2Kdtv_dEPlkS4Ndk 9nHGxkCPqc3WB6lUBA7wSUa2yBWn2mtHjIq4D1GCF6pzAxQK0qGTNlFCrqBK BaCJu4gVt8OjEFSyWxlH6JjZYG3I3_nc8gKPCoJWIJ4SBhhzk9TDCI7WxfOK DfLagV9UDQdP.GX_QZFP1gJ28lU2zpRMC_CNtRCXRc3L.TM2p X-Yahoo-SMTP: WU.IBxeswBAAnLcBZV3tEZIK0A-- Received: by nuvolo.localdomain (Postfix, from userid 1001) id EB6241AF109; Wed, 19 Oct 2016 08:43:15 +0200 (CEST) Date: Wed, 19 Oct 2016 08:43:15 +0200 From: Arrigo Marchiori To: Poul-Henning Kamp Cc: Arrigo Marchiori via freebsd-fs Subject: Re: Random truncated files on USB hard disk with timeouts; how to debug? Message-ID: <20161019064315.GB93031@nuvolo> References: <20161018152715.GC89691@nuvolo> <51997.1476812624@critter.freebsd.dk> <20161019062812.GA93031@nuvolo> <7759.1476858801@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <7759.1476858801@critter.freebsd.dk> User-Agent: Mutt/1.7.0 (2016-08-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 06:45:19 -0000 Hello Poul-Henning, On Wed, Oct 19, 2016 at 06:33:21AM +0000, Poul-Henning Kamp wrote: > -------- > In message <20161019062812.GA93031@nuvolo>, Arrigo Marchiori writes: > > >It is a USB disk bought some years ago, that contains actually > >rotating platters. It has a Y-shaped cable, to get power from two > >ports. > > Y-cables are a big warning sign. > > You can try plugging the "power-only" plug into a high quality 1 > ampere USB charger, but that is no guarantee for success. Yes, I also thought so at first. But I also believe that if anything goes wrong at the hardware level, I should get a big warning from the kernel, instead of a funny apparently-truncated file, that returns to be readable at next reboot...? This is only my humble opinion, of course. If there are any other assumptions that I should be following, please address me to the appropriate documentation! I think this occasion can be precious to find the missing piece, that could lead to the users getting advice _before_ they find out that some files are temporarily unreadable. Or maybe, even fixing this problem...? Best regards, -- rigo http://rigo.altervista.org From owner-freebsd-fs@freebsd.org Wed Oct 19 07:20:11 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0233CC16E39 for ; Wed, 19 Oct 2016 07:20:11 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FCA164A for ; Wed, 19 Oct 2016 07:20:10 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id z189so33596705wmb.1 for ; Wed, 19 Oct 2016 00:20:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=unSmzoWCRmSzAzeWEJVNERJoC7JNMcml5dOPqZ6B9Qk=; b=pM7hhgAJ3yacP+ZMF4rTQR3j42bc+FYY8pbDgzNrZjHGaq3HhnWIwK/uhVQbLHfbLK xn8rB6yBUV9lR0TOOKsgZPP1m9WBGUbcTrcVeoVyCvvhJIyxyG/rBwS1XN+ZHhDkPnzl dSQ3FDEcQSbVtkX99R5l2roq9wCSD3y2UjEiJYYNwldrnuSNJArCPdgHLmA+Urv4zg+N 7T3FxxLjePJx0nupymrcegrWz9vXAJZ6wSRCUe3EY9zpBVPN/CEji9J+efVP0iMpxgQI A/5YdidwGh6CY0X7cAf8iw4BeiFX1WhLSaU9JG0XpaMdRfUZ1gRykPnokgVpsUywFW7L hRRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=unSmzoWCRmSzAzeWEJVNERJoC7JNMcml5dOPqZ6B9Qk=; b=kap3wQeYrcJNtr0uj9GsY8+l5J5XBlZIhDPbEMT5CMIseJZ6FAGOOI2F4qUsjZeIAy 2PN5Yjv//VWOnPOtieB3enz3Ob5GdaxdPwH+2hDoTqUKI4AYyIIaO1TXLnzjALu2sPuk Znt3gWvjdLiYih7N2FbcWNoc1CrrPovx7mPziXmcImu+Yy2JnnqGc5SPdLu8FtPhCcnx eCnJfuadkd/0guLKLHekaXYPHr/OXzN74xCaf9tA5lqx7Fq11ZIaTAhYbhQTiwfsKMu/ lxfyEf6Aj7V5zf/NsgxT79xcTWwcd6sQP5cgvz0r5LM+8q9WHWs5EjzsLXw+j20jwB8e D/8w== X-Gm-Message-State: AA6/9Rk4NV1bfpjIiSmozVLc6kKMXeHBQnZQ055SDrcf6pIrP6bEgqEjp1S9nrp7k/GPlA== X-Received: by 10.194.203.6 with SMTP id km6mr3084576wjc.226.1476861608522; Wed, 19 Oct 2016 00:20:08 -0700 (PDT) Received: from macbook-air-de-benjamin.home (LFbn-1-7159-4.w90-116.abo.wanadoo.fr. [90.116.90.4]) by smtp.gmail.com with ESMTPSA id rv12sm67189723wjb.29.2016.10.19.00.20.07 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 19 Oct 2016 00:20:07 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Recommended HBA for ZFS, contemporary From: Ben RUBSON In-Reply-To: Date: Wed, 19 Oct 2016 09:20:06 +0200 Content-Transfer-Encoding: 7bit Message-Id: <2521A945-AB44-4ADF-80B2-03F528BA11B6@gmail.com> References: <306ccab3-4c78-751a-2258-54701a64ab4b@internetx.com> <41DE4DAA-B5E1-4BB9-AF54-780236A901EF@gmail.com> <059af3ed-71b3-b31d-893c-732121989cee@kateley.com> <633311CF-ADF2-479F-AFB9-E9265C101302@gmail.com> <376FE1E5-42BD-4878-8441-DA912E4ECB5B@gmail.com> <70B75F18-056B-49E5-9CDE-E8CCEA405CE8@gmail.com> To: freebsd-fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 07:20:11 -0000 Thank you Rich. I saw that the LSI 3008 can be put in IT mode, as with the well known 2008. Firmware & drivers seem to be well maintained, with a P13 release last month. 2 good points. However I did not found much much user feedback on it, nor recommandations. There should be no surprise compared to the 2008, but we never know... Ben > On 19 Oct 2016, at 08:24, Rich wrote: > > AFAIK, the only two vendors in the space with 12Gb HBAs are PMC-Sierra and > LSI/Avago. > > I can attest that the LSI 12Gb HBAs generally work as intended, though I > can't attest to that specifically on FreeBSD. > > When I last looked at this, PMC's 12Gb HBAs weren't out yet, so I have no > personal anecdata for you. > > - Rich > > On Wed, Oct 19, 2016 at 2:20 AM, Ben RUBSON wrote: > >> Any feedback ? >> >> Many thanks ! >> >> Ben >> >> >> >>> On 13 Oct 2016, at 10:53, Ben RUBSON wrote: >>> >>> What would you recommend for those who want a 12Gb/s SAS HBA ? >>> LSI 3008 ? >>> As reliable as LSI 2008 ? >>> >>> Thank you ! >>> >>> Ben >>> >>> >>> >>>> On 22 Aug 2016, at 18:14, InterNetX - Juergen Gotteswinter < >> juergen.gotteswinter@internetx.com> wrote: >>>> >>>> LSI SAS 2008 Based HBA, there are dozens of OEM available for Budget >> Prices >>>> With the IT firmware. >>>> >>>> Am 22.08.2016 um 18:08 schrieb Dmitry Morozovsky: >>>>> Dear colleagues, >>>>> >>>>> what is the list of preferred disk controllers to build storage >> server, say >>>>> 12-24 amd more 3.5" disks? Not too much IOPS are expected, and some >> could be >>>>> mitigated with L2ARC with only metadata cached, I suppose. >>>>> >>>>> Two usage schemes are file server for big files (mostly cold storage) >> and >>>>> backup/surveillance server (constant stream writes, occasional random >> reads) >>>>> >>>>> Any hints? Thanks! From owner-freebsd-fs@freebsd.org Wed Oct 19 07:22:22 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E5BC2C16FFE for ; Wed, 19 Oct 2016 07:22:22 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id B226EA31 for ; Wed, 19 Oct 2016 07:22:22 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id 650112740A; Wed, 19 Oct 2016 07:22:21 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u9J7MICW007925; Wed, 19 Oct 2016 07:22:20 GMT (envelope-from phk@phk.freebsd.dk) To: Arrigo Marchiori cc: Arrigo Marchiori via freebsd-fs Subject: Re: Random truncated files on USB hard disk with timeouts; how to debug? In-reply-to: <20161019064315.GB93031@nuvolo> From: "Poul-Henning Kamp" References: <20161018152715.GC89691@nuvolo> <51997.1476812624@critter.freebsd.dk> <20161019062812.GA93031@nuvolo> <7759.1476858801@critter.freebsd.dk> <20161019064315.GB93031@nuvolo> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <7923.1476861738.1@critter.freebsd.dk> Date: Wed, 19 Oct 2016 07:22:18 +0000 Message-ID: <7924.1476861738@critter.freebsd.dk> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 07:22:23 -0000 -------- In message <20161019064315.GB93031@nuvolo>, Arrigo Marchiori writes: >> Y-cables are a big warning sign. >> >> You can try plugging the "power-only" plug into a high quality 1 >> ampere USB charger, but that is no guarantee for success. > >Yes, I also thought so at first. > >But I also believe that if anything goes wrong at the hardware level, >I should get a big warning from the kernel, instead of a funny >apparently-truncated file, that returns to be readable at next >reboot...? Only if the drive finds out something is wrong and tells the kernel. If the drive has bad power supply, that may not happen. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-fs@freebsd.org Wed Oct 19 07:56:15 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28680C17CA3 for ; Wed, 19 Oct 2016 07:56:15 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D26053E8 for ; Wed, 19 Oct 2016 07:56:14 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: by mail-ua0-x236.google.com with SMTP id r64so4821138uar.2 for ; Wed, 19 Oct 2016 00:56:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=fau4myTicj5dMmEE7B7z5AE/zAhPdSIQDAJinhX4ebM=; b=EGMbb2Ff/aQ6cshS937beoCIZ/HoG+0Fro0FOYs5BbieuRe8d211sO449Z7mXy3fke rsrr2smM9fLSwixV5Xn9zpNYSFZ5/cas96yMXHBuNzzSGEN52EgwaWJEyzC5CvD0bYSr MXoaIV60HxPtXDXY8sdgfgAMdC27u1faKT9/JjTuCT9qpPOf5J3u8xlXFJoYFo9g19Zu D0CV8l0NxDrZGSOVgR3HpVj/HLfD926SATXHVcX+oZhppH9vxIJj10jAAOO0lrq2KhCM gWAKJJFBt5d2iBvnPapZosIfrWcEznlD7q4erAQ36JA+WFOgYQ8Etus15DjJwLkGo/wA YsRA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=fau4myTicj5dMmEE7B7z5AE/zAhPdSIQDAJinhX4ebM=; b=KmHUbHsGOI1JGXD/qKHepWXUNLsL+AMOmVaPTv4lIrEVy6+GswNZC9GR4hwCvRhZoS 4oyCQeITuVhF5Toeep3fYFEbMqIEKIUqAJONHDGyitwneyiGCNNs0iU6CGFT8WPnIq07 jdS/dcREAWLOI55gnH7zsYcNmsnNke3lsvkF8t8tVBfv7Jq5NPLkZeX4csE94hXlOnzn y6TvG04hG1oiyaP8pQAVlubMckocAPLiNCQu7dmNzccZNRbt9S9HVpZC21js7lGdrQWI Y16Pvwyu6XPAe5Uc2lNcM4vNKBzZDGN2xsRHWBMiaolsDAdF930A85USQ0kXsDt38Yme vwFQ== X-Gm-Message-State: AA6/9RmXpTng3IwZJhAw9gNfJZRBix8fc4OXbmKyPvbP03zHp+/fwbgoSaQEoM6YjsqnJgsAw0O+RWwujZKR1Q== X-Received: by 10.176.1.174 with SMTP id 43mr1185005ual.55.1476863773761; Wed, 19 Oct 2016 00:56:13 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.72.141 with HTTP; Wed, 19 Oct 2016 00:56:12 -0700 (PDT) In-Reply-To: <2521A945-AB44-4ADF-80B2-03F528BA11B6@gmail.com> References: <306ccab3-4c78-751a-2258-54701a64ab4b@internetx.com> <41DE4DAA-B5E1-4BB9-AF54-780236A901EF@gmail.com> <059af3ed-71b3-b31d-893c-732121989cee@kateley.com> <633311CF-ADF2-479F-AFB9-E9265C101302@gmail.com> <376FE1E5-42BD-4878-8441-DA912E4ECB5B@gmail.com> <70B75F18-056B-49E5-9CDE-E8CCEA405CE8@gmail.com> <2521A945-AB44-4ADF-80B2-03F528BA11B6@gmail.com> From: Rich Date: Wed, 19 Oct 2016 03:56:12 -0400 Message-ID: Subject: Re: Recommended HBA for ZFS, contemporary To: freebsd-fs Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 07:56:15 -0000 Well, the 2008 has been around for at least 7 years (if not longer, just guessing from the oldest FW on LSI's site), and the 3008 came out only 3 years ago. One of the reasons the 2008 is so well-known is that it, and its cousins the 2[123]08, have ended up in a great many platforms and rebranded cards by other people - on motherboards, Dell's "6Gbps SAS HBA" cards, [...] They've been around so long that things like the 9220-8i (the infamous IBM ServeRAID M1015) and friends, which aren't the 2008 but are close enough if you squint, are dirt-cheap secondhand compared to the price of a new 9211-8i or 9311-8i. The other difference is, there's not an obvious flaw in the 2008 and friends that you need to buy the 3008 to fix. The LSI 1068E and friends can't do drives over 2T, so you needed at least the 2008 for 3T drives. There's no such incompatibility visible in the 2008/3008 distinction that anyone's noticed yet. Maybe when we get to another fun LBA count boundary (512 TB seems promising), we'll see serious pressure. Otherwise, the 2008 is generally "good enough" for the long tail of people that make up the majority of online posts about things. - Rich On Wed, Oct 19, 2016 at 3:20 AM, Ben RUBSON wrote: > Thank you Rich. > > I saw that the LSI 3008 can be put in IT mode, as with the well known 2008. > Firmware & drivers seem to be well maintained, with a P13 release last > month. > 2 good points. > > However I did not found much much user feedback on it, nor recommandations. > There should be no surprise compared to the 2008, but we never know... > > Ben > > > On 19 Oct 2016, at 08:24, Rich wrote: > > > > AFAIK, the only two vendors in the space with 12Gb HBAs are PMC-Sierra > and > > LSI/Avago. > > > > I can attest that the LSI 12Gb HBAs generally work as intended, though I > > can't attest to that specifically on FreeBSD. > > > > When I last looked at this, PMC's 12Gb HBAs weren't out yet, so I have no > > personal anecdata for you. > > > > - Rich > > > > On Wed, Oct 19, 2016 at 2:20 AM, Ben RUBSON > wrote: > > > >> Any feedback ? > >> > >> Many thanks ! > >> > >> Ben > >> > >> > >> > >>> On 13 Oct 2016, at 10:53, Ben RUBSON wrote: > >>> > >>> What would you recommend for those who want a 12Gb/s SAS HBA ? > >>> LSI 3008 ? > >>> As reliable as LSI 2008 ? > >>> > >>> Thank you ! > >>> > >>> Ben > >>> > >>> > >>> > >>>> On 22 Aug 2016, at 18:14, InterNetX - Juergen Gotteswinter < > >> juergen.gotteswinter@internetx.com> wrote: > >>>> > >>>> LSI SAS 2008 Based HBA, there are dozens of OEM available for Budget > >> Prices > >>>> With the IT firmware. > >>>> > >>>> Am 22.08.2016 um 18:08 schrieb Dmitry Morozovsky: > >>>>> Dear colleagues, > >>>>> > >>>>> what is the list of preferred disk controllers to build storage > >> server, say > >>>>> 12-24 amd more 3.5" disks? Not too much IOPS are expected, and some > >> could be > >>>>> mitigated with L2ARC with only metadata cached, I suppose. > >>>>> > >>>>> Two usage schemes are file server for big files (mostly cold storage) > >> and > >>>>> backup/surveillance server (constant stream writes, occasional random > >> reads) > >>>>> > >>>>> Any hints? Thanks! > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@freebsd.org Wed Oct 19 08:03:00 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF097C18132 for ; Wed, 19 Oct 2016 08:03:00 +0000 (UTC) (envelope-from ardovm@yahoo.it) Received: from nm5-vm9.bullet.mail.ir2.yahoo.com (nm5-vm9.bullet.mail.ir2.yahoo.com [212.82.96.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6D37DB50 for ; Wed, 19 Oct 2016 08:03:00 +0000 (UTC) (envelope-from ardovm@yahoo.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.it; s=s2048; t=1476864006; bh=9vosDVVzf2SOP3QlxRtjGdds7f+XxcqjFaDbal+y45M=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From:Subject; b=GLmEZsb2oVbfzrd3l615qB8L6b4p7RXiCerpdo6dUj5xpy9P1xIuzzrd+v7KOADB0LG7em99wJ7IFgAVUPP19QHCA9XxoLs2r/yaT1IL3JjM+QfXzYMOU3GZKubB+C0/Bu2A+RvJGo/DMOLiLZ59tgUS0S0gZWdV7EkOH/5uRpXNHGuquQp48C8m3C0kcyE1SVXY5+ia9mXFq3lsAGfRMgi9ljT5sxbSU3DsMr9ErOCo8FrRjVSrCoKSPlmtMHx9jVoGHqU8Orqi9QqIgNK/xRaa4woJfkgI6+crd9UvfNeKGpl4vSDxhNJaoP+iBsQabeZm9vyJZzyqG7Du/8uzvA== Received: from [212.82.98.53] by nm5.bullet.mail.ir2.yahoo.com with NNFMP; 19 Oct 2016 08:00:06 -0000 Received: from [46.228.39.85] by tm6.bullet.mail.ir2.yahoo.com with NNFMP; 19 Oct 2016 08:00:06 -0000 Received: from [127.0.0.1] by smtp122.mail.ir2.yahoo.com with NNFMP; 19 Oct 2016 08:00:06 -0000 X-Yahoo-Newman-Id: 957286.50208.bm@smtp122.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: AbmggVcVM1kvYkKbj7Fq0HJli1J936_mLhCcOEd2aaOleE0 pMOOU52F.lTR3eLcwRQHUkn8yP5.5Hxqaw_qNdZo2m1pslYaOXpOvv7cx9sw WXlasVNHflsyaJyPTZPbK1bOuMzqheebeJ6.ROVBp5pzrR9C7jVVqWL7fEbQ 7Gs75pNWIn9f4hKY.WFea.uEMy2.kt01M6i60G01zck9lVfOq3odI0.rFSAk b7e.czuXWP47SGcMWDrcXidk2eSPaWMhqhGtSGGWXEG6zolFTfcJWxOF_dUj F54CmYDQIyEenxNNp8leSrDbnp7w0w69piFvTS5999WdRQiKXMcFjDFN.Y6e 8d1bjAcPC6tYvM53H9OM.Wy.NQmGURWuKLfJZp69e38CDCTPdIvzG17fQ2pX 7VQPI4mZRO2DLPqz94A6Yb_HnrrCPkOiFyAV.0XflCqRduhA.6KNdsqYG0MW NAdspcHGC3x4lC0pSpBi4tRtjBAPoduZaaOzrZVYQLB.uwBfj0Uz9iLPAv52 XdOJauKKJeE9Sj63ynHbBRdpUPjZRd3oskEDKtsSbCT__GFh7 X-Yahoo-SMTP: WU.IBxeswBAAnLcBZV3tEZIK0A-- Received: by nuvolo.localdomain (Postfix, from userid 1001) id 10AFA1AF109; Wed, 19 Oct 2016 10:00:05 +0200 (CEST) Date: Wed, 19 Oct 2016 10:00:05 +0200 From: Arrigo Marchiori To: Poul-Henning Kamp Cc: Arrigo Marchiori via freebsd-fs Subject: Re: Random truncated files on USB hard disk with timeouts; how to debug? Message-ID: <20161019080005.GD93031@nuvolo> References: <20161018152715.GC89691@nuvolo> <51997.1476812624@critter.freebsd.dk> <20161019062812.GA93031@nuvolo> <7759.1476858801@critter.freebsd.dk> <20161019064315.GB93031@nuvolo> <7924.1476861738@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <7924.1476861738@critter.freebsd.dk> User-Agent: Mutt/1.7.0 (2016-08-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 08:03:01 -0000 Hello Poul-Henning, On Wed, Oct 19, 2016 at 07:22:18AM +0000, Poul-Henning Kamp wrote: > -------- > In message <20161019064315.GB93031@nuvolo>, Arrigo Marchiori writes: > > >> Y-cables are a big warning sign. > >> > >> You can try plugging the "power-only" plug into a high quality 1 > >> ampere USB charger, but that is no guarantee for success. > > > >Yes, I also thought so at first. > > > >But I also believe that if anything goes wrong at the hardware level, > >I should get a big warning from the kernel, instead of a funny > >apparently-truncated file, that returns to be readable at next > >reboot...? > > Only if the drive finds out something is wrong and tells the kernel. > > If the drive has bad power supply, that may not happen. Yes, I understand. But, forgive me for insisting: there is an inconsistency that is _at filesystem level_ and _temporary_, and this really puzzles me. If there was an undetected problem when writing, I would expect garbage to be written instead of the actual data. Or, no data at all. But the outcome should be that such data should be _unrecoverable_ afterwards. Instead, the file is found and probably correct at next reboot! Last one was a Java source file; if it had errors internally I would have expected the port not to compile. If there was a problem when reading, should the kernel not detect an inconsistency in the data? Like a failed checksum? Because I think it does: read(2) returns zero bytes, not garbage. It just happened now, that another compilation filed. I cleaned, repeated and it worked, without need to reboot. So, the ``funny'' file seems to be deletable. Please correct me if I am wrong. And thank you for your replies so far! Best regards, -- rigo http://rigo.altervista.org From owner-freebsd-fs@freebsd.org Wed Oct 19 11:26:25 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8FA00C18AE5 for ; Wed, 19 Oct 2016 11:26:25 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 5988BB08 for ; Wed, 19 Oct 2016 11:26:25 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id D1C01273B2; Wed, 19 Oct 2016 11:26:23 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id u9JBQMcH023736; Wed, 19 Oct 2016 11:26:23 GMT (envelope-from phk@phk.freebsd.dk) To: Arrigo Marchiori cc: Arrigo Marchiori via freebsd-fs Subject: Re: Random truncated files on USB hard disk with timeouts; how to debug? In-reply-to: <20161019080005.GD93031@nuvolo> From: "Poul-Henning Kamp" References: <20161018152715.GC89691@nuvolo> <51997.1476812624@critter.freebsd.dk> <20161019062812.GA93031@nuvolo> <7759.1476858801@critter.freebsd.dk> <20161019064315.GB93031@nuvolo> <7924.1476861738@critter.freebsd.dk> <20161019080005.GD93031@nuvolo> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <23734.1476876382.1@critter.freebsd.dk> Date: Wed, 19 Oct 2016 11:26:22 +0000 Message-ID: <23735.1476876382@critter.freebsd.dk> X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 11:26:25 -0000 -------- In message <20161019080005.GD93031@nuvolo>, Arrigo Marchiori writes: >> If the drive has bad power supply, that may not happen. > >Yes, I understand. But, forgive me for insisting: there is an >inconsistency that is _at filesystem level_ and _temporary_, and this >really puzzles me. Because the drive returns wrong data every so often and when power is better returns correct data ? End-to-End arguments in system design applies here: Either you trust your drive, or you check everything it tells you (ie: RAID with parity, ZFS or similar). The only middle way is prayer. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-fs@freebsd.org Wed Oct 19 13:12:52 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0ADC7C17C4A for ; Wed, 19 Oct 2016 13:12:52 +0000 (UTC) (envelope-from ardovm@yahoo.it) Received: from nm3-vm3.bullet.mail.ir2.yahoo.com (nm3-vm3.bullet.mail.ir2.yahoo.com [212.82.96.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 96590819 for ; Wed, 19 Oct 2016 13:12:51 +0000 (UTC) (envelope-from ardovm@yahoo.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.it; s=s2048; t=1476882623; bh=HTUDES9BOPQw0P7AEyvzG5W0k44eKRMdmO6GA5K7loM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From:Subject; b=E2nY88dwK2oCMT+nUswZUN8rWx/jzScT1dzEGKUM84vZPHvNUtenfJL3G73zQljWmW4Ak/7T4h6VnDPYApHPTDBcpAiLqYcSSRkk2zfcS4jxi8zTWna4gBxSLA33JFz+JoxEh8RNIxY7CM6AYxIHtigeuzCq3ORbJwM6259xP6Vx5awxQovKCmNimi7GQLrr89oe4saIa8fMBkPtXA3mV40GOOm2OJ8JmRw+HIIbXOCqIxMrDhYjhAkWO/fwb52tAsM0zt8nU64lT1iaL9kAeLOdO4nY7GK5/7/I6fFYyyitwbtg9ueIPffAfJa+MBba15rVSMQAvMmKAuAcAVE3eg== Received: from [212.82.98.49] by nm3.bullet.mail.ir2.yahoo.com with NNFMP; 19 Oct 2016 13:10:23 -0000 Received: from [46.228.39.93] by tm2.bullet.mail.ir2.yahoo.com with NNFMP; 19 Oct 2016 13:10:23 -0000 Received: from [127.0.0.1] by smtp130.mail.ir2.yahoo.com with NNFMP; 19 Oct 2016 13:10:23 -0000 X-Yahoo-Newman-Id: 953490.63995.bm@smtp130.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: Y2bN3rQVM1mAqBFGUAEC.FjwGqcaV4sP19AFmt_a22E1rJJ 4VWk8wpDM5lKqbawaoDDglZpPeUBV5Z0mN4DNPiAisuIatUdt2Ki4XUuVBqM 69bhrZo7B9DF32tvg_Qw5xbj7IyB0DWOdLKLmJY_xY4klcAaHClS2KykmgIu NRYlvyFyiNKrCXhcSBxjlShXs6s22Ebn_fzoebgwTTzXii9XD4q0YLNCugYY X2qNz0CqIC66bu7wy44MEUv_gsZJ5OEGgNU8PXKJek.gb_1AC395FBbHmpKP o9_GuCj322mKZqnIhioYSqoB5uw2clSLF.XJGEuEWdQxeu9QzwWYC4ZIjUFV oYLzQm8m5K3Bo5wseclxTLkaVI_qpc2gDynhNG8Ot42JY.4MYCUwYCXViHuy K77jZhJdbYYrgdq3FTLmr5rJ9bpPGx3Gsac7Py57iFgF8mPEohX537BRQr6J Ntn.vvdSJ7YeFn3va5tiSKhLpgtHLWYjW.sDYjgyk5iFw5WJbBuOFD0RF0Hg lHWRtY8ag4IvGUyvKlxb5oopYxExkwuH0f3BOty41Qp_UtdvS X-Yahoo-SMTP: WU.IBxeswBAAnLcBZV3tEZIK0A-- Received: by nuvolo.localdomain (Postfix, from userid 1001) id 6A2501AF109; Wed, 19 Oct 2016 15:10:22 +0200 (CEST) Date: Wed, 19 Oct 2016 15:10:22 +0200 From: Arrigo Marchiori To: Poul-Henning Kamp Cc: Arrigo Marchiori via freebsd-fs Subject: Re: Random truncated files on USB hard disk with timeouts; how to debug? Message-ID: <20161019131022.GE93031@nuvolo> References: <20161018152715.GC89691@nuvolo> <51997.1476812624@critter.freebsd.dk> <20161019062812.GA93031@nuvolo> <7759.1476858801@critter.freebsd.dk> <20161019064315.GB93031@nuvolo> <7924.1476861738@critter.freebsd.dk> <20161019080005.GD93031@nuvolo> <23735.1476876382@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <23735.1476876382@critter.freebsd.dk> User-Agent: Mutt/1.7.0 (2016-08-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 13:12:52 -0000 Hello Poul-Henning, On Wed, Oct 19, 2016 at 11:26:22AM +0000, Poul-Henning Kamp wrote: > -------- > In message <20161019080005.GD93031@nuvolo>, Arrigo Marchiori writes: > > >> If the drive has bad power supply, that may not happen. > > > >Yes, I understand. But, forgive me for insisting: there is an > >inconsistency that is _at filesystem level_ and _temporary_, and this > >really puzzles me. > > Because the drive returns wrong data every so often and when > power is better returns correct data ? > > End-to-End arguments in system design applies here: > > Either you trust your drive, or you check everything it tells you > (ie: RAID with parity, ZFS or similar). Ok, but I cannot understand why read() returns plain zero bytes. If ``bad'' data was received from a USB read operation, it should just not make sense to the kernel. Not just show up as an empty file?... Wile fiddling with a funny file, I found that read(2) and mmap(2) behave differently. While cat(1) shows an empty file, cp(1) was able to read its contents. The file was in fact /usr/src/usr.bin/clang/clang/clang.1, the source of the clang(1) manual page. On the other hand, mv(1) does not alter the ``readability'' of the file. # mv clang.1 a # truss cat a [snip] openat(AT_FDCWD,"a",O_RDONLY,00) = 3 (0x3) fstat(1,{ mode=crw--w---- ,inode=146,size=0,blksize=4096 }) = 0 (0x0) __sysctl(0x7fffffffe5e0,0x2,0x7fffffffe5c4,0x7fffffffe5c8,0x0,0x0) = 0 (0x0) __sysctl(0x7fffffffe5e0,0x2,0x7fffffffe5c4,0x7fffffffe5c8,0x0,0x0) = 0 (0x0) mmap(0x0,2097152,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = 34374418432 (0x800e00000) read(3,0x800e16000,4096) = 0 (0x0) close(3) = 0 (0x0) [snip] # Truss cp a b [snip] stat("b",0x7fffffffe9d8) ERR#2 'No such file or directory' lstat("a",{ mode=-rw-r--r-- ,inode=6510202,size=16993,blksize=32768 }) = 0 (0x0) umask(0x1ff) = 18 (0x12) umask(0x12) = 511 (0x1ff) mmap(0x0,2097152,PROT_READ|PROT_WRITE,MAP_PRIVATE|MAP_ANON,-1,0x0) = 34374418432 (0x800e00000) fstatat(AT_FDCWD,"a",{ mode=-rw-r--r-- ,inode=6510202,size=16993,blksize=32768 },0x0) = 0 (0x0) stat("b",0x7fffffffea50) ERR#2 'No such file or directory' openat(AT_FDCWD,"a",O_RDONLY,00) = 3 (0x3) openat(AT_FDCWD,"b",O_WRONLY|O_CREAT|O_TRUNC,0100644) = 4 (0x4) mmap(0x0,16993,PROT_READ,MAP_SHARED,3,0x0) = 34366304256 (0x800643000) write(4,".\\" $FreeBSD: stable/11/usr.bin"...,16993) = 16993 (0x4261) munmap(0x800643000,16993) = 0 (0x0) close(4) = 0 (0x0) close(3) = 0 (0x0) [snip] Please also consider that these commands are repeatable (on the same file): cat always sees the file empty, cp always succeedes. # cp a c # cat a # cat c [data] I think this also tracks down the problem to read operations: the file was successfully installed with yesterday's buildworld. Only today, at this time, it started to behave ``funny''. Best regards, -- rigo http://rigo.altervista.org From owner-freebsd-fs@freebsd.org Wed Oct 19 15:28:48 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E0E1FC18AEA for ; Wed, 19 Oct 2016 15:28:48 +0000 (UTC) (envelope-from dgeo@centrale-marseille.fr) Received: from mel0.ec-m.fr (melout.ec-m.fr [147.94.19.37]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9635ED3B for ; Wed, 19 Oct 2016 15:28:48 +0000 (UTC) (envelope-from dgeo@centrale-marseille.fr) Subject: Re: Recommended HBA for ZFS, contemporary DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=centrale-marseille.fr; s=smtp0; t=1476890361; bh=GYBkjkBcPnLZl4bx5yzKW+9bw4l12ZtbFXSDRSNuWBI=; h=Subject:To:References:From:Date:In-Reply-To; b=oeAs6qjchzgm2+4fTeocMKD86X3XyMB3Ffp4Cg4CeWLQJHOUSCJrZURKPhm4+YWmg lwubG+uahaYMhIvunRpVlZ9UJI2o/g7K4ZZ6vl3RckICZnhieyhHDb0dA8E81B/1po iwU0gEOM4eWNveSw2Geh4bSbk3WInjVTZcv1idlGQZwPYxskfipKWiPDD/hwtfzNwV M69BPUHwID9IAcPW7wwLCrxy1d+tLdxbGDc9a/Jb3YB5s6QnLvpG+fnRHVuuaroed/ l2Mp06GUyVonHNUIrxpTTItw0rBe4EZAZZMhJSVY8zEuZQ2n5rj1ANjIJcglH9drju abc2lyZ7crlZQ== To: freebsd-fs@freebsd.org References: <306ccab3-4c78-751a-2258-54701a64ab4b@internetx.com> <41DE4DAA-B5E1-4BB9-AF54-780236A901EF@gmail.com> <059af3ed-71b3-b31d-893c-732121989cee@kateley.com> <633311CF-ADF2-479F-AFB9-E9265C101302@gmail.com> <376FE1E5-42BD-4878-8441-DA912E4ECB5B@gmail.com> <70B75F18-056B-49E5-9CDE-E8CCEA405CE8@gmail.com> <2521A945-AB44-4ADF-80B2-03F528BA11B6@gmail.com> From: geoffroy desvernay Openpgp: id=E15095B3F06A1012EE2921023FCFF4094587A0F0 Message-ID: <61997358-1660-20d1-1067-df4dc01ede7f@centrale-marseille.fr> Date: Wed, 19 Oct 2016 17:19:21 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <2521A945-AB44-4ADF-80B2-03F528BA11B6@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="LWeJIEF8gMOP3lFjMuRH54Wtlf1fGMFHk" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 15:28:49 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --LWeJIEF8gMOP3lFjMuRH54Wtlf1fGMFHk Content-Type: multipart/mixed; boundary="2h8ijnxl9H6fXA4wxnrRf6dKFoQ0xtMua"; protected-headers="v1" From: geoffroy desvernay To: freebsd-fs@freebsd.org Message-ID: <61997358-1660-20d1-1067-df4dc01ede7f@centrale-marseille.fr> Subject: Re: Recommended HBA for ZFS, contemporary References: <306ccab3-4c78-751a-2258-54701a64ab4b@internetx.com> <41DE4DAA-B5E1-4BB9-AF54-780236A901EF@gmail.com> <059af3ed-71b3-b31d-893c-732121989cee@kateley.com> <633311CF-ADF2-479F-AFB9-E9265C101302@gmail.com> <376FE1E5-42BD-4878-8441-DA912E4ECB5B@gmail.com> <70B75F18-056B-49E5-9CDE-E8CCEA405CE8@gmail.com> <2521A945-AB44-4ADF-80B2-03F528BA11B6@gmail.com> In-Reply-To: <2521A945-AB44-4ADF-80B2-03F528BA11B6@gmail.com> --2h8ijnxl9H6fXA4wxnrRf6dKFoQ0xtMua Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 10/19/2016 09:20, Ben RUBSON wrote: > Thank you Rich. >=20 > I saw that the LSI 3008 can be put in IT mode, as with the well known 2= 008. > Firmware & drivers seem to be well maintained, with a P13 release last = month. > 2 good points. >=20 > However I did not found much much user feedback on it, nor recommandati= ons. > There should be no surprise compared to the 2008, but we never know... >=20 Well, I just received one, and it seems complicated for the moment (or I missed something important): Dell-provided avago SAS3008 card, with dell 1420 enclosure with 24 sas drives=85 mprutil show some infos: Adapter: mpr0 Adapter: Board Name: Board Assembly: Chip Name: LSISAS3008 Chip Revision: BIOS Revision: 10.07.03.00 Firmware Revision: 9.00.09.00 Integrated RAID: no Devices: B____T SAS Address Handle Parent Device Speed Enc Slot Wdt 520474729974b57f 0009 0001 SMP Target 12 0002 00 4 00 28 5000c50097ce7339 000a 0009 SAS Target ??? 0002 20 1 00 29 5000c50097ce65d5 000b 0009 SAS Target ??? 0002 21 1 00 30 5000c50097ce53bd 000c 0009 SAS Target ??? 0002 22 1 00 31 5000c50097ce6225 000d 0009 SAS Target ??? 0002 23 1 00 26 5000c50097ce78dd 000e 0009 SAS Target 12 0002 18 1 00 27 5000c50097ce70c1 000f 0009 SAS Target 12 0002 19 1 00 20 5000c50097ce7c41 0010 0009 SAS Target 12 0002 12 1 00 21 5000c50097ce73a1 0011 0009 SAS Target 12 0002 13 1 00 22 5000c50097ce7085 0012 0009 SAS Target 12 0002 14 1 00 23 5000c50097ce5f6d 0013 0009 SAS Target 12 0002 15 1 00 24 5000c50097ca1d95 0014 0009 SAS Target 12 0002 16 1 00 25 5000c50097ce7ac5 0015 0009 SAS Target 12 0002 17 1 00 09 5000c50097ce1bd5 0016 0009 SAS Target 12 0002 01 1 00 10 5000c50097cd7f29 0017 0009 SAS Target 12 0002 02 1 00 11 5000c50097cd7efd 0018 0009 SAS Target 12 0002 03 1 00 12 5000c50097cda235 0019 0009 SAS Target 12 0002 04 1 00 15 5000c50097ce1a75 001a 0009 SAS Target 12 0002 07 1 00 16 5000c50097ce295d 001b 0009 SAS Target 12 0002 08 1 00 17 5000c50097cda74d 001c 0009 SAS Target 12 0002 09 1 00 18 5000c50097ce7b5d 001d 0009 SAS Target 12 0002 10 1 00 19 5000c50097ce8cb5 001e 0009 SAS Target 12 0002 11 1 00 14 5000c50097cdf3f1 001f 0009 SAS Target 12 0002 06 1 00 13 5000c50097ce6279 0020 0009 SAS Target 12 0002 05 1 00 08 5000c50097ce8215 0021 0009 SAS Target 12 0002 00 1 00 32 520474729974b57d 0022 0009 SEP Target 12 0002 24 1 smartctl show correct infos about drives But dmesg show this (for each drive): (da4:mpr0:0:12:0): READ(10). CDB: 28 00 e8 e0 88 ae 00 00 01 00 (da4:mpr0:0:12:0): CAM status: SCSI Status Error (da4:mpr0:0:12:0): SCSI status: Check Condition (da4:mpr0:0:12:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) (da4:mpr0:0:12:0): Error 22, Unretryable error (da4:mpr0:0:12:0): READ(10). CDB: 28 00 e8 e0 88 71 00 00 04 00 (da4:mpr0:0:12:0): CAM status: SCSI Status Error (da4:mpr0:0:12:0): SCSI status: Check Condition (da4:mpr0:0:12:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) (da4:mpr0:0:12:0): Error 22, Unretryable error (da4:mpr0:0:12:0): READ(10). CDB: 28 00 e8 e0 88 ae 00 00 01 00 (da4:mpr0:0:12:0): CAM status: SCSI Status Error (da4:mpr0:0:12:0): SCSI status: Check Condition (da4:mpr0:0:12:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) (da4:mpr0:0:12:0): Error 22, Unretryable error (da4:mpr0:0:12:0): READ(10). CDB: 28 00 e8 e0 88 af 00 00 01 00 (da4:mpr0:0:12:0): CAM status: SCSI Status Error (da4:mpr0:0:12:0): SCSI status: Check Condition (da4:mpr0:0:12:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) (da4:mpr0:0:12:0): Error 22, Unretryable error (da4:mpr0:0:12:0): READ(10). CDB: 28 00 e8 e0 88 af 00 00 01 00 (da4:mpr0:0:12:0): CAM status: SCSI Status Error (da4:mpr0:0:12:0): SCSI status: Check Condition (da4:mpr0:0:12:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) (da4:mpr0:0:12:0): Error 22, Unretryable error (da4:mpr0:0:12:0): READ(10). CDB: 28 00 e8 e0 88 af 00 00 01 00 (da4:mpr0:0:12:0): CAM status: SCSI Status Error (da4:mpr0:0:12:0): SCSI status: Check Condition (da4:mpr0:0:12:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) (da4:mpr0:0:12:0): Error 22, Unretryable error (da4:mpr0:0:12:0): READ(10). CDB: 28 00 e8 e0 88 af 00 00 01 00 (da4:mpr0:0:12:0): CAM status: SCSI Status Error (da4:mpr0:0:12:0): SCSI status: Check Condition (da4:mpr0:0:12:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) (da4:mpr0:0:12:0): Error 22, Unretryable error (da4:mpr0:0:12:0): READ(10). CDB: 28 00 e8 e0 88 af 00 00 01 00 (da4:mpr0:0:12:0): CAM status: SCSI Status Error (da4:mpr0:0:12:0): SCSI status: Check Condition (da4:mpr0:0:12:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) (da4:mpr0:0:12:0): Error 22, Unretryable error zpool create refuses to use them=85 I think mpr(4) is missing some love here=85 Or I missed something ? (Just posted some more details on freebsd-stable@ and current@) Cheers, --=20 *geoffroy desvernay* C.R.I - Administration syst=E8mes et r=E9seaux Ecole Centrale de Marseille --2h8ijnxl9H6fXA4wxnrRf6dKFoQ0xtMua-- --LWeJIEF8gMOP3lFjMuRH54Wtlf1fGMFHk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJYB475AAoJED/P9AlFh6DwS+4QAJX2sZh4cZ3iWC03vGmLyzwa 2bZZx6orPxhipzcuET+2CYY/9kG88vitwIudyu8sTzV0yfPuvs6ehfgOR5cSGwyb 3q5TDrp1nj3EiDuHlMaIfAWpwSpxWx/q4gxaIuyL7NDZj85aAeomajc7XpkGbkoH R1HEIraHhR9KbNDr0Vasq2OPfWHHjy7biSu8OAl2poYxhOSTzq71abNYVk1PZR5S IG1NKH5h4QYTy4r7ordiXXw82VrVB3v8dMU9sy/uMPk4xJweTbyIn4oTrt2HsJsZ rpKhoG0ff3LH2VgnuY2uz/gWODJqdUqqfBoLMFhyZempUvA5i3j6eW/fd6looFOY t9tvcYe3iiMsoouxPMU/avHMMpDNBXgClsvTt0hXquip6oIyRvRnrARKYseaVJZ/ hKSVEyVu02XbfqEc0g1iCOOcIcVyEVWrxfUJn++orciTWjJnYB/XTfLhWAG/6t53 02d7hUNJIiK8B5ab+/ClRJN/odXP2p+TYmRkXTXQCGfPwOC68txcp7nVx63azmyt nwO2aNtc8Rw5H1TLiyeZXJY2KoYv0pyyfeZ8Os1Oab8548+RIK7hYdSbYoJm1gpU eh31OxZStH8X8YR0B8N6g7GFlCxJFcRBBMvaCjFjQZH0TDdPtBAOJXyrTbDyD+T1 xJw+9/OKWGP30r2Fs+Ux =vYtM -----END PGP SIGNATURE----- --LWeJIEF8gMOP3lFjMuRH54Wtlf1fGMFHk-- From owner-freebsd-fs@freebsd.org Wed Oct 19 16:40:30 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71445C18D97 for ; Wed, 19 Oct 2016 16:40:30 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 23F611BF for ; Wed, 19 Oct 2016 16:40:30 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-qt0-x22a.google.com with SMTP id f6so29063030qtd.2 for ; Wed, 19 Oct 2016 09:40:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=huYh4NOeRKW734EWZx8NemC+OS8rjsTRYxGPQpZGqec=; b=yszbYJQcpRb5MhgqAJLbQRBFL6HBlbXAnVkcCC0AfK3mBpPPU9iGWr/MsUw+KCGq5H qpK0YZF6Ar8uPCAnSRBHwVUVaI3xBCcIDTBJQ75bbSN+pR5X4yrEXIle90iXlBE2o5yE FLy2yHmKr7sLBU2He4K/MHgyVMWhm2hLqpaPRGlkE+xoDEWf8rRyUwAmXOL92KSlNSQB /+SYy8xETCkF+1lwe3VrZQOv2XKLFnw1QaObrQ74DGYSVCjQIKHJMNV/l4sfiFOL+0Pa rxPW1fDvH57U/4pASACWui1kJvkW/lwshSS/qwWVhp+abW/Bgdwztuyd3RxzbgfeMTep ViqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=huYh4NOeRKW734EWZx8NemC+OS8rjsTRYxGPQpZGqec=; b=OZwG0dLQ+H02tsyHdz/QifJ6ymYMr2DJfzQtT8cZt3RDA0psQkxctXH6UyVRlPQMtV brWD0D7RyvKEMeR8GKNTzR4dygzSvC1AM3a8x0uXXD2zaUNX9OPmK+hYiq8cPfMKPEhB 3XgryZ5fh+2pvT8GvF+1x9ahrKQ1zZczbS3iqumuE+1vxCIKfXAxTS9BO5GTPlG4eBYk ykFiIWxpVS3otsosczCdfocWVn2FS2i+o/pzAXz/gphaUMXdCEY1aZT3kcgLrRFU8hBE cvQisXTSLutpcYvQNsyL8d/E67W3k3qLgHxrg4aZGImOU8q/nj3kntsrTQWiflV9i+yv 6dmg== X-Gm-Message-State: AA6/9Rk+GylqMK/zLNzzIvp3ABKNU1O3E7S4OXOLl8GnlM1VG8FCThCErcpciM6IfnQODA== X-Received: by 10.194.115.168 with SMTP id jp8mr4872937wjb.27.1476895228935; Wed, 19 Oct 2016 09:40:28 -0700 (PDT) Received: from macbook-air-de-benjamin.home (LFbn-1-7159-4.w90-116.abo.wanadoo.fr. [90.116.90.4]) by smtp.gmail.com with ESMTPSA id us3sm70387501wjb.32.2016.10.19.09.40.28 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 19 Oct 2016 09:40:28 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Recommended HBA for ZFS, contemporary From: Ben RUBSON In-Reply-To: <61997358-1660-20d1-1067-df4dc01ede7f@centrale-marseille.fr> Date: Wed, 19 Oct 2016 18:40:27 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <306ccab3-4c78-751a-2258-54701a64ab4b@internetx.com> <41DE4DAA-B5E1-4BB9-AF54-780236A901EF@gmail.com> <059af3ed-71b3-b31d-893c-732121989cee@kateley.com> <633311CF-ADF2-479F-AFB9-E9265C101302@gmail.com> <376FE1E5-42BD-4878-8441-DA912E4ECB5B@gmail.com> <70B75F18-056B-49E5-9CDE-E8CCEA405CE8@gmail.com> <2521A945-AB44-4ADF-80B2-03F528BA11B6@gmail.com> <61997358-1660-20d1-1067-df4dc01ede7f@centrale-marseille.fr> To: freebsd-fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 16:40:30 -0000 > On 19 Oct 2016, at 17:19, geoffroy desvernay = wrote: >=20 > On 10/19/2016 09:20, Ben RUBSON wrote: >> Thank you Rich. >>=20 >> I saw that the LSI 3008 can be put in IT mode, as with the well known = 2008. >> Firmware & drivers seem to be well maintained, with a P13 release = last month. >> 2 good points. >>=20 >> However I did not found much much user feedback on it, nor = recommandations. >> There should be no surprise compared to the 2008, but we never = know... >>=20 > Well, I just received one, and it seems complicated for the moment (or = I > missed something important): Some of your drives seems to be not correctly detected. What "sas3ircu 0 display" returns ? Does "geom disk list" correctly shows your disks ? Firmware seems quite old too. Does it suits the driver version ? Ben From owner-freebsd-fs@freebsd.org Wed Oct 19 16:46:27 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 654E9C1912B for ; Wed, 19 Oct 2016 16:46:27 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-qt0-f175.google.com (mail-qt0-f175.google.com [209.85.216.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 237EBA08 for ; Wed, 19 Oct 2016 16:46:26 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-qt0-f175.google.com with SMTP id f6so29280038qtd.2 for ; Wed, 19 Oct 2016 09:46:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=9hTgm0hE9mQPXgjqQsIoCmbSO38ndsM3UsMdQCMsL0o=; b=SYEcnJ9+4UugMWc9nVMqr980okQdG6ibjBnMbJPUNEnagJ8oLhiJsvM7l/HKVNf3Tr O8o3xJ0bdy+Nl8QRVZhQWMKYQX4SI5oyQmbFQS2Y/0hjd2oyjK2alc1IdklRS5yMFDe/ dF42GqeXy6fV91LtP3t2+ZiPQG+FgQzk3A+fA+a/xE7n/LLDJDtreX/T0pPhj66AShw5 2oLstAtlYMVd7W1sTHUiVQSwatdnZZR43N5IhwI70rFkXCWZnqOtI7tsI4xEV3DTvnD0 QwSJFb98MZI8y5OwgKJhqf0rZ3kYL1EMLPSF5iNdNcgYCbclUnspI1L6kF4O/S31C2si E+aQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=9hTgm0hE9mQPXgjqQsIoCmbSO38ndsM3UsMdQCMsL0o=; b=jSg/RkRcPtN7rdpWnhOytkOpbKSrDYE6VSnD9PcJRwibI51bYsdYT/08V+c37bKB9D mC2rADLWogOghBdZPJMNgIXtgOhx+Bq9L9CLsYvyfIBC1clIpsgMrUKBHUmuU/ULeXgn rtGGjlxSZA1e1qJo2XHY7t//gEKIyKoTATnrNQulBX+Q/DUOzBDoLgqhxbUDmjG1VIqH Ek0ye/aBAEZ134NHDO98gkHCj3mAuSIGPZEx+n5s2t+51asHji/8Lb+sng6dMZI0PwRI Q3XCyvMt/HZJIdFUwHZithFJAsdCL9qPAXteU2bz98M1cG/a9PG+NYUBrtAmmYDMIk2U 8HtA== X-Gm-Message-State: AA6/9RnVYhMM1uq2Pk2ni5L13Z7c1V94nd6+HzFapx+wFHHjZvB8xH/5Y+MqGp2ubiLv/g== X-Received: by 10.28.13.84 with SMTP id 81mr6116034wmn.102.1476895519775; Wed, 19 Oct 2016 09:45:19 -0700 (PDT) Received: from macbook-air-de-benjamin.home (LFbn-1-7159-4.w90-116.abo.wanadoo.fr. [90.116.90.4]) by smtp.gmail.com with ESMTPSA id ce6sm70316040wjc.27.2016.10.19.09.45.18 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 19 Oct 2016 09:45:19 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Recommended HBA for ZFS, contemporary From: Ben RUBSON In-Reply-To: Date: Wed, 19 Oct 2016 18:45:17 +0200 Content-Transfer-Encoding: 7bit Message-Id: <3C7A8B5A-5900-4996-A869-6BA00191F099@gmail.com> References: <306ccab3-4c78-751a-2258-54701a64ab4b@internetx.com> <41DE4DAA-B5E1-4BB9-AF54-780236A901EF@gmail.com> <059af3ed-71b3-b31d-893c-732121989cee@kateley.com> <633311CF-ADF2-479F-AFB9-E9265C101302@gmail.com> <376FE1E5-42BD-4878-8441-DA912E4ECB5B@gmail.com> <70B75F18-056B-49E5-9CDE-E8CCEA405CE8@gmail.com> <2521A945-AB44-4ADF-80B2-03F528BA11B6@gmail.com> To: freebsd-fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 16:46:27 -0000 > On 19 Oct 2016, at 09:56, Rich wrote: > > Otherwise, the 2008 is generally > "good enough" for the long tail of people that make up the majority of > online posts about things. Thank you for your feedback Rich. The thing it that now sometimes manufacturers do not make the 2008 available anymore with their server, we have to go with the 3008. We could however still have to choice to buy a 2008 separately... Ben From owner-freebsd-fs@freebsd.org Thu Oct 20 07:38:56 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35660C1974E for ; Thu, 20 Oct 2016 07:38:56 +0000 (UTC) (envelope-from jg@internetx.com) Received: from mx1.internetx.com (mx1.internetx.com [62.116.129.39]) by mx1.freebsd.org (Postfix) with ESMTP id E488DD50 for ; Thu, 20 Oct 2016 07:38:55 +0000 (UTC) (envelope-from jg@internetx.com) Received: from localhost (localhost [127.0.0.1]) by mx1.internetx.com (Postfix) with ESMTP id 3989245FC112; Thu, 20 Oct 2016 09:29:26 +0200 (CEST) X-Virus-Scanned: InterNetX GmbH amavisd-new at ix-mailer.internetx.de Received: from mx1.internetx.com ([62.116.129.39]) by localhost (ix-mailer.internetx.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NtgW09QGRaJ2; Thu, 20 Oct 2016 09:29:24 +0200 (CEST) Received: from [192.168.100.26] (pizza.internetx.de [62.116.129.3]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.internetx.com (Postfix) with ESMTPSA id EEC4E45FC110; Thu, 20 Oct 2016 09:29:23 +0200 (CEST) Subject: Re: Recommended HBA for ZFS, contemporary References: <306ccab3-4c78-751a-2258-54701a64ab4b@internetx.com> <41DE4DAA-B5E1-4BB9-AF54-780236A901EF@gmail.com> <059af3ed-71b3-b31d-893c-732121989cee@kateley.com> <633311CF-ADF2-479F-AFB9-E9265C101302@gmail.com> <376FE1E5-42BD-4878-8441-DA912E4ECB5B@gmail.com> <70B75F18-056B-49E5-9CDE-E8CCEA405CE8@gmail.com> <2521A945-AB44-4ADF-80B2-03F528BA11B6@gmail.com> <3C7A8B5A-5900-4996-A869-6BA00191F099@gmail.com> To: Ben RUBSON , freebsd-fs Reply-To: jg@internetx.com From: InterNetX - Juergen Gotteswinter Message-ID: <502e2b97-4f81-5fdf-3bcc-673d5cceaa22@internetx.com> Date: Thu, 20 Oct 2016 09:29:23 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <3C7A8B5A-5900-4996-A869-6BA00191F099@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2016 07:38:56 -0000 Dell has still so much in stock of those that they are forced to sell them. They are sold as SAS Adapter for Tape Drives, but its a standard LSI 2008 http://www.dell.com/en-us/shop/accessories/apd/342-0910?c=us&l=en&sku=342-0910 For Companies the priece should be less than 50% Cheers, Am 19.10.2016 um 18:45 schrieb Ben RUBSON: > >> On 19 Oct 2016, at 09:56, Rich wrote: >> >> Otherwise, the 2008 is generally >> "good enough" for the long tail of people that make up the majority of >> online posts about things. > > Thank you for your feedback Rich. > > The thing it that now sometimes manufacturers do not make the 2008 > available anymore with their server, we have to go with the 3008. > We could however still have to choice to buy a 2008 separately... > > Ben > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@freebsd.org Thu Oct 20 15:49:32 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0A71AC1A3AF for ; Thu, 20 Oct 2016 15:49:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E62F5E44 for ; Thu, 20 Oct 2016 15:49:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9KFnMpq048837 for ; Thu, 20 Oct 2016 15:49:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 204764] Filesystem deadlock, process in vodead state Date: Thu, 20 Oct 2016 15:49:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: matthew@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2016 15:49:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204764 Matthew Seaman changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthew@FreeBSD.org --- Comment #33 from Matthew Seaman --- Yet another data point:=20 Our environment: Dell R730 servers with ~2TB of RAID10 disk arrays running FreeBSD 10.3-RELEASE and postgresql92-server. UFS2 filesystems. We applied Kostik's patch from https://lists.freebsd.org/pipermail/freebsd-stable/2016-August/085150.html Before this we were seeing the VODEAD problem about 2--3 times per week. S= ince patching we've run for 16 days with out problems. A definite +1 for issuing this patch as an Errata Note. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Oct 21 02:29:05 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E970BC11A6E for ; Fri, 21 Oct 2016 02:29:05 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A7083BE6 for ; Fri, 21 Oct 2016 02:29:05 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by mail-qk0-x229.google.com with SMTP id n189so127742820qke.0 for ; Thu, 20 Oct 2016 19:29:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kraus-haus-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=j/HZhM0vgfUGeyJUso1Pk1y/gk4+pHZu54IGwvqU5cA=; b=ngQdf52EtL30JWPtglEzwWUOefAmJiOqX5tFHodV8andBx4mbt7wGkrMg+POqKo4Mo gdANjaHbN+wKcfrt0ociNvwZ9q5KKOJf0j954cvZpm4knnT7agbtcRVHX2IF97iafP43 K9wCjlTWLL2y0Pzp52XQaKWaAk8dkJRzg6qTzu0ne4TmBbL3fMNkrOwjrAS7a+xLHpsH cQynHiHh2cuEqpwJJp1ADAl/gntWcCoPfd3cnDe66QpTe8yVhL1fvzWuvUsgje4sF+5E Tv/QKVuj8y8nSTh7dnkiR7h5CVsDuSBlsbpEfJ13XcSuDIpPJv6FoJUiQS8SAi9N5C9R lCCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=j/HZhM0vgfUGeyJUso1Pk1y/gk4+pHZu54IGwvqU5cA=; b=KJdITJ9Udxp/cqM53x8IKwWnFgH/dhyzGL9h6UaXKcD3sbqIbH5NweHMsLATFtMkVN cOydyjNVxzCRLEDSkEfb7jtJNrx31PXVzC/DTuP0JTrMuTIQYkf9I6r7EgRFVxMykSf0 XpT0lwd5yJH++9Q/KA2lQ3qJ/YxB7nSDWk33gckQSpJW2KSx22fztJoOfdW9FC9BGjEE Yp0cAYMwm5UORs6AmAH5HKtf3nUPuaVph2OqFj7LPAq3fXgqM/Ivrg7Wc6fmrqU2HVug kbn6VaJCR5xEGfr2ALvcOTZQugxyh9wHYKsVMFv97JbrzC52bLlqHEfspIzkk257PKpc yUtA== X-Gm-Message-State: ABUngvdwKo7/2Lp+PSpfaQL/xAjIqmCUcOAvG1LMCmxddNRtTqG48k+xzTW/TJq0YgVKpQ== X-Received: by 10.55.191.135 with SMTP id p129mr4063242qkf.279.1477016944678; Thu, 20 Oct 2016 19:29:04 -0700 (PDT) Received: from [192.168.2.137] (pool-74-109-188-83.albyny.fios.verizon.net. [74.109.188.83]) by smtp.gmail.com with ESMTPSA id q5sm194594qtc.45.2016.10.20.19.29.04 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 20 Oct 2016 19:29:04 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Recommended HBA for ZFS, contemporary From: Paul Kraus In-Reply-To: <3c17c513-2eb3-7acf-4885-b31594ea2ee8@kateley.com> Date: Thu, 20 Oct 2016 22:29:07 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <306ccab3-4c78-751a-2258-54701a64ab4b@internetx.com> <41DE4DAA-B5E1-4BB9-AF54-780236A901EF@gmail.com> <63B2949F-01C6-4465-A2D8-E4AA0FE0150C@bway.net> <3c17c513-2eb3-7acf-4885-b31594ea2ee8@kateley.com> To: FreeBSD FS X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2016 02:29:06 -0000 > On Aug 22, 2016, at 3:23 PM, Linda Kateley = wrote: >> This is all a bit crazy. Is the LSI series of HBAs really the only = choice >> outside of onboard controllers? It seems like they are troublesome, = support >> is spotty, and this whole flashing process gives me nightmares. > I have the same question. LSI used to always be the go-to, but in = recent years it seems to get more and more wonky.. there has to be a = better way. I have been using a variety of cards using the non-RAID Marvell chipsets = (as was recommended to be me over on the OpenZFS list a few years ago). = Generally the cards are from Syba. I have had no failures and no = problems under FreeBSD 10.1 and 10.3. From owner-freebsd-fs@freebsd.org Fri Oct 21 09:20:02 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EFBC6C1BBFA for ; Fri, 21 Oct 2016 09:20:02 +0000 (UTC) (envelope-from marek.salwerowicz@misal.pl) Received: from mail3.misal.pl (mail3.misal.pl [83.19.131.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7B1F81735 for ; Fri, 21 Oct 2016 09:20:01 +0000 (UTC) (envelope-from marek.salwerowicz@misal.pl) Received: from localhost (mail3.misal.pl [127.0.0.1]) by mail3.misal.pl (Postfix) with ESMTP id 993B81BCEB for ; Fri, 21 Oct 2016 11:12:46 +0200 (CEST) X-Virus-Scanned: amavisd X-Spam-Flag: NO X-Spam-Score: -3 X-Spam-Level: X-Spam-Status: No, score=-3 tagged_above=-9999 required=9 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no Authentication-Results: mail3.misal.pl (amavisd-new); dkim=pass (1024-bit key) header.d=misal.pl Received: from mail3.misal.pl ([127.0.0.1]) by localhost (mail3.misal.pl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WdddxqQqKDxc for ; Fri, 21 Oct 2016 11:12:31 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.10.3 mail3.misal.pl E6A79316F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=misal.pl; s=misal.pl; t=1477041151; bh=hgcnrImbNeiYfC7ps4oe0uwDZV8s/MKDstdatsoZ2V8=; h=From:Subject:To:Date:From; b=p2iykMucw0bmoIa+3st2bc5wH7jL4ob8Co/qRTWg3uYkL1t4SID6nUaqhRwGxU7xy 8ZgHhwtuSv+kBr0dZwqmiNxdougQgpfjCZRlwlHAXUW0yoWphC+tYQtlM4ohdPOQKl /YqtlMQrPwee0kEm+btrIkvjfieavXpyY5Wy0780= From: Marek Salwerowicz Subject: ZFS - NFS server for VMware ESXi issues To: freebsd-fs@freebsd.org Message-ID: <930df17b-8db8-121a-a24b-b4909b8162dc@misal.pl> Date: Fri, 21 Oct 2016 11:12:21 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2016 09:20:03 -0000 Hi list, I run a following server: - Supermicro 6047R-E1R36L - 32 GB RAM - 1x INTEL CPU E5-2640 v2 @ 2.00GHz - FreeBSD 10.1 Drive for OS: - HW RAID1: 2x KINGSTON SV300S37A120G zpool: - 18x WD RED 4TB @ raidz2 - log: mirrored Intel 730 SSD atime disabled on zfs datasets. No NFS tuning MTU 9000 The box works as a NFS filer for 3 VMware ESXi (5.0, 5.1, 5.5) servers and iSCSI drive for one VM requiring huge space over 1Gbit Network. Interfaces on the server are aggregated 4x1Gbit. Current usage: # zpool list NAME SIZE ALLOC FREE FRAG EXPANDSZ CAP DEDUP HEALTH ALTROOT tank1 65T 27.3T 37.7T - - 41% 1.00x ONLINE - The box has been working fine for about two years. However, about two weeks ago we experienced a NFS service unavailability. ESXi servers lost NFS connection to the filer (shares were grayed out). 'top' command on the filer has shown that "nfsd: server" process hangs with consuming hundreds of CPU time (I didn't capture the output). # service nfsd restart didn't help, the only solution was cold-rebooting machine After the reboot I performed system upgrade (was running on 9.2-RELEASE before) to 10.1-RELEASE Today, after two weeks of working, we experienced the same situation. The nfsd service was in following state: PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 984 root 128 20 0 12344K 4020K vq->vq 8 346:27 0.00% nfsd nfsd service didn't respond to service nfsd restart, but this time machine was able to reboot using "# reboot" command. nfsd service works in threaded model, with 128 threads (default) Current top output: last pid: 2535; load averages: 0.13, 0.14, 0.15 up 0+04:29:06 11:00:24 36 processes: 1 running, 35 sleeping CPU: 0.0% user, 0.0% nice, 0.1% system, 0.0% interrupt, 99.9% idle Mem: 5724K Active, 48M Inact, 25G Wired, 173M Buf, 5828M Free ARC: 23G Total, 7737M MFU, 16G MRU, 16M Anon, 186M Header, 89M Other Swap: 32G Total, 32G Free Displaying threads as a count PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 1949 root 129 24 0 12344K 4132K rpcsvc 10 7:15 1.27% nfsd 1025 root 1 20 0 14472K 1936K select 15 0:01 0.00% powerd 1021 root 1 20 0 26096K 18016K select 2 0:01 0.00% ntpd 1147 marek 1 20 0 86488K 7592K select 2 0:01 0.00% sshd 1083 root 1 20 0 24120K 5980K select 0 0:00 0.00% sendmail 1052 root 1 20 0 30720K 5356K nanslp 6 0:00 0.00% smartd 1260 root 1 20 0 23576K 3576K pause 4 0:00 0.00% csh 1948 root 1 28 0 24632K 5832K select 10 0:00 0.00% nfsd 1144 root 1 20 0 86488K 7544K select 9 0:00 0.00% sshd 1148 marek 1 21 0 24364K 4324K pause 1 0:00 0.00% zsh 852 root 1 20 0 16584K 2192K select 3 0:00 0.00% rpcbind 1926 root 1 52 0 26792K 5956K select 1 0:00 0.00% mountd 848 root 1 20 0 14504K 2144K select 13 0:00 0.00% syslogd 1258 root 1 25 0 50364K 3468K select 6 0:00 0.00% sudo 2432 marek 1 20 0 86488K 7620K select 15 0:00 0.00% sshd 1090 root 1 49 0 16596K 2344K nanslp 0 0:00 0.00% cron 2535 root 1 20 0 21920K 4252K CPU15 15 0:00 0.00% top 1259 root 1 28 0 47708K 2808K wait 12 0:00 0.00% su 2433 marek 1 20 0 24364K 4272K ttyin 1 0:00 0.00% zsh 2429 root 1 20 0 86488K 7616K select 15 0:00 0.00% sshd 751 root 1 20 0 13164K 4548K select 13 0:00 0.00% devd 1086 smmsp 1 20 0 24120K 5648K pause 11 0:00 0.00% sendmail 1080 root 1 20 0 61220K 6996K select 8 0:00 0.00% sshd 1140 root 1 52 0 14492K 2068K ttyin 9 0:00 0.00% getty 1138 root 1 52 0 14492K 2068K ttyin 15 0:00 0.00% getty 1141 root 1 52 0 14492K 2068K ttyin 10 0:00 0.00% getty 1143 root 1 52 0 14492K 2068K ttyin 0 0:00 0.00% getty 1136 root 1 52 0 14492K 2068K ttyin 6 0:00 0.00% getty 1139 root 1 52 0 14492K 2068K ttyin 2 0:00 0.00% getty 1142 root 1 52 0 14492K 2068K ttyin 4 0:00 0.00% getty 1137 root 1 52 0 14492K 2068K ttyin 13 0:00 0.00% getty 953 root 1 20 0 27556K 3468K select 5 0:00 0.00% ctld 152 root 1 52 0 12336K 1800K pause 9 0:00 0.00% adjkerntz 734 root 1 52 0 16708K 2044K select 1 0:00 0.00% moused 692 root 1 52 0 16708K 2040K select 8 0:00 0.00% moused 713 root 1 52 0 16708K 2044K select 8 0:00 0.00% moused and with I/O output: last pid: 2535; load averages: 0.09, 0.12, 0.15 up 0+04:30:05 11:01:23 36 processes: 1 running, 35 sleeping CPU: 0.1% user, 0.0% nice, 1.7% system, 0.1% interrupt, 98.2% idle Mem: 5208K Active, 49M Inact, 25G Wired, 173M Buf, 5821M Free ARC: 23G Total, 7736M MFU, 16G MRU, 9744K Anon, 186M Header, 89M Other Swap: 32G Total, 32G Free PID USERNAME VCSW IVCSW READ WRITE FAULT TOTAL PERCENT COMMAND 1949 root 360 31 0 131 0 131 100.00% nfsd 1025 root 8 0 0 0 0 0 0.00% powerd 1021 root 2 0 0 0 0 0 0.00% ntpd 1147 marek 2 0 0 0 0 0 0.00% sshd 1083 root 0 0 0 0 0 0 0.00% sendmail 1052 root 0 0 0 0 0 0 0.00% smartd 1260 root 0 0 0 0 0 0 0.00% csh 1948 root 0 0 0 0 0 0 0.00% nfsd 1144 root 0 0 0 0 0 0 0.00% sshd My questions: 1. Since we are reaching ~30 TB of allocated space, could it be memory lacks ( magic rule 1 GB of RAM for 1 TB of ZFS storage space) 2. Does NFS server need tuning in a standard 1Gbit network environment ? We use lagg aggregation and agree that for one ESXi server have at most 1Gbit of throughput ? Is 128 threads too much ? 3. Could SMART tests have side effect in I/O performance that result in NFS hangs? I run quite intensively short tests (4 times per day), long test once per week (on weekend) Cheers Marek From owner-freebsd-fs@freebsd.org Sat Oct 22 03:06:15 2016 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 40FF5C1C1FD for ; Sat, 22 Oct 2016 03:06:15 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1bon0092.outbound.protection.outlook.com [157.56.111.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "Microsoft IT SSL SHA2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D3C08B59 for ; Sat, 22 Oct 2016 03:06:13 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM (10.165.218.133) by YTXPR01MB0190.CANPRD01.PROD.OUTLOOK.COM (10.165.218.134) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.12; Fri, 21 Oct 2016 21:47:28 +0000 Received: from YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) by YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM ([10.165.218.133]) with mapi id 15.01.0669.021; Fri, 21 Oct 2016 21:47:28 +0000 From: Rick Macklem To: Marek Salwerowicz , "freebsd-fs@freebsd.org" Subject: Re: ZFS - NFS server for VMware ESXi issues Thread-Topic: ZFS - NFS server for VMware ESXi issues Thread-Index: AQHSK3xZ74x1v1Hl9kyKv24uLlFAmaCzbiXv Date: Fri, 21 Oct 2016 21:47:28 +0000 Message-ID: References: <930df17b-8db8-121a-a24b-b4909b8162dc@misal.pl> In-Reply-To: <930df17b-8db8-121a-a24b-b4909b8162dc@misal.pl> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-office365-filtering-correlation-id: 1b0492a9-35f8-4b1a-d35c-08d3f9fbda69 x-microsoft-exchange-diagnostics: 1; YTXPR01MB0190; 7:CDNv5duTgPl6KMGDlR2iDeOp1nPGeT4aHHddHs3pTwfaQlOer44OaFeD9dAzwY5+K5wVuBEX2Azbknyq1cxt72wiV1I//z7ME4T8IkM3yo+XKzxX43m/X1XBJ4Jhh8aY8z+bRpwGMdvZcs57Mp2sci0PNrIUHS03k3okL86RagJRK92KIfENYxT7lrVqBOPHC+66NnPEdarv5ghag6Lp1YhWs4qb3vw2iK/qpDjTFf6fKyxj5QMq2OhGFIuI0Z7FbRlgmDbNIfF8JWAxWtbXCekibbIn7+pQMSdSHTX9gvCyRLhf6PhD1HFmw1wlxkfONajQnj6qNCBXm2EFib1YxZ9D1d/UxeOt2CK5zSIdvwA=; 23:GW06fk62wFmRndJneFQts8QTCRj3zwW2VRBlNWA/n3VRV9sXsSZJlstvUA+3lX8mkjPzYwf0yC211jOMPNu6uyYyGskWLs1NJ5ZOzCs2uVzVMoPPUB0Byr1mx+WkzdCw1o+cWf/TOzwpRTYZnbgS4bY3MQ2U8Udg1RKP6hGgiauusg37aevfatWej5ab3WaA x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:YTXPR01MB0190; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040176)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6043046)(6042046); SRVR:YTXPR01MB0190; BCL:0; PCL:0; RULEID:; SRVR:YTXPR01MB0190; x-forefront-prvs: 01026E1310 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(199003)(189002)(24454002)(81166006)(86362001)(107886002)(81156014)(586003)(3280700002)(3660700001)(102836003)(8676002)(2900100001)(77096005)(2501003)(2906002)(87936001)(68736007)(9686002)(7846002)(6606003)(97736004)(5660300001)(19625215002)(54356999)(92566002)(11100500001)(19627405001)(76176999)(10400500002)(101416001)(2950100002)(50986999)(74316002)(74482002)(5002640100001)(7696004)(8936002)(106116001)(106356001)(189998001)(16236675004)(33656002)(5001770100001)(105586002)(122556002); DIR:OUT; SFP:1101; SCL:1; SRVR:YTXPR01MB0190; H:YTXPR01MB0189.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Oct 2016 21:47:28.4506 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTXPR01MB0190 X-OriginatorOrg: uoguelph.ca Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Oct 2016 03:06:15 -0000 Marek Salwerowicz wrote: Stuff snipped for brevity... > Today, after two weeks of working, we experienced the same situation. > The nfsd service was in following state: > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 984 root 128 20 0 12344K 4020K vq->vq 8 346:27 0.00% nfsd > > nfsd service didn't respond to service nfsd restart, but this time > machine was able to reboot using "# reboot" command. I am not sure how "top" got a STATE of "vq->vq", but I suspect that refers = to the vdev section of the ZFS code. (The only other place in the kernel where "vq= ->vq" shows up is in virtio and I doubt you are using that?) I'm not a ZFS guy so I can't help, but I'd guess that it's looping around i= n the vdev code, possibly competing for the vq->vq_lock? Hopefully someone with ZFS expertise can help out? Btw, about the only area of the NFS server that might need tuning is the DR= C and this doesn't suggest that. If you "nfsstat -e -s" on the server and see lar= ge #s for the last line under "Server Cache Stats:" there are tunables that can be us= ed. I'd also suggest you capture the output of "ps axHl" on the server when it = happens again, which tells you what all the nfsd threads are up to. Good luck with it, rick