From owner-freebsd-fs@freebsd.org Sun Oct 8 11:40:25 2017 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 38AF0E32671 for ; Sun, 8 Oct 2017 11:40:25 +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 DCA4170D16 for ; Sun, 8 Oct 2017 11:40: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 v98BeONi044176 for ; Sun, 8 Oct 2017 11:40:24 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 222734] 11.1-RELEASE kernel panics while importing ZFS pool Date: Sun, 08 Oct 2017 11:40: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.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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, 08 Oct 2017 11:40:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222734 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Not A Bug --- Comment #2 from Andriy Gapon --- Additional debugging confirmed the bad on-disk data theory. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 8 12:06:33 2017 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 AE8D0E335C6 for ; Sun, 8 Oct 2017 12:06:33 +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 95A647699C for ; Sun, 8 Oct 2017 12:06:33 +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 v98C6X9i048391 for ; Sun, 8 Oct 2017 12:06:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 222734] 11.1-RELEASE kernel panics while importing ZFS pool Date: Sun, 08 Oct 2017 12:06:33 +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.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ben.rubson@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug 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, 08 Oct 2017 12:06:33 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222734 Ben RUBSON changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ben.rubson@gmail.com --- Comment #3 from Ben RUBSON --- "The older ZFS code is not as thorough in validating the data." Andriy, this is interesting (and quite scary ?). What are the differences between 11.0 and 11.1 in terms of ZFS data strengt= h ? Many thanks ! Ben --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 8 19:09:28 2017 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 F36D2E3D8CC for ; Sun, 8 Oct 2017 19:09:28 +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 A2F4A72930 for ; Sun, 8 Oct 2017 19:09:28 +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 v98J9QOS047202 for ; Sun, 8 Oct 2017 19:09:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 156781] [zfs] zfs is losing the snapshot directory, Date: Sun, 08 Oct 2017 19:09: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: 8.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jwdevel@gmail.com 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: 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, 08 Oct 2017 19:09:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D156781 jwdevel@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jwdevel@gmail.com --- Comment #14 from jwdevel@gmail.com --- Although I have never gotten a system freeze or panic, I have seen this iss= ue of not being able to access the .zfs/snapshot/xyz mount. For instance: $ ls /myvolume/.zfs ls: snapshot: Bad file descriptor shares For me, I have had success manually mounting the snapshot. Adding this advi= ce in case others like me hit this issue, as the "manual mount" option does not seem to be well-documented - no reference to ZFS in mount(8) or nmount(2), = for instance. I had to look at some ZFS-on-Linux sites to discover it (: $ mount -t zfs dataset@snapshot /mountpoint (replace with args appropriate for your system, of course) System info: FreeBSD FreeBSD 9.1-RELEASE-p17 #0 r268574 amd64 ZFS 5, pool version 28 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 8 20:03:30 2017 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 E08C8E3EC05 for ; Sun, 8 Oct 2017 20:03:30 +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 7E7F982729 for ; Sun, 8 Oct 2017 20:03:30 +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 v98K3Ts4083048 for ; Sun, 8 Oct 2017 20:03:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 156781] [zfs] zfs is losing the snapshot directory, Date: Sun, 08 Oct 2017 20:03:29 +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: 8.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Unable to Reproduce X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: 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: Sun, 08 Oct 2017 20:03:31 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D156781 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Unable to Reproduce Status|In Progress |Closed --- Comment #15 from Andriy Gapon --- 9.1 is unsupported as well. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Oct 9 01:14:48 2017 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 00080E44C95 for ; Mon, 9 Oct 2017 01:14:47 +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 9FC52D8E for ; Mon, 9 Oct 2017 01:14:47 +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 v991Elp2087154 for ; Mon, 9 Oct 2017 01:14:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 156781] [zfs] zfs is losing the snapshot directory, Date: Mon, 09 Oct 2017 01:14:47 +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: 8.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: karl@denninger.net X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Unable to Reproduce X-Bugzilla-Priority: Normal 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: Mon, 09 Oct 2017 01:14:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D156781 karl@denninger.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |karl@denninger.net --- Comment #16 from karl@denninger.net --- This is an old problem that I have seen repeatedly with that OS revision, a= nd beware -- attempting to send that snapshot is likely to lead to an immediate kernel panic. I recommend updating the system as I've not seen that issue arise on 11.0 or 11.1. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Oct 9 07:09:29 2017 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 D3905E277EF for ; Mon, 9 Oct 2017 07:09:29 +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 57FCC6B3F3 for ; Mon, 9 Oct 2017 07:09:29 +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 v9979SxO025214 for ; Mon, 9 Oct 2017 07:09:29 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 222734] 11.1-RELEASE kernel panics while importing ZFS pool Date: Mon, 09 Oct 2017 07:09:28 +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.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug 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, 09 Oct 2017 07:09:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222734 --- Comment #4 from Andriy Gapon --- (In reply to Ben RUBSON from comment #3) Not sure what's scary... (at least, scarier than before). But let me try to clarify the problem first. A bit flip happened in RAM (non-ECC) and some corrupted (meta-)data got wri= tten to disk. It happened to be a block pointer within an indirect block. For = ZFS the indirect block looked totally valid as its checksum was calculated after the bit flip. So, ZFS had no reason to distrust the block pointers in the block. Still, the newer ZFS does some additional validation (sanity checking) of t= hose block pointers while the older ZFS fully trusted them to be correct. A cor= rupt block pointer would typically result in a crash later on. And such a crash= is hard(-er) to debug, that's why the extra checks were added. In some cases = the corruption would be almost benign, so things would appear to be okay. In t= his case, the block pointer was actually a hole block pointer and the corruption was of the almost benign variety. So, really, the culprit here was faulty RAM. If your data gets corrupted in memory, you have corrupted data and there is no way ZFS can help with that.= If your metadata gets corrupted in memory, then ZFS might be able to detect th= at and bail out early, or it can fail to detect the problem and crash later on= , or it can even try to read a wrong block, but then the checksum error is the m= ost likely outcome. The usual advice applies, use ECC memory and have backups. Even on a system with ECC memory some hardware can corrupt memory by writin= g to wrong location via DMA, even on a system with reliable hardware there still= can be a kernel (driver) bug that would corrupt memory contents, etc. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Oct 9 21:10:26 2017 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 18965E3BF4B for ; Mon, 9 Oct 2017 21:10:26 +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 069F07FE23 for ; Mon, 9 Oct 2017 21:10:26 +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 v99LAPgb054275 for ; Mon, 9 Oct 2017 21:10:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 222785] [zfs] show progress of running zfs operations, zpool monitor Date: Mon, 09 Oct 2017 21:10:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@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: assigned_to 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, 09 Oct 2017 21:10:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222785 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Oct 10 17:36:08 2017 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 3766BE38441 for ; Tue, 10 Oct 2017 17:36:08 +0000 (UTC) (envelope-from juan@kognito.com) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::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 AA36A655B2 for ; Tue, 10 Oct 2017 17:36:07 +0000 (UTC) (envelope-from juan@kognito.com) Received: by mail-lf0-x22c.google.com with SMTP id d10so29593743lfg.11 for ; Tue, 10 Oct 2017 10:36:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kognito-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=mGyUVyP/YIilROi09JLAsVYF0Cnc1Gto1FL7/yIdvWI=; b=AS/YTG/orUFhY8Zq3PafJxeJzhOejaUkPaHiF1y9PrF5I4vP/weG5FAE2GRg6pIy9V Xkv2tbsCVXq+686hNh3s81Y2FNgvDpJYr87dYW8Ev+sZWoWoXn0fEUIGOVpeskcDnceT tzuSk2EiLUP1Z/c16DHsXl1kPRmiM/JmkKyQ/rTcOqqnVmqxLq+oW0HyAda6mEBJKsCY JpFfx543B7e84Lm5dLMbp+1bjcNR1Dx3r7o1EqRjLYwQY4sjpZysAXI5i++yu6VdZ8Ge HAMNGc+PgEU6fJ0RXU0rOq9WbBkp6fOxNY6dzgbqJLCN3/X6cKIvcV2E6oQCEjSW0/yU qm5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=mGyUVyP/YIilROi09JLAsVYF0Cnc1Gto1FL7/yIdvWI=; b=pszfATKZGoLvS2z3z6FIBkB699mS8P14SyMZPlvMHBifR6xK4C9yxxTQRCg5Xkkl1x Zu9DFJ0OH1rX4oL65tWbjViJzlBnq1YJtYFslX599j5+LkhMwqi57T3lxltsAuySynhP UqTr2V1ZUY0rdULambEcZb+myWc6O7Oa4+tTlmh6JtwgXpebJMRGWRfVUNWGa1FVZvms QCuBrsvZlC3uETbMQPf20HjDU7G/Db6UKX4Irqx+t+fNwiWrj6lonDVGFKrmkPNlgvj1 LIYSGrwgvK2KfKIN/xLDwnpYJpAJQZEP1MR7zzLeYb7l6u46Fp1DxZRiu2tdJgACnGBr uU+Q== X-Gm-Message-State: AMCzsaVBI8RFpY38Swg1t3OVBe/OrfrlLV+U0lqqosDkW70ddoI6Dmo8 +PI65ueJg86+ePBsVufwYDhLbPHgwFJk+jJSUZBh X-Google-Smtp-Source: AOwi7QDjmhR3suys2TaMVwdpRjd8G15Yt+FgqM8pUnWOa1TkilrsE1jHmM2iHDpxZurLyfvRINsX+sk+XgpUERx3Ues= X-Received: by 10.46.3.1 with SMTP id 1mr6337068ljd.147.1507656965486; Tue, 10 Oct 2017 10:36:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.38.146 with HTTP; Tue, 10 Oct 2017 10:35:34 -0700 (PDT) In-Reply-To: References: From: Juan Manuel Palacios Date: Tue, 10 Oct 2017 13:35:34 -0400 Message-ID: Subject: Re: Trying to understand confusing 'zfs diff' output To: freebsd-fs@freebsd.org 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: Tue, 10 Oct 2017 17:36:08 -0000 Hi everyone, I sent this question some weeks ago but got no response. Pinging again to see if anyone has any clues, thanks! On Tue, Sep 19, 2017 at 12:13 PM, Juan Manuel Palacios wrote: > Hi everyone, > > I'm trying to understand a result I'm seeing when comparing the diff of > two local ZFS snapshots that were successfully replicated to a remote pool > over SSH against the diff of their remote counterparts. The latter shows > three files as having been deleted, while the local diff of the exact same > two snapshots doesn't. > > Following are those diffs, with empty lines entered manually into the > local diff where the remote one shows the deleted files; moreover, lines > right above & below this confusing part of the diffs have been trimmed for > brevity's sake, since they were identical across both outputs. > > 1) Local diff (FreeBSD 10.3-RELEASE-p21 system): > > -> zfs diff zroot/mysql@automated_2017-07-31_23:45:04-EDT > zroot/mysql@automated_2017-08-01_23:45:03-EDT | gawk '{ match($2, > /\/(.*)/, matches); printf "%s\t%s\n", $1, matches[1]; }' > (trimmed) > M mysql/data/knet@002dlrs/lrs_providers.ibd > > M mysql/data/snap/sessions.ibd > M mysql/data/knet@002dlrs/sessions.ibd > M mysql/data/leads/demo_requests.ibd > M mysql/tmp/nk-dev.sql.gz > > > M mysql/data/knet/account_manager_memberships.ibd > (trimmed) > > > 2) Remote diff (FreeBSD 10.3-RELEASE-p19 system): > > -> zfs diff backup/mysql@automated_2017-07-31_23:45:04-EDT > backup/mysql@automated_2017-08-01_23:45:03-EDT | gawk '{ match($2, > /\/mnt\/backup\/(.*)/, matches); printf "%s\t%s\n", $1, matches[1]; }' > (trimmed) > M mysql/data/knet@002dlrs/lrs_providers.ibd > - mysql/tmp/nk-dump--2017-07-19_01:32:16-EDT.sql > M mysql/data/snap/sessions.ibd > M mysql/data/knet@002dlrs/sessions.ibd > M mysql/data/leads/demo_requests.ibd > M mysql/tmp/nk-dev.sql.gz > - mysql/replication/mysql-bin.001241 > - mysql/replication/mysql-bin.001242 > M mysql/data/knet/account_manager_memberships.ibd > (trimmed) > > So, as I was saying, the remote diff shows these three files as having > been deleted, because they were: > > 1) Locally: > > -> ls -l /mysql/.zfs/snapshot/automated_2017-07-31_23\:45\:04-EDT/ > tmp/nk-dump--2017-07-19_01\:32\:16-EDT.sql > -rw-r--r-- 1 jmpp jmpp 46M Jul 19 01:32 /mysql/.zfs/snapshot/automated > _2017-07-31_23:45:04-EDT/tmp/nk-dump--2017-07-19_01:32:16-EDT.sql > > -> ls -l /mysql/.zfs/snapshot/automated_2017-08-01_23\:45\:03-EDT/ > tmp/nk-dump--2017-07-19_01\:32\:16-EDT.sql > ls: /mysql/.zfs/snapshot/automated_2017-08-01_23:45:03-EDT/tmp/ > nk-dump--2017-07-19_01:32:16-EDT.sql: No such file or directory > > > 2) On the remote pool: > > -> ls -l /mnt/backup/mysql/.zfs/snapshot/automated_2017-07-31_23\:45\ > :04-EDT/tmp/nk-dump--2017-07-19_01:32:16-EDT.sql > -rw-r--r-- 1 1001 1001 48288840 Jul 18 22:32 > /mnt/backup/mysql/.zfs/snapshot/automated_2017-07-31_23:45: > 04-EDT/tmp/nk-dump--2017-07-19_01:32:16-EDT.sql > > -> ls -l /mnt/backup/mysql/.zfs/snapshot/automated_2017-08-01_23\:45\ > :03-EDT/tmp/nk-dump--2017-07-19_01:32:16-EDT.sql > ls: /mnt/backup/mysql/.zfs/snapshot/automated_2017-08-01_23:45: > 03-EDT/tmp/nk-dump--2017-07-19_01:32:16-EDT.sql: No such file or directory > > And so for the other two files. > > So, my question is, if the remote diff is correct in showing these files > as having been deleted between the two snapshots (it *is* correct in doing > that, right?), why does the local diff not show it also? > > Thanks in advance for any help! > > -- > Juan Palacios > Senior Software Architect > > 135 West 26th St l 12th Floor l NY, NY 10001 > 212.675.9234 <(212)%20675-9234> l 646.217.3677 <(646)%20217-3677> > > Register for our upcoming webinar with The Healthy Minds Network and > AUCCCD: > Trends in Higher Education Mental Health: Research Highlights > > > Connect with us! > > > > -- Juan Palacios Senior Software Architect 135 West 26th St l 12th Floor l NY, NY 10001 212.675.9234 l 646.217.3677 Register for our upcoming webinar with The Healthy Minds Network and AUCCCD: Trends in Higher Education Mental Health: Research Highlights Connect with us! From owner-freebsd-fs@freebsd.org Thu Oct 12 08:28:07 2017 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 050D2E48021 for ; Thu, 12 Oct 2017 08:28:07 +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 E24306C83A for ; Thu, 12 Oct 2017 08:28:06 +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 v9C8S6O6094278 for ; Thu, 12 Oct 2017 08:28:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 218626] [PATCH] cuse: new error code CUSE_ERR_NO_DEVICE (ENODEV) Date: Thu, 12 Oct 2017 08:28:07 +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 Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED 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: Thu, 12 Oct 2017 08:28:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218626 --- Comment #9 from commit-hook@freebsd.org --- A commit references this bug: Author: hselasky Date: Thu Oct 12 08:27:58 UTC 2017 New revision: 324546 URL: https://svnweb.freebsd.org/changeset/base/324546 Log: MFC r324320: Add support for new cuse(3) error code, CUSE_ERR_NO_DEVICE. This error code is useful when emulating Linux input event devices from userspace. PR: 218626 Submitted by: jan.kokemueller@gmail.com Sponsored by: Mellanox Technologies Changes: _U stable/11/ stable/11/lib/libcuse/cuse.3 stable/11/sys/fs/cuse/cuse.c stable/11/sys/fs/cuse/cuse_defs.h --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Oct 12 20:58:17 2017 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 ABBABE34895 for ; Thu, 12 Oct 2017 20:58:17 +0000 (UTC) (envelope-from juergen.gotteswinter@internetx.com) Received: from mx1.internetx.com (mx1.internetx.com [62.116.129.39]) by mx1.freebsd.org (Postfix) with ESMTP id 3797F66E60 for ; Thu, 12 Oct 2017 20:58:16 +0000 (UTC) (envelope-from juergen.gotteswinter@internetx.com) Received: from localhost (localhost [127.0.0.1]) by mx1.internetx.com (Postfix) with ESMTP id 6C3564C4C7EC for ; Thu, 12 Oct 2017 22:52:41 +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 BoCuvx1rvLGL for ; Thu, 12 Oct 2017 22:52:38 +0200 (CEST) Received: from [192.168.100.26] (pizza.internetx.de [62.116.129.3]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mx1.internetx.com (Postfix) with ESMTPSA id ADBA34C4C705 for ; Thu, 12 Oct 2017 22:52:38 +0200 (CEST) Reply-To: jg@internetx.com Subject: Re: ZFS stalled after some mirror disks were lost To: freebsd-fs@freebsd.org References: <4A0E9EB8-57EA-4E76-9D7E-3E344B2037D2@gmail.com> <82632887-E9D4-42D0-AC05-3764ABAC6B86@gmail.com> <20171007150848.7d50cad4@fabiankeil.de> From: InterNetX - Juergen Gotteswinter Organization: InterNetX GmbH Message-ID: <6d1c80df-7e9f-c891-31ae-74dad3f67985@internetx.com> Date: Thu, 12 Oct 2017 22:52:34 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US 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, 12 Oct 2017 20:58:17 -0000 Am 07.10.2017 um 15:57 schrieb Ben RUBSON >> Indeed. In the face of other types of errors as well, though. >> >>>> Essentially, each logical i/o request obtains a configuration lock of >>>> type 'zio' in shared mode to prevent certain configuration changes >>>> from happening while there are any outsanding zio-s. >>>> If a zio is lost, then this lock is leaked. >>>> Then, the code that deals with vdev failures tries to take this lock in >>>> exclusive mode while holding a few other configuration locks also in >>>> exclsuive mode so, any other thread needing those locks would block. >>>> And there are code paths where a configuration lock is taken while >>>> spa_namespace_lock is held. >>>> And when spa_namespace_lock is never dropped then the system is close >>>> to toast, because all pool lookups would get stuck. >>>> I don't see how this can be fixed in ZFS. >> >> While I haven't used iSCSI for a while now, over the years I've seen >> lots of similar issues with ZFS pools located on external USB disks <3 >> and ggate devices (backed by systems with patches for the known data >> corruption issues). Ben started a discussion about his setup a few months ago, where he described what he is going to do. And, at least my (and i am pretty sure there where others, too) prophecy was that it will end up in a pretty unreliable setup (gremlins and other things are included!) which is far far away from being helpful in term of HA. A single node setup, with reliable hardware configuration and as little as possible moving parts, whould be way more reliable and flawless. but anyhow, i hate (no i dont in that case) to say "told you so" its like using tons of external usb disks hooked up to flaky consumer grade controllers, creating a raidz on top of it and start looking surprised when the pool starts going crazy. sorry for being a ironic dick, its frustrating... > > There's no mention to code revision in this thread. > It finishes with a message from Alexander Motin : > "(...) I've got to conclusion that ZFS in many places > written in a way that simply does not expect errors. In such cases it > just stucks, waiting for disk to reappear and I/O to complete. (...)" > yep, nothing new? if the underlying block device works like expected a error should be returned to zfs, but noone knows what happens in this setup during failure. maybe its some switch issue, or network driver bug which prevents this and stalls the pool. who knows, what errors probably already got masked through the additional iscsi layer between phys. disk and zfs. lots of fun included for future issues. for a ha setup, its funny to add as much components as possible just to somehow get it look like ha. its the complete opposite, no matter what one would call it. >> I'm not claiming that the patch or other workarounds I'm aware of >> would actually help with your ZFS stalls at all, but it's not obvious >> to me that your problems can actually be blamed on the iSCSI code >> either. >> i would guess that its not an direct issue of the ctld, but its just a guess... @ben can you post your iscsi network configuration including ctld.conf and so on? is your iscsi setup using multipath, lacp or is it just single pathed? overall... ben is stacking up way too much layers which prevent root cause diagnostic. lets see, i am trying to describe what i see here (please correct me if this setup is different from my thinking). i think, to debug this mess, its absolutely necessary to see all involved components - physical machine(s), exporting single raw disks via iscsi to "frontends" (please provide exact configuration, software versions, and built in hardware -> especially nic models, drivers, firmware) - switch infrastructure (brand, model, firmware version, line speed, link aggregation in use? if yes, lacp or whatever is in use here?) - single switch or stacked setup? - frontend boxes, importing the raw iscsi disks for a zpool (again, exact hardware configuration, network configuration, driver / firmware versions and so on) did one already check the switch logs / error counts? another thing which came to my mind is, if has zfs ever been designed to be used on top of iscsi block devices? my thoughts so far where that zfs loves native disks, without any layer between (no volume manager, no partitions, no nothing). most ha setups i have seen so far where using rock solid cross over cabled sas jbods with on demand activated paths in case of failure. theres not that much that can cause voodoo in such setups, compared to iscsi ha however failover scenarios with tons of possible problematic components in between. >> Did you try to reproduce the problem without iSCSI? i bet the problem wont occur anymore on native disks. which should NOT mean that zfs cant be used on iscsi devices, i am pretty sure it will work fine... as long as: - iscsi target behavior is doing well, which includes that no strange bugs start partying on your san network - rock solid stable networking, no hickups, no retrans, no loss, no nothing (dont forget to 100% seperate san traffic from other traffic, better go for completely dedicated switches which only handle san traffic) - no nic driver / firmware issues - no switch firmware issues the point is, with this kind of setup you get that much components into the game that its nearly impossible to figure out where the vodoo comes from. its getting even more worse with ha setups using such a infrastructure, which need to be debugged while stay into production. >> Anyway, good luck with your ZFS-on-iscsi issue(s). good luck from me, too. whould be very interesting which caused this issue. until the next one pops up > > Thank you very much Fabian for your help and contribution, > I really hope we'll find the root cause of this issue, > as it's quite annoying in a HA-expected production environment :/ > the point with ha setups is... planning, planning, planning, testing, testing, praying & hoping that nothing unexpected will happen to your setup. its always somehow a gamble, and in there will be still enough situations where a well planned ha setup will still fail. but, usually its a pretty good starting point to keep things as simple as possible when designing such setups. extra layers like iscsi in this case are nothing which should be seen as "keeping things simple", this things are a good way to prepare a ha setup to fail with whatever obscure issues. debugging is a bit... overall, please forgive my ironic writing > 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 Fri Oct 13 02:43:18 2017 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 40051E3B0ED for ; Fri, 13 Oct 2017 02:43:18 +0000 (UTC) (envelope-from shiva.bhanujan@quorum.com) Received: from asp.reflexion.net (outbound-mail-210-77.reflexion.net [208.70.210.77]) (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 E2A0870D04 for ; Fri, 13 Oct 2017 02:43:16 +0000 (UTC) (envelope-from shiva.bhanujan@quorum.com) Received: (qmail 6989 invoked from network); 13 Oct 2017 02:43:09 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 13 Oct 2017 02:43:09 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.40.3) with SMTP; Thu, 12 Oct 2017 22:43:10 -0400 (EDT) Received: (qmail 21695 invoked from network); 13 Oct 2017 02:43:09 -0000 Received: from unknown (HELO mail.quorum.net) (64.74.133.216) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 13 Oct 2017 02:43:09 -0000 Received: from QLEXC01.Quorum.local ([fe80::edb6:63d5:778f:2f0e]) by QLEXC01.Quorum.local ([fe80::edb6:63d5:778f:2f0e%14]) with mapi id 14.03.0351.000; Thu, 12 Oct 2017 19:43:08 -0700 From: Shiva Bhanujan To: "freebsd-fs@freebsd.org" Subject: FreeBSD 10.3/11.0 SCSI errors with Symbios Logic SAS3008 PCI-Express Fusion-MPT SAS-3 Thread-Topic: FreeBSD 10.3/11.0 SCSI errors with Symbios Logic SAS3008 PCI-Express Fusion-MPT SAS-3 Thread-Index: AQHTQ80AKMPHqs1A+0yLHlbMiv8g5A== Date: Fri, 13 Oct 2017 02:43:08 +0000 Message-ID: <3A5A10BE32AC9E45B4A22F89FC90EC0701C3665D5D@QLEXC01.Quorum.local> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [24.6.174.236] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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: Fri, 13 Oct 2017 02:43:18 -0000 Hello,=0A= =0A= I have a FreeBSD 10.3 install in a HVM on XenServer 6.5. The HBA330 SAS-3 = controller is in pcipassthrough mode to the FreeBSD VM. When I try to acce= ss the disks (/dev/da0...) using gpart, I get SCSI errors, like the followi= ng:=0A= =0A= (da0:mpr0:0:0:0): CAM status: SCSI Status Error=0A= (da0:mpr0:0:0:0): SCSI status: Check Condition=0A= (da0:mpr0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command ope= ration code)=0A= =0A= I get the same errors w/ FreeBSD 11.0 also.=0A= =0A= Please note, that these errors don't show up on a Fusion-MPT SAS-2 controll= er, or a MegaRAID SAS 2208 controller. Additionally, FreeBSD 10.2 doesn't = have any SCSI errors on the HBA330 SAS-3 controller either. =0A= =0A= Is there a different version of the mpr driver I should be using? I haven'= t checked the differences between the mpr driver in 10.2 vs 10.3 and 11.0. = I do see that there are others who have experienced these issues. Can som= ebody please provide me some pointers as to why this is occurring? Or if t= here are some driver changes that I might be able to incorporate?=0A= =0A= Regards,=0A= Shiva=0A= =0A= From owner-freebsd-fs@freebsd.org Fri Oct 13 16:58:35 2017 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 78692E273DD for ; Fri, 13 Oct 2017 16:58:35 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::241]) (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 069476D295 for ; Fri, 13 Oct 2017 16:58:35 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wr0-x241.google.com with SMTP id y44so1231427wry.2 for ; Fri, 13 Oct 2017 09:58:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=OLXZYhwNpFg+7LfT3d70kZE2axZynW14Di1wIvLXASE=; b=sZrVAKP5uxuF2J/S5Rp1gPSTzSfVbkchCY359KitifGZNZhH5+ceb8UzduYi0J0YuY fLiJhtAahlmzCiRQvVzjuDJUwxVAdT/jRU2IeBtBBKYRgNZG2XwgQgtSMR2yT649IuQq VHgP+L6+BIEY3Iyli/WJobyQENMPy31jYrjHlhY1gqFTaUq1XUOnRomgQmQJq8t5UK3+ DEpuOGklgIxk6Mqsn/Odn4aPswxj9l44Piudjzwz32t8c5q5tVgnDB3L4OId/JgnFZic VLItWMB30bbyvE5uYkkB/+pHGQTHbJ08noTSuK/d/MZIDeTz+XlF3K/wQTYQjTunlnQD YWYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=OLXZYhwNpFg+7LfT3d70kZE2axZynW14Di1wIvLXASE=; b=XNAe4+GiA44MPu3OdRFnOflF9aDQUridWab9DGEt5/09MOKV84W8DnPlleEOJ09wGP NEojJf75F5wwrCeYUJ+R9aQoSFCXnXseaIYRpXQwk/tSGKSHAeuLBvQxqhSv5eWKbirY 3Dhgxr99UO0olo3umgvXU3D3729AU+FnYhZMF6L7Nvxpa4KpkPTEx3D0RFGC0C/kOwec wr+5JVdfg1XIpBuKAtUq4QCWLFsLF5mazWjsZm5NY+hpPfG4QYsqO1bCYQy0JTUdk32Q hoLwMRCVCwOijN9kMvnm/ItkRoKTKECANl+FqeP/CtBMWGeeOJdc+v3yc2qy/D5r0awS JgrQ== X-Gm-Message-State: AMCzsaUbEzePSNBhAcslzawcf1qtVOPs8bgM8UEPEpBeFt81Q9Vp9EK+ AKWIVOuBhpLODcgnGddFvSpF99mS X-Google-Smtp-Source: AOwi7QCzD4TSilR2oXD6+OHYNOb4DPB4zJCbNCpCUC9Xt16Cvf8eYC4hQI/yYsUPf9j6C01XyzmtuQ== X-Received: by 10.223.161.156 with SMTP id u28mr1788055wru.244.1507913913084; Fri, 13 Oct 2017 09:58:33 -0700 (PDT) Received: from bens-mac.home (LFbn-MAR-1-445-220.w2-15.abo.wanadoo.fr. [2.15.38.220]) by smtp.gmail.com with ESMTPSA id i16sm2520283wrf.19.2017.10.13.09.58.31 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 13 Oct 2017 09:58:32 -0700 (PDT) Content-Type: text/plain; charset=us-ascii; delsp=yes; format=flowed Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: ZFS stalled after some mirror disks were lost From: Ben RUBSON In-Reply-To: <6d1c80df-7e9f-c891-31ae-74dad3f67985@internetx.com> Date: Fri, 13 Oct 2017 18:58:30 +0200 Content-Transfer-Encoding: 7bit Message-Id: <13AF09F5-3ED9-4C81-A5E2-94BA770E991B@gmail.com> References: <4A0E9EB8-57EA-4E76-9D7E-3E344B2037D2@gmail.com> <82632887-E9D4-42D0-AC05-3764ABAC6B86@gmail.com> <20171007150848.7d50cad4@fabiankeil.de> <6d1c80df-7e9f-c891-31ae-74dad3f67985@internetx.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, 13 Oct 2017 16:58:35 -0000 On 12 Oct 2017 22:52, InterNetX - Juergen Gotteswinter wrote: > Ben started a discussion about his setup a few months ago, where he > described what he is going to do. And, at least my (and i am pretty sure > there where others, too) prophecy was that it will end up in a pretty > unreliable setup (gremlins and other things are included!) which is far > far away from being helpful in term of HA. A single node setup, with > reliable hardware configuration and as little as possible moving parts, > whould be way more reliable and flawless. First, thank you for your answer Juergen, I do appreciate it, of course, as well as the help you propose below. So thank you ! :) Yes, the discussion, more than one year ago now, on this list, was named "HAST + ZFS + NFS + CARP", but quickly moved around iSCSI when I initiated the idea :) I must say, after one year of production, that I'm rather happy with this setup. It works flawlessly (but the current discussed issue of course), and I switched from one node to another several times, successfully. Main purpose of the previous discussion was to have a second chassis to host the pool in case of a failure with the first one. > (...) if the underlying block device works like expected a > error should be returned to zfs, but noone knows what happens in this > setup during failure. maybe its some switch issue, or network driver bug > which prevents this and stalls the pool. The issue only happens when I disconnect iSCSI drives, it does not occurs suddenly by itself. So I would say the issue is on FreeBSD side, not network hardware :) 2 distinct behaviours/issues : - 1 : when I disconnect iSCSI drives from the server running the pool (iscsictl -Ra), some iSCSI drives remain on the system, leaving ZFS stalled ; - 2 : when I disconnect iSCSI drives from the target (shut NIC down / shutdown ctld), server running the pool sometimes panics (traces in my previous mail, 06/10). > @ben > > can you post your iscsi network configuration including ctld.conf and so > on? is your iscsi setup using multipath, lacp or is it just single pathed? Sure. So I use single pathed iSCSI. ### Target side : # /etc/ctl.conf (all targets are equally configured) : target iqn.............:hm1 { portal-group pg0 au0 alias G1207FHRDP2SThm lun 0 { path /dev/gpt/G1207FHRDP2SThm serial G1207FHRDP2SThm } } So, each target has its GPT label to clearly & quickly identify it (location, serial). Best practice, which I find to be very useful, taken from storage/ZFS books from Michael W Lucas & Allan Jude. ### Initiator side : # /etc/iscsi.conf (all targets are equally configured) : hm1 { InitiatorName = iqn............. TargetAddress = 192.168.2.2 TargetName = iqn.............:hm1 HeaderDigest = CRC32C DataDigest = CRC32C } Then, each disk is geom-labeled (glabel label) so that the previous example disk appears on initiator side in : /dev/label/G1207FHRDP2SThm Still the naming best practice which allows me to identify a disk wherever it is, without mistake. ZFS thus uses /dev/label/ paths. NAME STATE READ WRITE CKSUM home ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 label/G1203_serial_hm ONLINE 0 0 0 label/G1204_serial_hm ONLINE 0 0 0 label/G2203_serial_hm ONLINE 0 0 0 label/G2204_serial_hm ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 label/G1205_serial_hm ONLINE 0 0 0 label/G1206_serial_hm ONLINE 0 0 0 label/G2205_serial_hm ONLINE 0 0 0 label/G2206_serial_hm ONLINE 0 0 0 cache label/G2200_serial_ch ONLINE 0 0 0 label/G2201_serial_ch ONLINE 0 0 0 (G2* are local disks, G1* are iCSCI disks) > overall... > > ben is stacking up way too much layers which prevent root cause diagnostic. > > lets see, i am trying to describe what i see here (please correct me if > this setup is different from my thinking). i think, to debug this mess, > its absolutely necessary to see all involved components > > - physical machine(s), exporting single raw disks via iscsi to > "frontends" (please provide exact configuration, software versions, and > built in hardware -> especially nic models, drivers, firmware) > > - frontend boxes, importing the raw iscsi disks for a zpool (again, > exact hardware configuration, network configuration, driver / firmware > versions and so on) Exact same hardware and software on both sides. FreeBSD 11.0-RELEASE-p12 SuperMicro motherboard ECC RAM NIC Mellanox ConnectX-3 40G fw 2.36.5000 HBA SAS 2008 LSI 9211-8i fw 20.00.07.00-IT SAS-only disks (no SATA) > - switch infrastructure (brand, model, firmware version, line speed, > link aggregation in use? if yes, lacp or whatever is in use here?) > > - single switch or stacked setup? > > did one already check the switch logs / error counts? No, as issue seems to come from FreeeBSD (easily reproductible with the 2 scenarios I gave above). > another thing which came to my mind is, if has zfs ever been designed to > be used on top of iscsi block devices? my thoughts so far where that zfs > loves native disks, without any layer between (no volume manager, no > partitions, no nothing). most ha setups i have seen so far where using > rock solid cross over cabled sas jbods with on demand activated paths in > case of failure. theres not that much that can cause voodoo in such > setups, compared to iscsi ha however failover scenarios with tons of > possible problematic components in between. We analyzed this in the previous topic : https://lists.freebsd.org/pipermail/freebsd-fs/2016-July/023503.html https://lists.freebsd.org/pipermail/freebsd-fs/2016-July/023527.html >>> Did you try to reproduce the problem without iSCSI? > > i bet the problem wont occur anymore on native disks. which should NOT > mean that zfs cant be used on iscsi devices, i am pretty sure it will > work fine... as long as: > > - iscsi target behavior is doing well, which includes that no strange > bugs start partying on your san network > (...) Andriy, who took many debug traces from my system, managed to reproduce the first issue locally, using a 3-way ZFS mirror with one local disk plus two iSCSI disks. Sounds like there is a deadlock issue on iSCSI initiator side (of course Andriy feel free to correct me if I'm wrong). Regarding the second issue, I'm not able to reproduce it if I don't use geom-labels. There may then be an issue on geom-label side (which could then also affect fully-local ZFS pools using geom-labels). Thank you again, Ben From owner-freebsd-fs@freebsd.org Fri Oct 13 17:46:53 2017 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 9B12CE28542 for ; Fri, 13 Oct 2017 17:46: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 7E21D6EB03 for ; Fri, 13 Oct 2017 17:46: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 v9DHkq0t010810 for ; Fri, 13 Oct 2017 17:46:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 204643] [msdosfs] [panic] Crash while accessing files with large, non-english names Date: Fri, 13 Oct 2017 17:46: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: 9.3-RELEASE X-Bugzilla-Keywords: patch, security X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: emaste@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: 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: Fri, 13 Oct 2017 17:46:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204643 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress --- Comment #9 from Ed Maste --- A change has been committed to HEAD and merged to stable/10 -- is this now resolved? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Oct 13 17:49:29 2017 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 A1916E28685 for ; Fri, 13 Oct 2017 17:49:29 +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 902436EC32 for ; Fri, 13 Oct 2017 17:49:29 +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 v9DHnTGC014713 for ; Fri, 13 Oct 2017 17:49:29 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 204643] [msdosfs] [panic] Crash while accessing files with large, non-english names Date: Fri, 13 Oct 2017 17:49:29 +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: 9.3-RELEASE X-Bugzilla-Keywords: patch, security X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kp@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: 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: Fri, 13 Oct 2017 17:49:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204643 --- Comment #10 from Kristof Provost --- (In reply to Ed Maste from comment #9) The panic is resolved, yes. I think this can be closed. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Oct 13 18:58:18 2017 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 85823E2A259 for ; Fri, 13 Oct 2017 18:58:18 +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 7363C71076 for ; Fri, 13 Oct 2017 18:58:18 +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 v9DIwHS2024154 for ; Fri, 13 Oct 2017 18:58:18 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 204643] [msdosfs] [panic] Crash while accessing files with large, non-english names Date: Fri, 13 Oct 2017 18:58:18 +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: 9.3-RELEASE X-Bugzilla-Keywords: patch, security X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kp@freebsd.org X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: kp@freebsd.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution assigned_to 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: Fri, 13 Oct 2017 18:58:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204643 Kristof Provost changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Assignee|freebsd-fs@FreeBSD.org |kp@freebsd.org Status|In Progress |Closed --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Oct 14 01:05:06 2017 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 5F2E3E32010 for ; Sat, 14 Oct 2017 01:05:06 +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 4DFBD7FF24 for ; Sat, 14 Oct 2017 01:05:06 +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 v9E1567O034540 for ; Sat, 14 Oct 2017 01:05:06 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 222929] ZFS ARC stats have wrong count Date: Sat, 14 Oct 2017 01:05:06 +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.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@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: assigned_to 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: Sat, 14 Oct 2017 01:05:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222929 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Oct 14 23:42:43 2017 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 0EA2EE2FBBF for ; Sat, 14 Oct 2017 23:42:43 +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 F176263A for ; Sat, 14 Oct 2017 23:42:42 +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 v9ENggVp068598 for ; Sat, 14 Oct 2017 23:42:42 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223015] [tmpfs] tmpfs does not support sparse files Date: Sat, 14 Oct 2017 23:42:43 +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: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@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: assigned_to 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: Sat, 14 Oct 2017 23:42:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223015 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.=