From owner-freebsd-fs@freebsd.org Sun Apr 29 01:37:07 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C22DFFBF531 for ; Sun, 29 Apr 2018 01:37:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5325B7E437 for ; Sun, 29 Apr 2018 01:37:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 16B0DFBF52E; Sun, 29 Apr 2018 01:37:06 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04573FBF52D for ; Sun, 29 Apr 2018 01:37:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 96CBB7E41C for ; Sun, 29 Apr 2018 01:37:05 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id E0F9614F4E for ; Sun, 29 Apr 2018 01:37:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3T1b4f7067623 for ; Sun, 29 Apr 2018 01:37:04 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3T1b4Zc067622 for fs@FreeBSD.org; Sun, 29 Apr 2018 01:37:04 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 217560] FAT32 - Time stamp of file is one hour off Date: Sun, 29 Apr 2018 01:37:05 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: damjan.jov@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 01:37:07 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217560 Damjan Jovanovic changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |damjan.jov@gmail.com --- Comment #4 from Damjan Jovanovic --- There is definitely some timestamp bug here. In my UTC+2 timezone: $ date=20=20 Sun Apr 29 03:23:58 SAST 2018 $ touch bsd-201804290323.txt $ stat -x bsd-201804290323.txt=20 File: "bsd-201804290323.txt" Size: 0 FileType: Regular File Mode: (0755/-rwxr-xr-x) Uid: ( 1002/ user) Gid: ( 0/ whee= l) Device: 0,139 Inode: 59620 Links: 1 Access: Sun Apr 29 02:00:00 2018 Modify: Sun Apr 29 05:23:58 2018 Change: Sun Apr 29 05:23:58 2018 Windows shows the correct modified/changed times of 03:23. Why is FreeBSD adding my time zone offset (2 hours) to the times when stat reads them, even though they are already in local time? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Apr 29 03:37:56 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E6A2FC3194 for ; Sun, 29 Apr 2018 03:37:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E7B2976CEE for ; Sun, 29 Apr 2018 03:37:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AB8BFFC3193; Sun, 29 Apr 2018 03:37:55 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9941BFC3192 for ; Sun, 29 Apr 2018 03:37:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 33FD476CEA for ; Sun, 29 Apr 2018 03:37:55 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7F26816017 for ; Sun, 29 Apr 2018 03:37:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3T3bsKK075247 for ; Sun, 29 Apr 2018 03:37:54 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3T3bsxt075246 for fs@FreeBSD.org; Sun, 29 Apr 2018 03:37:54 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 217560] FAT32 - Time stamp of file is one hour off Date: Sun, 29 Apr 2018 03:37:54 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: damjan.jov@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 03:37:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217560 --- Comment #5 from Damjan Jovanovic --- Created attachment 192889 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D192889&action= =3Dedit Use vfs_timestamp() instead of getnanotime() in msdosfs I've noticed msdosfs uses getnanotime() to generate timestamps, unlike ufs, ext2fs, devfs, nandfs, nfsclient, nfsserver, and tmpfs, which all use the better vfs_timestamp() function instead (which allows filesystem timestamp granularity to be configured using the vfs.timestamp_precision sysctl). Only autofs and msdosfs use getnanotime(). Patching msdosfs to use vfs_timestamp() instead, seems to also fix this bug here, with msdosfs timestamps having the timezone offset added to them a se= cond time when read. Please find my patch attached. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Apr 29 12:55:23 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA3E7FAC641 for ; Sun, 29 Apr 2018 12:55:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7551C6C0FA for ; Sun, 29 Apr 2018 12:55:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 33BC9FAC640; Sun, 29 Apr 2018 12:55:23 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 21202FAC63F for ; Sun, 29 Apr 2018 12:55:23 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A791E6C0F6 for ; Sun, 29 Apr 2018 12:55:22 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id DEDAA1ADB6 for ; Sun, 29 Apr 2018 12:55:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3TCtLKk059047 for ; Sun, 29 Apr 2018 12:55:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3TCtL57059046 for fs@FreeBSD.org; Sun, 29 Apr 2018 12:55:21 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 217560] FAT32 - Time stamp of file is one hour off Date: Sun, 29 Apr 2018 12:55:20 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 12:55:24 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217560 Konstantin Belousov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kib@FreeBSD.org --- Comment #6 from Konstantin Belousov --- (In reply to Damjan Jovanovic from comment #5) Change to use vfs_timestamp() should be fine by itself, but I cannot see how could it solve 'off by a hour' issue. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Apr 29 13:00:10 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4BBB8FAC78B for ; Sun, 29 Apr 2018 13:00:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D98E66C21B for ; Sun, 29 Apr 2018 13:00:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9A15FFAC78A; Sun, 29 Apr 2018 13:00:09 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 87A77FAC788 for ; Sun, 29 Apr 2018 13:00:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2371C6C217 for ; Sun, 29 Apr 2018 13:00: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D3AC21ADC5 for ; Sun, 29 Apr 2018 13:00:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3TD07vQ067426 for ; Sun, 29 Apr 2018 13:00:07 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3TD07M0067417 for fs@FreeBSD.org; Sun, 29 Apr 2018 13:00:07 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 217560] FAT32 - Time stamp of file is one hour off Date: Sun, 29 Apr 2018 13:00:06 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: damjan.jov@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 13:00:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217560 --- Comment #7 from Damjan Jovanovic --- (In reply to Konstantin Belousov from comment #6) By default vfs.timestamp_precision is TSP_USEC, which returns microtime() instead of getnanotime(). The timezone for microtime() seems to be more cor= rect than for getnanotime(). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Apr 29 13:24:01 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9066FACFAD for ; Sun, 29 Apr 2018 13:24:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 638DF6F46E for ; Sun, 29 Apr 2018 13:24:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1ED56FACFAC; Sun, 29 Apr 2018 13:24:01 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B9F2FACFAB for ; Sun, 29 Apr 2018 13:24:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 970B36F46A for ; Sun, 29 Apr 2018 13:24:00 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id B620B1B1DF for ; Sun, 29 Apr 2018 13:23:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3TDNxDG040191 for ; Sun, 29 Apr 2018 13:23:59 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3TDNx98040190 for fs@FreeBSD.org; Sun, 29 Apr 2018 13:23:59 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 217560] FAT32 - Time stamp of file is one hour off Date: Sun, 29 Apr 2018 13:23:59 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 13:24:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217560 --- Comment #8 from Konstantin Belousov --- (In reply to Damjan Jovanovic from comment #7) This does not make sense, there is no 'timezone', and esp. there is no 'more correct' timezone. The difference between e.g. getmicrotime() and microtime() is that get retu= rn current clock hands without quering hardware to get the most precise possib= le value for the timecounter. So the typical precision of of getXXX() is 1/hz, while precision of XXX() is around the precision of hardware. But both variants return UTC time as known by kernel. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Apr 29 14:07:34 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7F79FADCED for ; Sun, 29 Apr 2018 14:07:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 67FC4797AC for ; Sun, 29 Apr 2018 14:07:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 23DBAFADCE9; Sun, 29 Apr 2018 14:07:34 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 114BEFADCE8 for ; Sun, 29 Apr 2018 14:07:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9AD2679786 for ; Sun, 29 Apr 2018 14:07: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id D29561B779 for ; Sun, 29 Apr 2018 14:07:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3TE7WtG049974 for ; Sun, 29 Apr 2018 14:07:32 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3TE7WxK049973 for fs@FreeBSD.org; Sun, 29 Apr 2018 14:07:32 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 217560] FAT32 - Time stamp of file is one hour off Date: Sun, 29 Apr 2018 14:07:32 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: damjan.jov@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 14:07:35 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217560 --- Comment #9 from Damjan Jovanovic --- (In reply to Konstantin Belousov from comment #8) Thank you, I'll try that test again with a clean kernel rebuild. MICROTIME(9) does not document the timezone for the time functions. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Apr 29 14:29:27 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80B90FAE3A1; Sun, 29 Apr 2018 14:29:27 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (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 1BB447DE84; Sun, 29 Apr 2018 14:29:27 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 823ED2814A; Sun, 29 Apr 2018 16:29:24 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JgASCmEvMonn; Sun, 29 Apr 2018 16:29:23 +0200 (CEST) Received: from [192.168.11.152] (unknown [192.168.11.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id C859D28147; Sun, 29 Apr 2018 16:29:22 +0200 (CEST) Subject: Re: Getting ZFS pools back. To: Richard Yao Cc: FreeBSD Hackers , FreeBSD Filesystems References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> From: Willem Jan Withagen Message-ID: Date: Sun, 29 Apr 2018 16:29:24 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: nl Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 14:29:27 -0000 On 28/04/2018 20:43, Richard Yao wrote: > What is the output of ‘zpool import‘ with no arguments? If I boot thru aa mem-stick.... # zpool import # So, empty line In the mean time I rebuild the system. Was able to retreive the data by a convoluted incantation of 'zpool import -fmNF' or something like that. Made a full backup, and started fresh. --WjW >> On Apr 28, 2018, at 11:42 AM, Willem Jan Withagen wrote: >> >> >> Hi, >> >> I had this server crash on me, and first it just complained about not being able to boot because it could not find the guid. >> >> Now I cannot even import the pools any longer. >> Althoug zdb -l /dev/ada0 still gives me data that indicates that there should be a ZFS pool on that partition. >> >> Any suggestions on how to get the pools/data back online? >> >> Help would be highly appreciated, since restoring it from backups is going to quite some work. >> >> Thanx, >> --WjW >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-fs@freebsd.org Sun Apr 29 14:30:19 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09E4EFAE47D for ; Sun, 29 Apr 2018 14:30:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 988547DF3C for ; Sun, 29 Apr 2018 14:30:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4FBBDFAE47B; Sun, 29 Apr 2018 14:30:18 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3E281FAE47A for ; Sun, 29 Apr 2018 14:30:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D23587DF37 for ; Sun, 29 Apr 2018 14:30:17 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1ABAD1BA3B for ; Sun, 29 Apr 2018 14:30:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3TEUGsD096908 for ; Sun, 29 Apr 2018 14:30:16 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3TEUGBp096907 for fs@FreeBSD.org; Sun, 29 Apr 2018 14:30:16 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 217560] FAT32 - Time stamp of file is one hour off Date: Sun, 29 Apr 2018 14:30:16 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: damjan.jov@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 14:30:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217560 --- Comment #10 from Damjan Jovanovic --- (In reply to Damjan Jovanovic from comment #9) Something must have been wrong with my setup. With a clean kernel rebuild, I can no longer reproduce this bug, even without my patch. Sorry. That patch may still be worth committing regardless ;). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Apr 29 14:40:52 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A505FAEB72; Sun, 29 Apr 2018 14:40:52 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::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 00FE380D3B; Sun, 29 Apr 2018 14:40:51 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22a.google.com with SMTP id m18-v6so8962889lfb.0; Sun, 29 Apr 2018 07:40:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=+E4MjoDmPCpiOuF8DaCb5DcLt+yjN5KizG0ElaN+qAI=; b=g+FL8ihMfx9S4BuSv0zwuQO7ouHkfzxpz9b0U+CnxEjOC5k0E/KdhAnVYR4fQBTRcE hG2/RXzX5cxCfZqmkEGxzPI6Ku4r43owd9hdrM0lOeHwukk95dVwZYaerujDZ4xbwWN5 ku2dWEMpd93/jz59i9T6tPeHXxm7hRDiZ4SB3Jn/PfwG4QyusM+xGsVaGyVkLM1pFZ7J wWOza5/LGCe7v3gVW91AWejlWffnEgClM04hCOFEPafJZbLd+gfcZlWvTSe8W0qTGZcM d+HzSPMgR6XPjtpp0W4HjJGasVa0hONBZlPN1PBjTC8QVBEHlY6IEnZLfVu76rUfsg6k ovyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=+E4MjoDmPCpiOuF8DaCb5DcLt+yjN5KizG0ElaN+qAI=; b=EceIGJwJENZj5DYoH3pvGQkmdcoaEXaj1JukabtRmaacm6tDgJRKhj12kLahg9oPPd im+avPp9JvW6ShGtZZQMCeWDMSJH0cIsSxyS7//ygG4tRSms4/KqLda84uBmq+C5bnpp I3D9AnCl3ofhbTahdLJWhJL4Q4Q+YVni7kFeMN5wYQ6Rk9yxSwAPE1XABG27yCquXgKt oUheOaJv+8Fk6zYx1SyOxrhp05ZdTC5LDbGIfVLTPFbSufg5I1GItQXFsowLAWvGd6pB qGTJ5tAQOUBfKURB3LSG7HSCkpspwg8qT8Bit8TQzCq8ZH78c662iYm2vdL6yGnfyNm3 OhZA== X-Gm-Message-State: ALQs6tAoyvVjndNvQENm7fg1JlgOX4uvf1mi7UI0BND4YLy/J0l3wEf/ mnB7iCSjeT7XxAO21o2sQbFMmcIsAKmgFBM6E+c= X-Google-Smtp-Source: AB8JxZp5T+/Et2dtDU41VT5tF5YHE4XH8AXEVbQf4Or57w8h7azY6cbxmJmVo53tBPs8bFducNZajrh11B2LmNST0j4= X-Received: by 2002:a2e:9f03:: with SMTP id u3-v6mr5866932ljk.53.1525012850386; Sun, 29 Apr 2018 07:40:50 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.114.79 with HTTP; Sun, 29 Apr 2018 07:40:49 -0700 (PDT) In-Reply-To: References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> From: Alan Somers Date: Sun, 29 Apr 2018 08:40:49 -0600 X-Google-Sender-Auth: yBDCKqGUP-1u390c2CtLNYMiSE4 Message-ID: Subject: Re: Getting ZFS pools back. To: Willem Jan Withagen Cc: Richard Yao , FreeBSD Filesystems , FreeBSD Hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 14:40:52 -0000 So your kernel couldn't find the pool. That might be due to a GEOM module that wasn't loaded but should've been (were you using gmirror or geli or something?). Or you might've accidentally destroyed the pool. It would still show up in "zdb -l", albeit in the destroyed state. Or you might've accidentally destroyed the partition. If the pool had resided on the disk's last partition, then "zdb -l /dev/ada0" still would've seen the label, since there's a copy of the label at the end of the device. But if you've reused the disk, then there's no way to know for sure. -Alan On Sun, Apr 29, 2018 at 8:29 AM, Willem Jan Withagen wrote: > On 28/04/2018 20:43, Richard Yao wrote: > >> What is the output of =E2=80=98zpool import=E2=80=98 with no arguments? >> > > If I boot thru aa mem-stick.... > # zpool import > # > > So, empty line > In the mean time I rebuild the system. > > Was able to retreive the data by a convoluted incantation of > 'zpool import -fmNF' or something like that. > Made a full backup, and started fresh. > > --WjW > > > > On Apr 28, 2018, at 11:42 AM, Willem Jan Withagen wrote= : >>> >>> >>> Hi, >>> >>> I had this server crash on me, and first it just complained about not >>> being able to boot because it could not find the guid. >>> >>> Now I cannot even import the pools any longer. >>> Althoug zdb -l /dev/ada0 still gives me data that indicates that there >>> should be a ZFS pool on that partition. >>> >>> Any suggestions on how to get the pools/data back online? >>> >>> Help would be highly appreciated, since restoring it from backups is >>> going to quite some work. >>> >>> Thanx, >>> --WjW >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@f >>> reebsd.org" >>> >> >> > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > From owner-freebsd-fs@freebsd.org Sun Apr 29 16:07:48 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35E62FB0D18 for ; Sun, 29 Apr 2018 16:07:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BACE473D07 for ; Sun, 29 Apr 2018 16:07:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 75D74FB0D17; Sun, 29 Apr 2018 16:07:47 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 64876FB0D16 for ; Sun, 29 Apr 2018 16:07:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0089873CE6 for ; Sun, 29 Apr 2018 16:07: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 3978F1C84A for ; Sun, 29 Apr 2018 16:07:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3TG7kbV032306 for ; Sun, 29 Apr 2018 16:07:46 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3TG7kTM032305 for fs@FreeBSD.org; Sun, 29 Apr 2018 16:07:46 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 217560] FAT32 - Time stamp of file is one hour off Date: Sun, 29 Apr 2018 16:07:45 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 16:07:48 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217560 --- Comment #11 from Konstantin Belousov --- (In reply to Damjan Jovanovic from comment #10) Did you tweaked machdep.adjkerntz or machdep.wall_cmos_clock between tests ? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Apr 29 17:27:22 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A15ABFB28F8; Sun, 29 Apr 2018 17:27:22 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (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 309FA80FE0; Sun, 29 Apr 2018 17:27:22 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 8650E3D573; Sun, 29 Apr 2018 19:27:13 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q0qfoFa_30An; Sun, 29 Apr 2018 19:27:13 +0200 (CEST) Received: from [192.168.10.67] (opteron [192.168.10.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 211FC3D572; Sun, 29 Apr 2018 19:27:13 +0200 (CEST) Subject: Re: Getting ZFS pools back. To: Alan Somers Cc: Richard Yao , FreeBSD Filesystems , FreeBSD Hackers References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> From: Willem Jan Withagen Message-ID: <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> Date: Sun, 29 Apr 2018 19:27:12 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: nl Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 17:27:22 -0000 On 29-4-2018 16:40, Alan Somers wrote: > So your kernel couldn't find the pool.  That might be due to a GEOM > module that wasn't loaded but should've been (were you using gmirror or > geli or something?).  Or you might've accidentally destroyed the pool. > It would still show up in "zdb -l", albeit in the destroyed state.  Or > you might've accidentally destroyed the partition.  If the pool had > resided on the disk's last partition, then "zdb -l /dev/ada0" still > would've seen the label, since there's a copy of the label at the end of > the device.  But if you've reused the disk, then there's no way to know > for sure. Hi Alan, I still have one of the original disks of the mirror, but the system/hardware causing trouble is back in use in the DC. No geli, or anything other that basic GEOM was involved. Disks were running on GPT: boot swap zroot zfsdata And yes zdb -l was able to find both pools: zroot, and zfsdata. And I'm pretty sure I did not destroy them on purpose. ;-) Trouble started when I installed (freebsd-update) 11.1 over a running 10.4. Which is sort of scarry? But because the system needed to go back on the air, I did only so much to recover the original stuff. But it just kept naging me over the GUID it could not find. So for sake of progress I reinstalled the system on one of the mirror disks, keeping the other one. So I could hook that disk up to my Freetest play box, and see what that brings. If anyone is interested. But than again the zpool import could have fixed what was broken in the first place. Haven't looked at it yet, since the 12 hour straight session yesterday was enough for the weekend. --WjW > -Alan > > On Sun, Apr 29, 2018 at 8:29 AM, Willem Jan Withagen > wrote: > > On 28/04/2018 20:43, Richard Yao wrote: > > What is the output of ‘zpool import‘ with no arguments? > > > If I boot thru aa mem-stick.... > # zpool import > # > > So, empty line > In the mean time I rebuild the system. > > Was able to retreive the data by a convoluted incantation of > 'zpool import -fmNF' or something like that. > Made a full backup, and started fresh. > > --WjW > > > > On Apr 28, 2018, at 11:42 AM, Willem Jan Withagen > > wrote: > > > Hi, > > I had this server crash on me, and first it just complained > about not being able to boot because it could not find the guid. > > Now I cannot even import the pools any longer. > Althoug zdb -l /dev/ada0 still gives me data that indicates > that there should be a ZFS pool on that partition. > > Any suggestions on how to get the pools/data back online? > > Help would be highly appreciated, since restoring it from > backups is going to quite some work. > > Thanx, > --WjW From owner-freebsd-fs@freebsd.org Sun Apr 29 18:03:52 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 186A8FB3632 for ; Sun, 29 Apr 2018 18:03:52 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [162.217.114.50]) by mx1.freebsd.org (Postfix) with SMTP id 9602587EDD for ; Sun, 29 Apr 2018 18:03:51 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 24356 invoked by uid 89); 29 Apr 2018 17:57:08 -0000 Received: from c-24-0-179-87.hsd1.nj.comcast.net (HELO iMac.local) (jan@digitaldaemon.com@24.0.179.87) by digitaldaemon.com with SMTP; 29 Apr 2018 17:57:08 -0000 Subject: Re: Getting ZFS pools back. To: Willem Jan Withagen , Alan Somers Cc: FreeBSD Filesystems , FreeBSD Hackers , Richard Yao References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> From: Jan Knepper Message-ID: <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> Date: Sun, 29 Apr 2018 13:57:07 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 18:03:52 -0000 On 04/29/2018 13:27, Willem Jan Withagen wrote: > Trouble started when I installed (freebsd-update) 11.1 over a running > 10.4. Which is sort of scarry? This does sounds 'scary' as I am planning to do this in the (near) future... Has anyone else experienced issues like this? Generally I do build the new system software on a running system, but then go to single user mode to perform the actual install. I have done many upgrades like that over 18 or so years and never seen or heard of an issue alike this. Thanks! ManiaC++ Jan Knepper From owner-freebsd-fs@freebsd.org Sun Apr 29 18:14:49 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8919EFB3C5D for ; Sun, 29 Apr 2018 18:14:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2143A6AC12 for ; Sun, 29 Apr 2018 18:14:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id D9844FB3C5B; Sun, 29 Apr 2018 18:14:48 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C722DFB3C5A for ; Sun, 29 Apr 2018 18:14:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6284B6AC0E for ; Sun, 29 Apr 2018 18:14:48 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 956AD1DA27 for ; Sun, 29 Apr 2018 18:14:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3TIElmu000749 for ; Sun, 29 Apr 2018 18:14:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3TIElnN000747 for fs@FreeBSD.org; Sun, 29 Apr 2018 18:14:47 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 217560] FAT32 - Time stamp of file is one hour off Date: Sun, 29 Apr 2018 18:14:47 +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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: damjan.jov@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 18:14:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217560 --- Comment #12 from Damjan Jovanovic --- (In reply to Konstantin Belousov from comment #11) During my early tests, I did change CMOS clock to local time in the BIOS, a= nd run tzsetup selecting that the CMOS clock is in local time, but I still got= the same bad times after that. Most probably, between experimenting with several patches to the msdosfs co= de that passed utc=3D1 to fattime2timespec() and/or timespec2fattime(), and sometimes forgetting to run "make installkernel" after "make buildkernel", I ended up with a badly patched msdosfs binary, that kept giving bad times un= til I did a clean rebuild. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Apr 29 18:21:21 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B603EFB4128 for ; Sun, 29 Apr 2018 18:21:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::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 4D53B6D7BC for ; Sun, 29 Apr 2018 18:21:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x236.google.com with SMTP id 144-v6so7583951iti.5 for ; Sun, 29 Apr 2018 11:21:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=uABNZlQvDTp99jAU0v/nbxCtH4T5u38kO+tuOl5zvH8=; b=yZPVXaXgSzpTdA4IjfpjuzIEeEOifcJQ9RPJXlvLaUY2TByF9sJGEGYQfZAlt/vGsf eimtteFiq/J2+cUeexeCsJn34WRF52ZazyvUMURATmjpajXmq+HILBlByCaZSfvAQUv0 6guabEV6NSPQgKEtDfH9h+aE0SYvT2lmIUXDWRJBVCLoqcrRwmnmCJHYO5EzPu2a/4aR wa5Gqrm0OWt6rUZF7Ia9/OY7BNamaHQqiXrygNxiViBC9TRRYoeNRxdBkLbBQP/joeHR cwnD9S/9m4JpjIPc+WC1c/GYxQx/z4IEhtgr4o7HrfcJj309z5Rb7ildQ3oo+KDoB5vA 3www== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=uABNZlQvDTp99jAU0v/nbxCtH4T5u38kO+tuOl5zvH8=; b=RgEZsP+BYaQh1OXf13EZ7+gcV7xqC3Sps8jP8SmS+F4eQR/vEE2pw19Gt0iMpcLMdV HYiDLckfJbkIHyptoRPAj9sPVPnyINaoXM21GG2zAyAXZ3LELZRI242ruCX/ILuNeauD T/5yf1EzUMVgqk138pjp0Kmc+72doSNamWQVIr/L7nkej4YTwB2gjmsOLuzA3UxHyhjF Xboc038PsLBrfmysYPfXPAKYNkiG8FHZseR1/GmUR7vjlfui/c1KKtguPHO6dHSM8Uq/ CB/pU0AQjxyRwQwvGlsET+iTvmV0ru9yxsIHP/hkFdO8mMg0kRe35mpDft6qqkZksKg2 ebiA== X-Gm-Message-State: ALQs6tDsrNiHS0xMDYrlhKlGy0sTTMFX3FvYI6EALOPBCKqnkp9Z1Lvj c2KClg0sPGQYMnbKV8Te1I5oI0SYzaG1ongT/yp1hA== X-Google-Smtp-Source: AB8JxZqANCpXB7sMqxVnhd+G8Lvnkji1U6D7EyzJV8ml3N7IIO5sYa7++hXdj4nbsnJRjvZ91O/i+rZimOOL3VeR38E= X-Received: by 2002:a24:42c6:: with SMTP id i189-v6mr9343932itb.73.1525026080498; Sun, 29 Apr 2018 11:21:20 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a65a:0:0:0:0:0 with HTTP; Sun, 29 Apr 2018 11:21:19 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> From: Warner Losh Date: Sun, 29 Apr 2018 12:21:19 -0600 X-Google-Sender-Auth: pkzFlqKdzugInV083a6N0Rw8uwQ Message-ID: Subject: Re: Getting ZFS pools back. To: Jan Knepper Cc: Willem Jan Withagen , Alan Somers , FreeBSD Filesystems , FreeBSD Hackers , Richard Yao Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 18:21:22 -0000 On Sun, Apr 29, 2018 at 11:57 AM, Jan Knepper wrote: > On 04/29/2018 13:27, Willem Jan Withagen wrote: > >> Trouble started when I installed (freebsd-update) 11.1 over a running >> 10.4. Which is sort of scarry? >> > This does sounds 'scary' as I am planning to do this in the (near) > future... > > Has anyone else experienced issues like this? > > Generally I do build the new system software on a running system, but then > go to single user mode to perform the actual install. > > I have done many upgrades like that over 18 or so years and never seen or > heard of an issue alike this. 11.x binaries aren't guaranteed to work with a 10.x kernel. So that's a bit of a problem. freebsd-update shouldn't have let you do that either. However, most 11.x binaries work well enough to at least bootstrap / fix problems if booted on a 10.x kernel due to targeted forward compatibility. You shouldn't count on it for long, but it generally won't totally brick your box. In the past, and I believe this is still true, they work well enough to compile and install a new kernel after pulling sources. The 10.x -> 11.x syscall changes are such that you should be fine. At least if you are on UFS. However, the ZFS ioctls and such are in the bag of 'don't specifically guarantee and also they change a lot' so that may be why you can't mount ZFS by UUID. I've not checked to see if there's specifically an issue here or not. The ZFS ABI is somewhat more fragile than other parts of the system, so you may have issues here. If all else fails, you may be able to PXE boot an 11 kernel, or boot off a USB memstick image to install a kernel. Generally, while we don't guarantee forward compatibility (running newer binaries on older kernels), we've generally built enough forward compat so that things work well enough to complete the upgrade. That's why you haven't hit an issue in 18 years of upgrading. However, the velocity of syscall additions has increased, and we've gone from fairly stable (stale?) ABIs for UFS to a more dynamic one for ZFS where backwards compat is a bit of a crap shoot and forward compat isn't really there at all. That's likely why you've hit a speed bump here. Warner From owner-freebsd-fs@freebsd.org Sun Apr 29 18:31:35 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74CD5FB46DB for ; Sun, 29 Apr 2018 18:31:35 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [162.217.114.50]) by mx1.freebsd.org (Postfix) with SMTP id 15BBB705BD for ; Sun, 29 Apr 2018 18:31:35 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 28614 invoked by uid 89); 29 Apr 2018 18:31:31 -0000 Received: from c-24-0-179-87.hsd1.nj.comcast.net (HELO iMac.local) (jan@digitaldaemon.com@24.0.179.87) by digitaldaemon.com with SMTP; 29 Apr 2018 18:31:31 -0000 Subject: Re: Getting ZFS pools back. To: Warner Losh Cc: Willem Jan Withagen , Alan Somers , FreeBSD Filesystems , FreeBSD Hackers , Richard Yao References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> From: Jan Knepper Message-ID: <5692d3b6-038e-4c4b-c5b6-b0f719b4ac38@digitaldaemon.com> Date: Sun, 29 Apr 2018 14:31:30 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 18:31:35 -0000 On 04/29/2018 14:21, Warner Losh wrote: > On Sun, Apr 29, 2018 at 11:57 AM, Jan Knepper > wrote: > > On 04/29/2018 13:27, Willem Jan Withagen wrote: > > Trouble started when I installed (freebsd-update) 11.1 over a > running 10.4. Which is sort of scarry? > > This does sounds 'scary' as I am planning to do this in the (near) > future... > > Has anyone else experienced issues like this? > > Generally I do build the new system software on a running system, > but then go to single user mode to perform the actual install. > > I have done many upgrades like that over 18 or so years and never > seen or heard of an issue alike this. > > > 11.x binaries aren't guaranteed to work with a 10.x kernel. So that's > a bit of a problem. freebsd-update shouldn't have let you do that either. The process I have used so far is to svnup, build, reboot... > However, most 11.x binaries work well enough to at least bootstrap / > fix problems if booted on a 10.x kernel due to targeted forward > compatibility. You shouldn't count on it for long, but it generally > won't totally brick your box. In the past, and I believe this is still > true, they work well enough to compile and install a new kernel after > pulling sources. The 10.x -> 11.x syscall changes are such that you > should be fine. At least if you are on UFS. > > However, the ZFS ioctls and such are in the bag of 'don't specifically > guarantee and also they change a lot' so that may be why you can't > mount ZFS by UUID. I've not checked to see if there's specifically an > issue here or not. The ZFS ABI is somewhat more fragile than other > parts of the system, so you may have issues here. > > If all else fails, you may be able to PXE boot an 11 kernel, or boot > off a USB memstick image to install a kernel. > > Generally, while we don't guarantee forward compatibility (running > newer binaries on older kernels), we've generally built enough forward > compat so that things work well enough to complete the upgrade. That's > why you haven't hit an issue in 18 years of upgrading. However, the > velocity of syscall additions has increased, and we've gone from > fairly stable (stale?) ABIs for UFS to a more dynamic one for ZFS > where backwards compat is a bit of a crap shoot and forward compat > isn't really there at all. That's likely why you've hit a speed bump here. > I have not closely looked at the procedures outlined in /usr/src/UPDATING for 11.x. But do I read correctly that performing a buildworld, buildkernel, then installworld and reboot to update from 10.4 to 11.x does not work? Thanks! ManiaC++ Jan Knepper From owner-freebsd-fs@freebsd.org Sun Apr 29 18:32:50 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04422FB477E; Sun, 29 Apr 2018 18:32:50 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (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 9086770706; Sun, 29 Apr 2018 18:32:49 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 1B18D3DFB2; Sun, 29 Apr 2018 20:32:47 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NeiTaFAUhDC3; Sun, 29 Apr 2018 20:32:46 +0200 (CEST) Received: from [192.168.11.152] (unknown [192.168.11.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 58EF73DFAE; Sun, 29 Apr 2018 20:32:46 +0200 (CEST) Subject: Re: Getting ZFS pools back. To: Jan Knepper , Alan Somers Cc: FreeBSD Filesystems , FreeBSD Hackers , Richard Yao References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> From: Willem Jan Withagen Message-ID: <31f9e4cd-4865-651a-0966-4600101beb8f@digiware.nl> Date: Sun, 29 Apr 2018 20:32:47 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 18:32:50 -0000 On 29/04/2018 19:57, Jan Knepper wrote: > On 04/29/2018 13:27, Willem Jan Withagen wrote: >> Trouble started when I installed (freebsd-update) 11.1 over a running >> 10.4. Which is sort of scarry? > This does sounds 'scary' as I am planning to do this in the (near) > future... > > Has anyone else experienced issues like this? > > Generally I do build the new system software on a running system, but > then go to single user mode to perform the actual install. > > I have done many upgrades like that over 18 or so years and never seen > or heard of an issue alike this. Hi Jan, Most of my upgrades went smooth, other than being pestered by files that are only changed in verssion no and/or comments. This is a rather old server that I installed zfs-on-root, when there were only howtos and no automagic installers. So I guess that it might even be from the 9.x days. It went through several manual upgrades and at least once a online disk replacement with growing disks (500G to 4T). Al that went well, but could very well be that some odd bits and pieces were (missing) left overs. So Don't excluded that there is pilot error involved. I tried Google to find more about fixing the system when this error got reported, but only a rather hefty session with Andriy Gapon, I think. And that was for 9.x or so. Nothing else... So given my need to go on, I just reinstalled. --WjW From owner-freebsd-fs@freebsd.org Sun Apr 29 18:34:07 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD874FB4853 for ; Sun, 29 Apr 2018 18:34:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::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 491627082B for ; Sun, 29 Apr 2018 18:34:07 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22a.google.com with SMTP id d26-v6so7982397ioc.2 for ; Sun, 29 Apr 2018 11:34:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=BaNki7abp+a/BZuXxYzg6EGbIz9W1/HBg1D5jZGc7jI=; b=XR72VzL6S3vSDGEg4m0gSavWLjw6yqGBombQ48vv0Y7t7IrEfREIGB1qc2LrGeDKWM 4JkYunpxCtRhHvyinjUJbxryH6P1idVMzcbcmQ/VWZOwcNJmKRkqIN4TsBLJbIvzSMDE nIge6L0J+OhCxPdGwKKnLS7f0rZ4IwqZWpf5PiXbqSM+hvVwQtjkyUrWOsh9Q4e9sYBD ni/K7olkgR9ZhbmT3unxIRap4S0VCDKK6APyg+YRy2NeYgRNo9hpjlm+doDDmyqySwdT IlpEq7C6PPYlXXazlVimWSfngVoEhPfPZ5DKsuoix6pG1AxJtkUPDmFxuOZLPGUf4ZZh Xj6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=BaNki7abp+a/BZuXxYzg6EGbIz9W1/HBg1D5jZGc7jI=; b=Wa/aCUpz0nIP0nrK0eILHMSE+tcvbgwhU48icTk2GpCNs9ecEqX27ZAh0bmoB1wXVe aPVOfTsaYFXVtsw0n3xQTyQ4ngfVraEvPFy7jYg6yfg8c/sWpH4bTBFG47IrYB9IOrh0 XRaSvDWNK1DMlB6Cs45/DoEkmebDRUm/a38F/02WbBMiGyLXE0oufTUZed+hUQNyHO/i G33v0nGInCojJKtDbnYO/mW8B8ZV4FJIeDywaJ+utuO3zWtYMKsm3OkYl2urwvE8PPfV aRhHPJyH2PHan+CVMrxW01rWGfOXByIGYvqxbE7QL/066NuvGdbRKZ6pH/PMMaq/C0NW aD7g== X-Gm-Message-State: ALQs6tD7q815KxG7cWC7KuRlmRBdoFk+USIsandGH5+OabizlcIGGu7+ JW6cU9jlaK/eN1K0vUXs6uGUpF4UI3ZoehrBzvMj7Q== X-Google-Smtp-Source: AB8JxZow7PoPmhek7TqiAXS9wwOgfkLIBPTnKB2XIR75Z5k16nng4+aDNbhUE07HB+O78f8Nq9q7dPnAwhgiJDQed2Y= X-Received: by 2002:a6b:d404:: with SMTP id l4-v6mr10065025iog.37.1525026846533; Sun, 29 Apr 2018 11:34:06 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a65a:0:0:0:0:0 with HTTP; Sun, 29 Apr 2018 11:34:06 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <5692d3b6-038e-4c4b-c5b6-b0f719b4ac38@digitaldaemon.com> References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> <5692d3b6-038e-4c4b-c5b6-b0f719b4ac38@digitaldaemon.com> From: Warner Losh Date: Sun, 29 Apr 2018 12:34:06 -0600 X-Google-Sender-Auth: 2OHb_nsgMQX9zCbsizBr0zA17fE Message-ID: Subject: Re: Getting ZFS pools back. To: Jan Knepper Cc: Willem Jan Withagen , Alan Somers , FreeBSD Filesystems , FreeBSD Hackers , Richard Yao Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 18:34:08 -0000 On Sun, Apr 29, 2018 at 12:31 PM, Jan Knepper wrote: > However, most 11.x binaries work well enough to at least bootstrap / fix > problems if booted on a 10.x kernel due to targeted forward compatibility. > You shouldn't count on it for long, but it generally won't totally brick > your box. In the past, and I believe this is still true, they work well > enough to compile and install a new kernel after pulling sources. The 10.x > -> 11.x syscall changes are such that you should be fine. At least if you > are on UFS. > > However, the ZFS ioctls and such are in the bag of 'don't specifically > guarantee and also they change a lot' so that may be why you can't mount > ZFS by UUID. I've not checked to see if there's specifically an issue here > or not. The ZFS ABI is somewhat more fragile than other parts of the > system, so you may have issues here. > > If all else fails, you may be able to PXE boot an 11 kernel, or boot off a > USB memstick image to install a kernel. > > Generally, while we don't guarantee forward compatibility (running newer > binaries on older kernels), we've generally built enough forward compat so > that things work well enough to complete the upgrade. That's why you > haven't hit an issue in 18 years of upgrading. However, the velocity of > syscall additions has increased, and we've gone from fairly stable (stale?) > ABIs for UFS to a more dynamic one for ZFS where backwards compat is a bit > of a crap shoot and forward compat isn't really there at all. That's likely > why you've hit a speed bump here. > > I have not closely looked at the procedures outlined in /usr/src/UPDATING > for 11.x. But do I read correctly that performing a buildworld, > buildkernel, then installworld and reboot to update from 10.4 to 11.x does > not work? > No. That will work. If you always install a new kernel and reboot (especially across major releases) and then install the new binaries, you're safe. You won't get into a situation where new binaries are running on an old kernel. As far as I know that's not broken, even with the strange ABI issues I talk about. That's only when you're running 11.x binaries on a 10.x kernel, not the other way around. Warner From owner-freebsd-fs@freebsd.org Sun Apr 29 18:37:26 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 45084FB4A58 for ; Sun, 29 Apr 2018 18:37:26 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: from digitaldaemon.com (digitaldaemon.com [162.217.114.50]) by mx1.freebsd.org (Postfix) with SMTP id A915171975 for ; Sun, 29 Apr 2018 18:37:25 +0000 (UTC) (envelope-from jan@digitaldaemon.com) Received: (qmail 29312 invoked by uid 89); 29 Apr 2018 18:37:21 -0000 Received: from c-24-0-179-87.hsd1.nj.comcast.net (HELO iMac.local) (jan@digitaldaemon.com@24.0.179.87) by digitaldaemon.com with SMTP; 29 Apr 2018 18:37:21 -0000 Subject: Re: Getting ZFS pools back. To: Willem Jan Withagen , Alan Somers Cc: FreeBSD Filesystems , FreeBSD Hackers , Richard Yao References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> <31f9e4cd-4865-651a-0966-4600101beb8f@digiware.nl> From: Jan Knepper Message-ID: Date: Sun, 29 Apr 2018 14:37:21 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <31f9e4cd-4865-651a-0966-4600101beb8f@digiware.nl> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 18:37:26 -0000 On 04/29/2018 14:32, Willem Jan Withagen wrote: > On 29/04/2018 19:57, Jan Knepper wrote: >> On 04/29/2018 13:27, Willem Jan Withagen wrote: >>> Trouble started when I installed (freebsd-update) 11.1 over a >>> running 10.4. Which is sort of scarry? >> This does sounds 'scary' as I am planning to do this in the (near) >> future... >> >> Has anyone else experienced issues like this? >> >> Generally I do build the new system software on a running system, but >> then go to single user mode to perform the actual install. >> >> I have done many upgrades like that over 18 or so years and never >> seen or heard of an issue alike this. > > Most of my upgrades went smooth, other than being pestered by files > that are only changed in verssion no and/or comments. Yeah... Know about those... mergemaster has a option to elevate some of that pain though... > This is a rather old server that I installed zfs-on-root, when there > were only howtos and no automagic installers. So I guess that it might > even be from the 9.x days. It went through several manual upgrades and > at least once a online disk replacement with growing disks (500G to 4T). > Al that went well, but could very well be that some odd bits and pieces > were (missing) left overs. OK... That might explain a thing or two... I do recall installing 9.x I think on a new server (hardware) and having to do the ZFS setup manually... Everything currently runs 10.x > So Don't excluded that there is pilot error involved. > I tried Google to find more about fixing the system when this error > got reported, but only a rather hefty session with Andriy Gapon, I think. > And that was for 9.x or so. > Nothing else... > > So given my need to go on, I just reinstalled. OK! Thank you for letting me know! ManiaC++ Jan Knepper From owner-freebsd-fs@freebsd.org Sun Apr 29 19:36:33 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 56394FB66C5; Sun, 29 Apr 2018 19:36:33 +0000 (UTC) (envelope-from leres@freebsd.org) Received: from xse.com (xse.com [IPv6:2607:f2f8:abb8::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "xse.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C63427ED82; Sun, 29 Apr 2018 19:36:32 +0000 (UTC) (envelope-from leres@freebsd.org) Received-SPF: pass (dot.xse.com: authenticated connection) receiver=dot.xse.com; client-ip=2001:558:6045:10:9084:9e0:4b6d:eb99; helo=ice.alameda.xse.com; envelope-from=leres@freebsd.org; x-software=spfmilter 2.001 http://www.acme.com/software/spfmilter/ with libspf2-1.2.10; Received: from ice.alameda.xse.com (ice.xse.com [IPv6:2001:558:6045:10:9084:9e0:4b6d:eb99]) (authenticated bits=0) by dot.xse.com (8.15.2/8.15.2) with ESMTPSA id w3TJa6AS052823 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sun, 29 Apr 2018 12:36:08 -0700 (PDT) (envelope-from leres@freebsd.org) X-Authentication-Warning: dot.xse.com: Host ice.xse.com [IPv6:2001:558:6045:10:9084:9e0:4b6d:eb99] claimed to be ice.alameda.xse.com Subject: Re: Getting ZFS pools back. To: Warner Losh , Jan Knepper References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> <5692d3b6-038e-4c4b-c5b6-b0f719b4ac38@digitaldaemon.com> Cc: FreeBSD Filesystems , FreeBSD Hackers , Richard Yao , Willem Jan Withagen , Alan Somers From: Craig Leres Message-ID: Date: Sun, 29 Apr 2018 12:36:05 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.100.0 at dot.xse.com X-Virus-Status: Clean X-GBUdb-Analysis: Unknown X-MessageSniffer-Rules: 0-0-0-4746-c X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 19:36:33 -0000 On 04/29/18 11:34, Warner Losh wrote: > If you always install a new kernel and reboot > (especially across major releases) and then install the new binaries, > you're safe. I upgraded 40+ systems from 10.3-RELEASE to 11.1-RELEASE over the last few weeks including 8 or so with zfs partitions (but all boot off of ufs2). The work flow I converged on was: - (I use rcs for configs so) co -l all customized config files - Check /etc/freebsd-update.conf for the desired config - Download the upgrade updates (freebsd-update upgrade -r 11.1-RELEASE) - Check /etc/rc.conf and disable kern_securelevel if enabled - Check/update /etc/resolv.conf if using bind9* - Switch to /usr/bin/sshd if using openssh-portable - Copy and install custom 11.1 kernel from my build server - Stop most services - Save a list of installed packages: pkg info|sed -e 's/-[0-9a-zA-Z._,]* *.*//' > /var/tmp/a - Remove all packages (pkg-static delete -fya) - Reboot - Run "freebsd-update install" three times - Reinstall packages: pkg update -f pkg clean -ay pkg install -y `cat /var/tmp/a` - Check/reset/checkin configs and reboot I had zero^H^H^H^Hno zfs issues. On 04/29/18 11:32, Willem Jan Withagen wrote: > Most of my upgrades went smooth, other than being pestered by > files that are only changed in verssion no and/or comments. I also find this annoying but started manually updating things that were problematic before starting which minimized freebsd-update merging. Craig From owner-freebsd-fs@freebsd.org Sun Apr 29 21:01:17 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB57DFB8707 for ; Sun, 29 Apr 2018 21:01:17 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3CF3F70799 for ; Sun, 29 Apr 2018 21:01:17 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id F0525FB8704; Sun, 29 Apr 2018 21:01:16 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CE1D4FB8702 for ; Sun, 29 Apr 2018 21:01:16 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 508D870772 for ; Sun, 29 Apr 2018 21:01:16 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7D8AE1F242 for ; Sun, 29 Apr 2018 21:01:15 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3TL1FKE051586 for ; Sun, 29 Apr 2018 21:01:15 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3TL1FLj051585 for fs@FreeBSD.org; Sun, 29 Apr 2018 21:01:15 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201804292101.w3TL1FLj051585@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: fs@FreeBSD.org Subject: Problem reports for fs@FreeBSD.org that need special attention Date: Sun, 29 Apr 2018 21:01:15 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 21:01:18 -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 New | 217062 | for file systems mounted with -o noexec, exec=off New | 221909 | [ZFS] Add a sysctl to toggle send_corrupt_data 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 | 211491 | System hangs after "Uptime" on reboot with ZFS 8 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Sun Apr 29 21:20:05 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 392DDFB953A; Sun, 29 Apr 2018 21:20:05 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (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 C127276035; Sun, 29 Apr 2018 21:20:04 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 57BA43DD27; Sun, 29 Apr 2018 23:20:02 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pns3VvmlAITH; Sun, 29 Apr 2018 23:20:01 +0200 (CEST) Received: from [192.168.11.152] (unknown [192.168.11.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 462423DD26; Sun, 29 Apr 2018 23:20:01 +0200 (CEST) Subject: Re: Getting ZFS pools back. To: Warner Losh , Jan Knepper Cc: Alan Somers , FreeBSD Filesystems , FreeBSD Hackers , Richard Yao References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> From: Willem Jan Withagen Message-ID: <7588abf8-16e4-8820-a0e5-e019a02a7bd6@digiware.nl> Date: Sun, 29 Apr 2018 23:20:02 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 21:20:05 -0000 On 29/04/2018 20:21, Warner Losh wrote: > > > On Sun, Apr 29, 2018 at 11:57 AM, Jan Knepper > wrote: > > On 04/29/2018 13:27, Willem Jan Withagen wrote: > > Trouble started when I installed (freebsd-update) 11.1 over a > running 10.4. Which is sort of scarry? > > This does sounds 'scary' as I am planning to do this in the (near) > future... > > Has anyone else experienced issues like this? > > Generally I do build the new system software on a running system, > but then go to single user mode to perform the actual install. > > I have done many upgrades like that over 18 or so years and never > seen or heard of an issue alike this. > > > 11.x binaries aren't guaranteed to work with a 10.x kernel. So that's a > bit of a problem. freebsd-update shouldn't have let you do that either. > > However, most 11.x binaries work well enough to at least bootstrap / fix > problems if booted on a 10.x kernel due to targeted forward > compatibility. You shouldn't count on it for long, but it generally > won't totally brick your box. In the past, and I believe this is still > true, they work well enough to compile and install a new kernel after > pulling sources. The 10.x -> 11.x syscall changes are such that you > should be fine. At least if you are on UFS. I have been doing those kind of this for years and years. Even upgrading over NFS and stuff. Sometimes it is a bit too close to the sun and things burn. But never crash this bad. > However, the ZFS ioctls and such are in the bag of 'don't specifically > guarantee and also they change a lot' so that may be why you can't mount > ZFS by UUID. I've not checked to see if there's specifically an issue > here or not. The ZFS ABI is somewhat more fragile than other parts of > the system, so you may have issues here. > > If all else fails, you may be able to PXE boot an 11 kernel, or boot off > a USB memstick image to install a kernel. Tried just about replace everything in both the boot-partition (First growing it to take > 64K gptzfsboot) and in /boot from the memstick. But the error never went away. Never had ZFS die on me this bad, that I could not get it back. > Generally, while we don't guarantee forward compatibility (running newer > binaries on older kernels), we've generally built enough forward compat > so that things work well enough to complete the upgrade. That's why you > haven't hit an issue in 18 years of upgrading. However, the velocity of > syscall additions has increased, and we've gone from fairly stable > (stale?) ABIs for UFS to a more dynamic one for ZFS where backwards > compat is a bit of a crap shoot and forward compat isn't really there at > all. That's likely why you've hit a speed bump here. Come to think of it, I did not do this step with freebsd-update, since I was not at an official release yet. I was going to 11.1-RELEASE, to be able to start using freebsd-update. So I don't think I did just do that.... But I tried so much yesterday. Normally I would installkernel, reboot, installworld, mergemaster, reboot for systems that are not up for freebsd-update. --WjW From owner-freebsd-fs@freebsd.org Mon Apr 30 05:18:17 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84C00FC3AFA for ; Mon, 30 Apr 2018 05:18:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 199D67E71E for ; Mon, 30 Apr 2018 05:18:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id CF036FC3AF9; Mon, 30 Apr 2018 05:18:16 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BDA7FFC3AF8 for ; Mon, 30 Apr 2018 05:18:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5BEBF7E701 for ; Mon, 30 Apr 2018 05:18:16 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 9683D23765 for ; Mon, 30 Apr 2018 05:18:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3U5IFIW059053 for ; Mon, 30 Apr 2018 05:18:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3U5IFh0059052 for fs@FreeBSD.org; Mon, 30 Apr 2018 05:18:15 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 210316] panic after trying to r/w mount msdosfs on write protected media Date: Mon, 30 Apr 2018 05:18: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: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: damjan.jov@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2018 05:18:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210316 Damjan Jovanovic changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |damjan.jov@gmail.com --- Comment #5 from Damjan Jovanovic --- Still a problem on CURRENT. Very easy to reproduce: dd if=3D/dev/zero of=3D/path/to/image bs=3D1M count=3D100 newfs_msdos /path/to/image ggatel create -o ro /path/to/image mount /dev/ggate0 /mnt A few seconds later: crash. I wonder what the best way to fix this is. Should the referenced geom explicitly be cleared from the buffer after the failed write? Should the msdosfs driver call fsync() before g_vfs_destroy()-ing the geom on mount failure, so the dirty buffer is deleted before the geom device it reference= s is deleted? Should geom devices be reference counted by their buffers and be forced to live until all buffers that reference them are deleted? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Apr 30 06:49:45 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B4F56FC573D for ; Mon, 30 Apr 2018 06:49:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4BD166EF25 for ; Mon, 30 Apr 2018 06:49:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 05B0CFC573C; Mon, 30 Apr 2018 06:49:45 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E7720FC573A for ; Mon, 30 Apr 2018 06:49:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 84A9A6EF23 for ; Mon, 30 Apr 2018 06:49:44 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 832BE243C6 for ; Mon, 30 Apr 2018 06:49:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w3U6nhQi067423 for ; Mon, 30 Apr 2018 06:49:43 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w3U6nhGi067422 for fs@FreeBSD.org; Mon, 30 Apr 2018 06:49:43 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 210316] panic after trying to r/w mount msdosfs on write protected media Date: Mon, 30 Apr 2018 06:49:41 +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: damjan.jov@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2018 06:49:45 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210316 --- Comment #6 from Damjan Jovanovic --- Repeating that test with UFS (newfs -U -j) also freezes the system, so sadly msdosfs is not the only filesystem affected. Using the ext2fs driver on a read-only EXT3 filesystem however works, print= ing some errors in dmesg: g_vfs_done():ggate0[WRITE(offset=3D1024, length=3D1024)]error =3D 1 g_vfs_done():ggate0[WRITE(offset=3D1024, length=3D1024)]error =3D 1 g_vfs_done():ggate0[WRITE(offset=3D2048, length=3D1024)]error =3D 1 g_vfs_done():ggate0[WRITE(offset=3D268288, length=3D1024)]error =3D 1 g_vfs_done():ggate0[WRITE(offset=3D268288, length=3D1024)]error =3D 1 but it mounts successfully, denies writes with EPERM, and doesn't crash. Unmounting however fails, with this ominous error: fsync: giving up on dirty (error =3D 1) 0xfffff801df6a45a0: tag devfs, type= VCHR usecount 1, writecount 0, refcount 7 rdev 0xfffff800d1092800 flags (VI_ACTIVE) v_object 0xfffff80146eb3900 ref 0 pages 2 cleanbuf 1 dirtybuf 4 lock type devfs: EXCL by thread 0xfffff800d1017000 (pid 1494, umount, t= id 100515) dev ggate0 but still no crash. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Apr 30 10:37:51 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8D286FCACBE; Mon, 30 Apr 2018 10:37:51 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [176.74.240.9]) (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 2611D78C10; Mon, 30 Apr 2018 10:37:50 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id AF4C23D4F4; Mon, 30 Apr 2018 12:37:48 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ovyt5Zq6dPbv; Mon, 30 Apr 2018 12:37:47 +0200 (CEST) Received: from [192.168.10.67] (opteron [192.168.10.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 5604E3D4F0; Mon, 30 Apr 2018 12:37:47 +0200 (CEST) Subject: Re: Getting ZFS pools back. From: Willem Jan Withagen To: Warner Losh , Jan Knepper Cc: FreeBSD Filesystems , FreeBSD Hackers , Richard Yao , Alan Somers References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> <7588abf8-16e4-8820-a0e5-e019a02a7bd6@digiware.nl> Message-ID: Date: Mon, 30 Apr 2018 12:37:45 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <7588abf8-16e4-8820-a0e5-e019a02a7bd6@digiware.nl> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2018 10:37:51 -0000 On 29-4-2018 23:20, Willem Jan Withagen wrote: > On 29/04/2018 20:21, Warner Losh wrote: >> >> >> On Sun, Apr 29, 2018 at 11:57 AM, Jan Knepper > > wrote: >> >>     On 04/29/2018 13:27, Willem Jan Withagen wrote: >> >>         Trouble started when I installed (freebsd-update) 11.1 over a >>         running 10.4. Which is sort of scarry? >> >>     This does sounds 'scary' as I am planning to do this in the (near) >>     future... >> >>     Has anyone else experienced issues like this? >> >>     Generally I do build the new system software on a running system, >>     but then go to single user mode to perform the actual install. >> >>     I have done many upgrades like that over 18 or so years and never >>     seen or heard of an issue alike this. >> >> >> 11.x binaries aren't guaranteed to work with a 10.x kernel. So that's >> a bit of a problem. freebsd-update shouldn't have let you do that either. >> >> However, most 11.x binaries work well enough to at least bootstrap / >> fix problems if booted on a 10.x kernel due to targeted forward >> compatibility. You shouldn't count on it for long, but it generally >> won't totally brick your box. In the past, and I believe this is still >> true, they work well enough to compile and install a new kernel after >> pulling sources. The 10.x -> 11.x syscall changes are such that you >> should be fine. At least if you are on UFS. > > I have been doing those kind of this for years and years. Even upgrading > over NFS and stuff. Sometimes it is a bit too close to the sun and > things burn. But never crash this bad. > >> However, the ZFS ioctls and such are in the bag of 'don't specifically >> guarantee and also they change a lot' so that may be why you can't >> mount ZFS by UUID. I've not checked to see if there's specifically an >> issue here or not. The ZFS ABI is somewhat more fragile than other >> parts of the system, so you may have issues here. >> >> If all else fails, you may be able to PXE boot an 11 kernel, or boot >> off a USB memstick image to install a kernel. > > Tried just about replace everything in both the boot-partition (First > growing it to take > 64K gptzfsboot) and in /boot from the memstick. > But the error never went away. > > Never had ZFS die on me this bad, that I could not get it back. > >> Generally, while we don't guarantee forward compatibility (running >> newer binaries on older kernels), we've generally built enough forward >> compat so that things work well enough to complete the upgrade. That's >> why you haven't hit an issue in 18 years of upgrading. However, the >> velocity of syscall additions has increased, and we've gone from >> fairly stable (stale?) ABIs for UFS to a more dynamic one for ZFS >> where backwards compat is a bit of a crap shoot and forward compat >> isn't really there at all. That's likely why you've hit a speed bump >> here. > > Come to think of it, I did not do this step with freebsd-update, since I > was not at an official release yet. I was going to 11.1-RELEASE, to be > able to start using freebsd-update. > > So I don't think I did just do that.... But I tried so much yesterday. > Normally I would installkernel, reboot, installworld, mergemaster, > reboot for systems that are not up for freebsd-update. Right, The story gets even sadder ..... Took the "spare" disk home, and just connected it to an older SuperMicro server I had lying about for Ceph tests. And lo and behold, it just boots. So that system got upgraded from: 10.2 -> 10.4 -> 11.1 No complaints about anything. So now I'm inclined to point at older hardware with an old bios, which confused ZFS, or probably more precisely gptzfsboot. From dmidecode: System Information Manufacturer: Supermicro Product Name: H8SGL Version: 1234567890 BIOS Information Vendor: American Megatrends Inc. Version: 3.5 Release Date: 11/25/2013 Address: 0xF0000 We only have 1 of those, so further investigation, and or tinkering, in combo with the hardware will be impossible. --WjW From owner-freebsd-fs@freebsd.org Tue May 1 06:12:49 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C36CFFC57DE for ; Tue, 1 May 2018 06:12:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3D710835B4 for ; Tue, 1 May 2018 06:12:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id EBE46FC57DB; Tue, 1 May 2018 06:12:48 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9163FC57D9 for ; Tue, 1 May 2018 06:12:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6AD33835A9 for ; Tue, 1 May 2018 06:12:48 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 737B210E03 for ; Tue, 1 May 2018 06:12:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w416ClxM011932 for ; Tue, 1 May 2018 06:12:47 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w416Clm8011921 for fs@FreeBSD.org; Tue, 1 May 2018 06:12:47 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 210316] panic after trying to r/w mount msdosfs on write protected media Date: Tue, 01 May 2018 06:12:45 +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: damjan.jov@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2018 06:12:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210316 --- Comment #7 from Damjan Jovanovic --- If I add this code snippet (copied from somewhere in the ext2fs driver) so = that vinvalbuf() is called before g_vfs_close(), the r/w mount of a r/o geom fai= ls (EPERM), and the panic doesn't happen: diff --git a/sys/fs/msdosfs/msdosfs_vfsops.c b/sys/fs/msdosfs/msdosfs_vfsop= s.c index 76a238c5ff77..7477d5b03a1f 100644 --- a/sys/fs/msdosfs/msdosfs_vfsops.c +++ b/sys/fs/msdosfs/msdosfs_vfsops.c @@ -717,6 +717,12 @@ mountmsdosfs(struct vnode *devvp, struct mount *mp) error_exit: if (bp) brelse(bp); + + vn_lock(devvp, LK_EXCLUSIVE | LK_RETRY); + if (vinvalbuf(devvp, 0, 0, 0) !=3D 0) + panic("mountmsdosfs: dirty"); + VOP_UNLOCK(devvp, 0); + if (cp !=3D NULL) { g_topology_lock(); g_vfs_close(cp); Apart from not really understanding it, I don't like it, because if every filesystem should be calling vinvalbuf() before g_vfs_close(), then shouldn= 't g_vfs_close() rather be calling vinvalbuf() itself? Also msdosfs_unmount() doesn't call vinvalbuf() before its own g_vfs_close(), but it does call msdosfs_sync() and vflush(). Would those also work, or be even better? Fixing UFS will be a different story, as msdosfs writes to the filesystem during mount [in markvoldirty()], so the panic is almost immediate. I could only crash UFS by trying to write to a file after mounting. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue May 1 21:25:44 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A3225FB86B9; Tue, 1 May 2018 21:25:44 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [176.74.240.9]) (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 3708F7647D; Tue, 1 May 2018 21:25:43 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 988833D726; Tue, 1 May 2018 23:25:42 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UCSJBzm6VGGg; Tue, 1 May 2018 23:25:41 +0200 (CEST) Received: from [192.168.11.152] (unknown [192.168.11.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 3B85E3D720; Tue, 1 May 2018 23:25:40 +0200 (CEST) Subject: Re: Getting ZFS pools back. From: Willem Jan Withagen To: Warner Losh , Jan Knepper Cc: FreeBSD Filesystems , FreeBSD Hackers , Richard Yao , Alan Somers References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> <7588abf8-16e4-8820-a0e5-e019a02a7bd6@digiware.nl> Message-ID: Date: Tue, 1 May 2018 23:25:41 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: nl Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2018 21:25:44 -0000 On 30/04/2018 12:37, Willem Jan Withagen wrote: > On 29-4-2018 23:20, Willem Jan Withagen wrote: >> On 29/04/2018 20:21, Warner Losh wrote: >>> >>> >>> On Sun, Apr 29, 2018 at 11:57 AM, Jan Knepper >> > wrote: >>> >>>     On 04/29/2018 13:27, Willem Jan Withagen wrote: >>> >>>         Trouble started when I installed (freebsd-update) 11.1 over a >>>         running 10.4. Which is sort of scarry? >>> >>>     This does sounds 'scary' as I am planning to do this in the (near) >>>     future... >>> >>>     Has anyone else experienced issues like this? >>> >>>     Generally I do build the new system software on a running system, >>>     but then go to single user mode to perform the actual install. >>> >>>     I have done many upgrades like that over 18 or so years and never >>>     seen or heard of an issue alike this. >>> >>> >>> 11.x binaries aren't guaranteed to work with a 10.x kernel. So that's >>> a bit of a problem. freebsd-update shouldn't have let you do that >>> either. >>> >>> However, most 11.x binaries work well enough to at least bootstrap / >>> fix problems if booted on a 10.x kernel due to targeted forward >>> compatibility. You shouldn't count on it for long, but it generally >>> won't totally brick your box. In the past, and I believe this is >>> still true, they work well enough to compile and install a new kernel >>> after pulling sources. The 10.x -> 11.x syscall changes are such that >>> you should be fine. At least if you are on UFS. >> >> I have been doing those kind of this for years and years. Even >> upgrading over NFS and stuff. Sometimes it is a bit too close to the >> sun and things burn. But never crash this bad. >> >>> However, the ZFS ioctls and such are in the bag of 'don't >>> specifically guarantee and also they change a lot' so that may be why >>> you can't mount ZFS by UUID. I've not checked to see if there's >>> specifically an issue here or not. The ZFS ABI is somewhat more >>> fragile than other parts of the system, so you may have issues here. >>> >>> If all else fails, you may be able to PXE boot an 11 kernel, or boot >>> off a USB memstick image to install a kernel. >> >> Tried just about replace everything in both the boot-partition (First >> growing it to take > 64K gptzfsboot) and in /boot from the memstick. >> But the error never went away. >> >> Never had ZFS die on me this bad, that I could not get it back. >> >>> Generally, while we don't guarantee forward compatibility (running >>> newer binaries on older kernels), we've generally built enough >>> forward compat so that things work well enough to complete the >>> upgrade. That's why you haven't hit an issue in 18 years of >>> upgrading. However, the velocity of syscall additions has increased, >>> and we've gone from fairly stable (stale?) ABIs for UFS to a more >>> dynamic one for ZFS where backwards compat is a bit of a crap shoot >>> and forward compat isn't really there at all. That's likely why >>> you've hit a speed bump here. >> >> Come to think of it, I did not do this step with freebsd-update, since >> I was not at an official release yet. I was going to 11.1-RELEASE, to >> be able to start using freebsd-update. >> >> So I don't think I did just do that.... But I tried so much yesterday. >> Normally I would installkernel, reboot, installworld, mergemaster, >> reboot for systems that are not up for freebsd-update. > > Right, > > The story gets even sadder ..... > Took the "spare" disk home, and just connected it to an older SuperMicro > server I had lying about for Ceph tests. And lo and behold, it just boots. > > So that system got upgraded from: 10.2 -> 10.4 -> 11.1 > No complaints about anything. > > So now I'm inclined to point at older hardware with an old bios, which > confused ZFS, or probably more precisely gptzfsboot. > > From dmidecode: > System Information >         Manufacturer: Supermicro >         Product Name: H8SGL >         Version: 1234567890 > BIOS Information >         Vendor: American Megatrends Inc. >         Version: 3.5 >         Release Date: 11/25/2013 >         Address: 0xF0000 > > We only have 1 of those, so further investigation, and or tinkering, in > combo with the hardware will be impossible. Today i found the messages below in my daily report of the server: +NMI ISA 3c, EISA ff +NMI ISA 3c, EISA ff +NMI ISA 3c, EISA ff +NMI ... going to debugger +NMI ... going to debugger +NMI ISA 3c, EISA ff +NMI ISA 2c, EISA ff +NMI ... going to debugger +NMI ... going to debugger +NMI ISA 2c, EISA ff +NMI ISA 3c, EISA ff +NMI ... going to debugger +NMI ... going to debugger +NMI ... going to debugger +NMI ISA 3c, EISA ff +NMI ... going to debugger Could these things have anything to do with the problem I had with trying to find the pools. --WjW From owner-freebsd-fs@freebsd.org Wed May 2 09:47:33 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 297D2FC7C1C; Wed, 2 May 2018 09:47:33 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f42.google.com (mail-lf0-f42.google.com [209.85.215.42]) (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 7F6038648A; Wed, 2 May 2018 09:47:32 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f42.google.com with SMTP id g12-v6so19910813lfb.10; Wed, 02 May 2018 02:47:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=0M1IFBvXCXyWKO3WUpYCih+fjR3mAQDZlmIXnTYmP7w=; b=CbNpbnO0HwDcvtgeTxuwCJ6nmRCculbe73sLBdr0pciiM9WgowAh+lhyc5FHecs/u3 lNGxcGdbmwhsONoGO0GfIPgMwvWcBygtjEGLJz3YTqMBKPT6ussFN0kZIcfwy4rOIyKX PqZM4VuVE/wxh/SL287+JM+46FE3veEWlOHWoDjWmVJeRKSm6TPUsKSLTf309oyVfUB6 owU3QxMU8F9SVSvt2S8+SKwLDsMFBXIfaLFu/uzFVtleEj2NjknMfhYJFYRUST+YhMp2 PhebaPHwp4/VFIgxsWVWgj09cZfrCD1ugDdiM068PQqXfOp7MVScPxms+wCNzcssRzxa /5Yg== X-Gm-Message-State: ALQs6tAT8A2j2tEkeCaMf2ZSuqJPYZNsou7yAtolh0AjuI1JDSLGMv3W QlL03QkIfMqHwcxTJulfKEvT/PmG X-Google-Smtp-Source: AB8JxZqYQ7cT6orIJhU8Iza78/Y5cjtWbxU6z3itxu/xmIollxCVhkrmKI5Qxsq9tFigM+m/zyPVXA== X-Received: by 2002:a2e:320b:: with SMTP id y11-v6mr12485388ljy.119.1525254444993; Wed, 02 May 2018 02:47:24 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id g20-v6sm2336902lfk.39.2018.05.02.02.47.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 02 May 2018 02:47:24 -0700 (PDT) Subject: Re: Getting ZFS pools back. To: Willem Jan Withagen Cc: FreeBSD Filesystems , FreeBSD Hackers References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> <7588abf8-16e4-8820-a0e5-e019a02a7bd6@digiware.nl> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <616ffef3-195b-47fa-fcc6-1ba9f5545bef@FreeBSD.org> Date: Wed, 2 May 2018 12:47:22 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 May 2018 09:47:33 -0000 On 30/04/2018 13:37, Willem Jan Withagen wrote: > So now I'm inclined to point at older hardware with an old bios, which confused > ZFS, or probably more precisely gptzfsboot. I think that this alone wouldn't explain the problems you had with zpool import. Maybe you had multiple issues at the same time. - something with BIOS caused trouble with booting - something else, e.g. kernel-userland mismatch, caused zpool commands to misbehave -- Andriy Gapon From owner-freebsd-fs@freebsd.org Wed May 2 10:01:37 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8FE49FC830E for ; Wed, 2 May 2018 10:01:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1A742698DB for ; Wed, 2 May 2018 10:01:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id CFC5BFC8307; Wed, 2 May 2018 10:01:36 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BD3C9FC8304 for ; Wed, 2 May 2018 10:01:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 516F1698BD for ; Wed, 2 May 2018 10:01:36 +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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 5B53C1F4FC for ; Wed, 2 May 2018 10:01:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w42A1Zje030384 for ; Wed, 2 May 2018 10:01:35 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w42A1Z9m030383 for fs@FreeBSD.org; Wed, 2 May 2018 10:01:35 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 210316] panic after trying to r/w mount msdosfs on write protected media Date: Wed, 02 May 2018 10:01:31 +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: avg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 May 2018 10:01:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210316 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |g.gonter@ieee.org --- Comment #8 from Andriy Gapon --- *** Bug 67326 has been marked as a duplicate of this bug. *** --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed May 2 11:48:34 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 037DEFA6BBE for ; Wed, 2 May 2018 11:48:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8C89C8303B for ; Wed, 2 May 2018 11:48:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4F9D6FA6BBD; Wed, 2 May 2018 11:48:33 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B891FA6BBC for ; Wed, 2 May 2018 11:48:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C758F83037 for ; Wed, 2 May 2018 11:48: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id EE71220401 for ; Wed, 2 May 2018 11:48:31 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w42BmVW4089015 for ; Wed, 2 May 2018 11:48:31 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w42BmVFA089014 for fs@FreeBSD.org; Wed, 2 May 2018 11:48:31 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 210316] panic after trying to r/w mount msdosfs on write protected media Date: Wed, 02 May 2018 11:48:31 +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: kib@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: 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.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 May 2018 11:48:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210316 --- Comment #9 from Konstantin Belousov --- (In reply to Andriy Gapon from comment #1) Assuming that this analysis covers all cases, what could be your suggestion there, Andrey ? May be, in g_vfs_close() we should set up bo_ops to some vector which conta= ins NOP strategy and return success ? Perhaps this should be an opt-in from the caller of g_vfs_close(). In that case, we might also stop passing V_SAVE to invalbuf(). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed May 2 12:00:47 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D3304FA749E; Wed, 2 May 2018 12:00:47 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [IPv6:2001:4cb8:90:ffff::3]) (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 6A5FF85DCB; Wed, 2 May 2018 12:00:47 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 465633DB6B; Wed, 2 May 2018 14:00:45 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0v2x8m-JhTxk; Wed, 2 May 2018 14:00:44 +0200 (CEST) Received: from [192.168.10.67] (opteron [192.168.10.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id AD01D3DB6A; Wed, 2 May 2018 14:00:44 +0200 (CEST) Subject: Re: Getting ZFS pools back. To: Andriy Gapon Cc: FreeBSD Filesystems , FreeBSD Hackers References: <5f836c79-b379-f066-689b-1645e393c5e9@digiware.nl> <1645b168-4133-693c-2dd3-8e0606abb9c3@digiware.nl> <07576f68-f67e-3a22-7a50-ff261c9b3fff@digitaldaemon.com> <7588abf8-16e4-8820-a0e5-e019a02a7bd6@digiware.nl> <616ffef3-195b-47fa-fcc6-1ba9f5545bef@FreeBSD.org> From: Willem Jan Withagen Message-ID: <7c0b4478-ff87-0d70-d9ef-203122c2bc7f@digiware.nl> Date: Wed, 2 May 2018 14:00:43 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <616ffef3-195b-47fa-fcc6-1ba9f5545bef@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: nl Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 May 2018 12:00:48 -0000 On 2-5-2018 11:47, Andriy Gapon wrote: > On 30/04/2018 13:37, Willem Jan Withagen wrote: >> So now I'm inclined to point at older hardware with an old bios, which confused >> ZFS, or probably more precisely gptzfsboot. > > I think that this alone wouldn't explain the problems you had with zpool import. > Maybe you had multiple issues at the same time. > - something with BIOS caused trouble with booting > - something else, e.g. kernel-userland mismatch, caused zpool commands to misbehave More than likely you are right. Frustrating was, how ever, that most trouble I run into, I can fix. Doing FreeBSD for so long, makes that I don't easily give up. But after 4 hours of fiddling with bootsectors, loaders, setting and what not, I gave up. Also because I did not want to jeopardize the data. (It is on backup, but the backup was already 8 hours stale) But hey, system is backup. And haven't heart anybody complaining about missing data, of other failures.... --WjW