From owner-freebsd-fs@freebsd.org Sun Mar 4 13:56: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 D865AF357C6 for ; Sun, 4 Mar 2018 13:56:35 +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 77D747BDC7 for ; Sun, 4 Mar 2018 13:56:35 +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 B062510912 for ; Sun, 4 Mar 2018 13:56:34 +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 w24DuYgq022852 for ; Sun, 4 Mar 2018 13:56:34 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w24DuY8P022851 for freebsd-fs@FreeBSD.org; Sun, 4 Mar 2018 13:56:34 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: freebsd-fs@FreeBSD.org Subject: [Bug 225960] zfs: g_access leak when unmounting UFS on a zvol Date: Sun, 04 Mar 2018 13:56:34 +0000 X-Bugzilla-Reason: CC 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 Some People X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-geom@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, 04 Mar 2018 13:56:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225960 --- Comment #14 from Andriy Gapon --- A more generic patch for the problem: https://reviews.freebsd.org/D14533 --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-fs@freebsd.org Sun Mar 4 18:31: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 6BBACF2560E for ; Sun, 4 Mar 2018 18:31:19 +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 07DC768843 for ; Sun, 4 Mar 2018 18:31:19 +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 258F312F32 for ; Sun, 4 Mar 2018 18:31:18 +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 w24IVIEB004970 for ; Sun, 4 Mar 2018 18:31:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w24IVIsB004962 for freebsd-fs@FreeBSD.org; Sun, 4 Mar 2018 18:31:18 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: freebsd-fs@FreeBSD.org Subject: [Bug 208882] zfs root filesystem mount failure on startup in FreeBSD 10.3-RELEASE if USB hdd with zpool is attached to another port Date: Sun, 04 Mar 2018 18:31:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: imp@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Mar 2018 18:31:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208882 Warner Losh changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |imp@FreeBSD.org --- Comment #19 from Warner Losh --- There needs to be a 'zpool wait' or there needs to be something that tries again when devices arrive in the background dependng on how critical the ne= ed for the zpool is. devd could be useful here, imho. devd is also useful for mounting /usr or some other crit fs when the device arrives, and we could p= ut waits in rc for them if necessary. That may need some more thought. IMHO, the whole root hold thing is shite and should be flushed. It should be replaced by a loop similar to what we have today: try to mount /, sleep unt= il the next device arrives and try again. timeout to a prompt after N seconds = (or in an ideal world, when kbkit is true :). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Mar 4 21:01:31 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 EE0C8F3265E for ; Sun, 4 Mar 2018 21:01:30 +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 66CB06F576 for ; Sun, 4 Mar 2018 21:01:30 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 8E00614622 for ; Sun, 4 Mar 2018 21:01:29 +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 w24L1Thn022139 for ; Sun, 4 Mar 2018 21:01:29 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w24L1TOH022131 for freebsd-fs@FreeBSD.org; Sun, 4 Mar 2018 21:01:29 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201803042101.w24L1TOH022131@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: freebsd-fs@FreeBSD.org Subject: Problem reports for freebsd-fs@FreeBSD.org that need special attention Date: Sun, 4 Mar 2018 21:01:29 +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, 04 Mar 2018 21:01:31 -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 Mar 4 21:04:08 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 C97C4F32D34; Sun, 4 Mar 2018 21:04:08 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6E40F6FB31; Sun, 4 Mar 2018 21:04:07 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1esane-000619-67; Sun, 04 Mar 2018 22:04:06 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-fs@freebsd.org, "FreeBSD Current" Date: Sun, 04 Mar 2018 22:04:05 +0100 Subject: vboxvfs: Not a directory MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 51a43cd7ff6838d9e9bce89dbcde6c26 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, 04 Mar 2018 21:04:09 -0000 Hi, I'm trying to use vboxfs on # uname -a FreeBSD sjakie 12.0-CURRENT FreeBSD 12.0-CURRENT #4 r329516M: Sun Feb 18 12:37:36 CET 2018 ronald@sjakie:/data/ronald/obj-freebsd-current/data/ronald/freebsd-current/amd64.amd64/sys/GENERIC-NODEBUG amd64 I run VirtualBox on Windows 10 using FreeBSD 12 as a guest. virtualbox-ose-additions-5.2.8 is installed by pkg. I configured C:\Temp as 'win' in VirtualBox. Modules are loaded: kldstat | grep vbox 5 2 0xffffffff82e26000 2d9e0 vboxguest.ko 13 1 0xffffffff82e7e000 1f320 vboxvfs.ko [root@sjakie ~]# mount_vboxvfs win /mnt/win [root@sjakie ~]# ls /mnt/win/ ls: /mnt/win/: Not a directory I tried different Windows directories and different users/rights on the /mnt/win directory. Am I doing something wrong? I can't find a lot documentation about vboxvfs. Regards, Ronald. From owner-freebsd-fs@freebsd.org Mon Mar 5 01:00:04 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 02F3AF44706; Mon, 5 Mar 2018 01:00:04 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 76E5679CF8; Mon, 5 Mar 2018 01:00:03 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 19ABDC13C; Mon, 5 Mar 2018 01:00:02 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id E487696E; Mon, 5 Mar 2018 01:00:00 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id 9h7f-RI9ZLMf; Mon, 5 Mar 2018 00:59:54 +0000 (UTC) To: "current@freebsd.org" , FreeBSD FS DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com 28E74965 From: Bryan Drewery Subject: ZFS panic at boot when mounting root on r330386 Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: <681cabc1-9b50-8f27-5242-5a9eb3ed3c39@FreeBSD.org> Date: Sun, 4 Mar 2018 16:59:52 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WqOnxRM9OjFGG5SKa6gk4xpdlGMUlmWUA" 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, 05 Mar 2018 01:00:04 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --WqOnxRM9OjFGG5SKa6gk4xpdlGMUlmWUA Content-Type: multipart/mixed; boundary="LHTKNrnkHzCknXGbmclPwT8dSFMkQO2Mu"; protected-headers="v1" From: Bryan Drewery To: "current@freebsd.org" , FreeBSD FS Message-ID: <681cabc1-9b50-8f27-5242-5a9eb3ed3c39@FreeBSD.org> Subject: ZFS panic at boot when mounting root on r330386 --LHTKNrnkHzCknXGbmclPwT8dSFMkQO2Mu Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable > panic: solaris assert: refcount_count(&spa->spa_refcount) > spa->spa_mi= nref || MUTEX_HELD(&spa_namespace_lock), file: /usr/src/sys/cddl/contrib/= opensolaris/uts/common/fs/zfs/spa_misc.c, line: 952 > cpuid =3D 10 > time =3D 1520207367 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe23f= 57a2420 > vpanic() at vpanic+0x18d/frame 0xfffffe23f57a2480 > panic() at panic+0x43/frame 0xfffffe23f57a24e0 > assfail() at assfail+0x1a/frame 0xfffffe23f57a24f0 > spa_close() at spa_close+0x5d/frame 0xfffffe23f57a2520 > spa_get_stats() at spa_get_stats+0x481/frame 0xfffffe23f57a2700 > zfs_ioc_pool_stats() at zfs_ioc_pool_stats+0x25/frame 0xfffffe23f57a274= 0 > zfsdev_ioctl() at zfsdev_ioctl+0x76b/frame 0xfffffe23f57a27e0 > devfs_ioctl() at devfs_ioctl+0xcb/frame 0xfffffe23f57a2830 > VOP_IOCTL_APV() at VOP_IOCTL_APV+0x102/frame 0xfffffe23f57a2860 > vn_ioctl() at vn_ioctl+0x124/frame 0xfffffe23f57a2970 > devfs_ioctl_f() at devfs_ioctl_f+0x1f/frame 0xfffffe23f57a2990 > kern_ioctl() at kern_ioctl+0x2c2/frame 0xfffffe23f57a29f0 > sys_ioctl() at sys_ioctl+0x15c/frame 0xfffffe23f57a2ac0 > amd64_syscall() at amd64_syscall+0x786/frame 0xfffffe23f57a2bf0 > fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe23f57a= 2bf0 > --- syscall (54, FreeBSD ELF64, sys_ioctl), rip =3D 0x80049afda, rsp =3D= 0x7fffffffbd18, rbp =3D 0x7fffffffbd90 --- > KDB: enter: panic > [ thread pid 56 tid 100606 ] > Stopped at kdb_enter+0x3b: movq $0,kdb_why > db> It seems like a race as I can get it to boot sometimes. --=20 Regards, Bryan Drewery --LHTKNrnkHzCknXGbmclPwT8dSFMkQO2Mu-- --WqOnxRM9OjFGG5SKa6gk4xpdlGMUlmWUA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJanJaIAAoJEDXXcbtuRpfPmZYIAMnfBvvSfLR+S0ypcIrvwR8K wz2XiHw4zo0TAd/j3blNXaX+LRNOnxS49ojiyhrLwv5C5lLMYQQ+LxhhVJW6EP3d u433gDMgKBaeFQc+rHSczSsknmWNDUvNEESF0L304fm5Idq423nOSep0GnK5pJOw yhH9Hvfq7iGQXbsqO4faAZLDnp7NLoWUptE9atGqicU9k7zayUxYbVDtVli8Fguo rch9R8yrflWxwZysu09esQfJ1nTTY8CrhOqKJ1yjNjiFkwdV5YEdnw/5tuwvHM9+ jGRMgzqFKQTpQC4PLbGYvgj/LoCDG/oGzxFiny5NQfKRr9ehGA9t9edix0nKKCA= =j2cg -----END PGP SIGNATURE----- --WqOnxRM9OjFGG5SKa6gk4xpdlGMUlmWUA-- From owner-freebsd-fs@freebsd.org Mon Mar 5 06:24:59 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 0C20EF35108; Mon, 5 Mar 2018 06:24:59 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com [209.85.215.41]) (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 675D78579C; Mon, 5 Mar 2018 06:24:58 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f41.google.com with SMTP id 37so21427690lfs.7; Sun, 04 Mar 2018 22:24:58 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=UT26Tlr8N97BXiqJOrYKqp3fK7llfSt+cUlKTQR7BFo=; b=e246f27fq3r8H2ZByfcV1ldltn53NLKsowp3xwqehUECcgPoxXWp/T0k0DFahIwjRU 3wGYDsnI/O6x4DCkdoF97XngRJXG9CbwsTOT3oZU9vh9INRabEUcxom+/Td+A9JfZRtE GeAHwtIyidGRu6SP2eKc8u2dgZmjrPtsPAHyogQmViJVerqPsbZOy2gYjlzOpcTWbv33 xNSLKtMSlp4qGHq3wzxHCneqPK3LNeLsnqLsGzXLjyDE5ZGk+zHMiK+lmn2BlZLL5tFq bCjXg0e5iC4UOmKNG3xkFH9lAK0w1OZKqFRcWCHWB3UhbGMeQa0CCnioT3xwkIgtRTNj TVCg== X-Gm-Message-State: AElRT7F8i+k5zMpQUbo5Dhl8wkoBgvtybS73UsEKMGI+uAbaZunbevWk Q4EVdzwz+chDJ5XPkr0OaWNqpO55 X-Google-Smtp-Source: AG47ELtekot6ayH0fN1KrED5k1wXHlPNyCdjx13oi1uhp1W6bZP4Pb6c6PhHscyn102c4imSdD8vYg== X-Received: by 10.46.87.72 with SMTP id r8mr9293185ljd.93.1520231091136; Sun, 04 Mar 2018 22:24:51 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id 21sm2568536ljc.82.2018.03.04.22.24.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 04 Mar 2018 22:24:50 -0800 (PST) Subject: Re: ZFS panic at boot when mounting root on r330386 To: Bryan Drewery , "current@freebsd.org" , FreeBSD FS References: <681cabc1-9b50-8f27-5242-5a9eb3ed3c39@FreeBSD.org> From: Andriy Gapon Message-ID: <407e9672-f138-38de-c10f-a0bcee0716be@FreeBSD.org> Date: Mon, 5 Mar 2018 08:24:49 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <681cabc1-9b50-8f27-5242-5a9eb3ed3c39@FreeBSD.org> 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: Mon, 05 Mar 2018 06:24:59 -0000 On 05/03/2018 02:59, Bryan Drewery wrote: >> panic: solaris assert: refcount_count(&spa->spa_refcount) > spa->spa_minref || MUTEX_HELD(&spa_namespace_lock), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/spa_misc.c, line: 952 >> cpuid = 10 >> time = 1520207367 >> KDB: stack backtrace: >> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe23f57a2420 >> vpanic() at vpanic+0x18d/frame 0xfffffe23f57a2480 >> panic() at panic+0x43/frame 0xfffffe23f57a24e0 >> assfail() at assfail+0x1a/frame 0xfffffe23f57a24f0 >> spa_close() at spa_close+0x5d/frame 0xfffffe23f57a2520 >> spa_get_stats() at spa_get_stats+0x481/frame 0xfffffe23f57a2700 >> zfs_ioc_pool_stats() at zfs_ioc_pool_stats+0x25/frame 0xfffffe23f57a2740 >> zfsdev_ioctl() at zfsdev_ioctl+0x76b/frame 0xfffffe23f57a27e0 >> devfs_ioctl() at devfs_ioctl+0xcb/frame 0xfffffe23f57a2830 >> VOP_IOCTL_APV() at VOP_IOCTL_APV+0x102/frame 0xfffffe23f57a2860 >> vn_ioctl() at vn_ioctl+0x124/frame 0xfffffe23f57a2970 >> devfs_ioctl_f() at devfs_ioctl_f+0x1f/frame 0xfffffe23f57a2990 >> kern_ioctl() at kern_ioctl+0x2c2/frame 0xfffffe23f57a29f0 >> sys_ioctl() at sys_ioctl+0x15c/frame 0xfffffe23f57a2ac0 >> amd64_syscall() at amd64_syscall+0x786/frame 0xfffffe23f57a2bf0 >> fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe23f57a2bf0 >> --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x80049afda, rsp = 0x7fffffffbd18, rbp = 0x7fffffffbd90 --- >> KDB: enter: panic >> [ thread pid 56 tid 100606 ] >> Stopped at kdb_enter+0x3b: movq $0,kdb_why >> db> > > It seems like a race as I can get it to boot sometimes. Yes, it does. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210409 -- Andriy Gapon From owner-freebsd-fs@freebsd.org Mon Mar 5 12:10:53 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 49BA3F29092; Mon, 5 Mar 2018 12:10:53 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D2AFC7619F; Mon, 5 Mar 2018 12:10:52 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.avinity.tv (unknown [77.95.97.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 30826171FD; Mon, 5 Mar 2018 13:10:50 +0100 (CET) From: Dimitry Andric Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_964AB4CF-CDC5-4A80-AA77-493179094E33"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: zfs problems after rebuilding system [SOLVED] Date: Mon, 5 Mar 2018 13:10:48 +0100 In-Reply-To: <20180303234236.M3811@besplex.bde.org> Cc: tech-lists , FreeBSD Filesystems , FreeBSD Stable To: Bruce Evans References: <21c64a2d-b9f9-24c8-88ec-ff1210891f60@zyxst.net> <1dc2b8ef-2914-8182-e2b0-ac637e6b2095@zyxst.net> <65372449-53f1-8002-981a-e20f4a592e26@zyxst.net> <5CFC89E9-57BE-4CB7-9C55-0D3CCF1E8D3D@FreeBSD.org> <20180303234236.M3811@besplex.bde.org> X-Mailer: Apple Mail (2.3273) 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, 05 Mar 2018 12:10:53 -0000 --Apple-Mail=_964AB4CF-CDC5-4A80-AA77-493179094E33 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 3 Mar 2018, at 13:56, Bruce Evans wrote: > > On Sat, 3 Mar 2018, tech-lists wrote: >> On 03/03/2018 00:23, Dimitry Andric wrote: ... >>> Whether this is due to some sort of BIOS handover trouble, or due to >>> cheap and/or crappy USB-to-SATA bridges (even with brand WD and Seagate >>> disks!), I have no idea. I attempted to debug it at some point, but >>> a well-placed "sleep 10" was an acceptable workaround... :) >> >> That fixed it, thank you again :D > > That won't work for the boot drive. > > When no boot drive is detected early enough, the kernel goes to the > mountroot prompt. That seems to hold a Giant lock which inhibits > further progress being made. Sometimes progress can be made by trying > to mount unmountable partitions on other drives, but this usually goes > too fast, especially if the USB drive often times out. What I would like to know, is why our USB stack has such timeout issues at all. When I boot Linux on the same type of hardware, I never see USB timeouts. They must be doing something right, or maybe they just don't bother checking some status bits that we are very strict about? -Dimitry --Apple-Mail=_964AB4CF-CDC5-4A80-AA77-493179094E33 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWp0zyAAKCRCwXqMKLiCW ox4PAKCWp0chtfvrf/plVG056kdey/h94wCgvFWof7JkHBclVqAdAWiqXqSCYz4= =aRJ0 -----END PGP SIGNATURE----- --Apple-Mail=_964AB4CF-CDC5-4A80-AA77-493179094E33-- From owner-freebsd-fs@freebsd.org Mon Mar 5 16:49:43 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 2CA2BF3E6FE for ; Mon, 5 Mar 2018 16:49:43 +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 9F1538227D for ; Mon, 5 Mar 2018 16:49:42 +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 BD1821EA86 for ; Mon, 5 Mar 2018 16:49:41 +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 w25GnfK1046644 for ; Mon, 5 Mar 2018 16:49:41 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w25Gnfoj046643 for freebsd-fs@FreeBSD.org; Mon, 5 Mar 2018 16:49:41 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: freebsd-fs@FreeBSD.org Subject: [Bug 210409] zfs: panic during boot Date: Mon, 05 Mar 2018 16: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: bdrewery@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2018 16:49:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210409 --- Comment #10 from Bryan Drewery --- I hit this like 7 times yesterday on r330386. # zpool status pool: scratch state: ONLINE scan: scrub repaired 0 in 0h20m with 0 errors on Mon Jan 29 10:08:25 2018 config: NAME STATE READ WRITE CKSUM scratch ONLINE 0 0 0 gpt/disk2 ONLINE 0 0 0 logs gpt/log1 ONLINE 0 0 0 cache gpt/cache1 ONLINE 0 0 0 errors: No known data errors pool: zroot state: ONLINE scan: scrub repaired 0 in 2h43m with 0 errors on Tue Feb 20 06:42:23 2018 config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 gpt/disk0 ONLINE 0 0 0 gpt/disk1 ONLINE 0 0 0 logs gpt/log0 ONLINE 0 0 0 cache gpt/cache0 ONLINE 0 0 0 errors: No known data errors # gpart show =3D> 40 1953525088 ada0 GPT (932G) 40 256 1 freebsd-boot (128K) 296 16777216 2 freebsd-swap (8.0G) 16777512 1936747616 3 freebsd-zfs (924G) =3D> 40 1953525088 ada1 GPT (932G) 40 256 1 freebsd-boot (128K) 296 16777216 2 freebsd-swap (8.0G) 16777512 1936747616 3 freebsd-zfs (924G) =3D> 34 250069613 ada2 GPT (119G) 34 2014 - free - (1.0M) 2048 2097152 1 freebsd-zfs (1.0G) 2099200 104857600 2 freebsd-zfs (50G) 106956800 2097152 3 freebsd-zfs (1.0G) 109053952 104857600 4 freebsd-zfs (50G) 213911552 36158095 - free - (17G) =3D> 40 1953525088 ada3 GPT (932G) 40 256 1 freebsd-boot (128K) 296 960495616 2 freebsd-zfs (458G) 960495912 209715200 3 freebsd-swap (100G) 1170211112 783314016 - free - (374G) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Mar 5 17:17:54 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 7FF05F40DAB for ; Mon, 5 Mar 2018 17:17:54 +0000 (UTC) (envelope-from bengt.ahlgren@ri.se) Received: from se-out1.mx-wecloud.net (se-out1.mx-wecloud.net [89.221.255.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.mx-wecloud.net", Issuer "GeoTrust SHA256 SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 17AD18468F for ; Mon, 5 Mar 2018 17:17:53 +0000 (UTC) (envelope-from bengt.ahlgren@ri.se) Received: from sp-mail-3.sp.se (unknown [194.218.146.197]) by se-out1.mx-wecloud.net (Postfix) with ESMTPS id C85B3205383 for ; Mon, 5 Mar 2018 17:17:43 +0000 (UTC) Received: from P142s.sics.se (10.116.0.226) by sp-mail-3.sp.se (10.100.0.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.35; Mon, 5 Mar 2018 18:17:44 +0100 Received: (from bengta@localhost) by P142s.sics.se (8.15.2/8.15.2/Submit) id w25HGtFL006558; Mon, 5 Mar 2018 18:16:55 +0100 (CET) (envelope-from bengt.ahlgren@ri.se) X-Authentication-Warning: P142s.sics.se: bengta set sender to bengt.ahlgren@ri.se using -f From: Bengt Ahlgren To: Subject: "PI - Protection Information" drives? User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix) Date: Mon, 5 Mar 2018 18:16:54 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.116.0.226] X-ClientProxiedBy: sp-mail-3.sp.se (10.100.0.163) To sp-mail-3.sp.se (10.100.0.163) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=cdiiljLM c=1 sm=1 tr=0 a=L5DDne6A+dD0FbDkt2Fblw==:117 a=L5DDne6A+dD0FbDkt2Fblw==:17 a=sZ8rJzgPlrQA:10 a=v2DPQv5-lfwA:10 a=sq00Bc2Utgu_OoRDXvAA:9 a=rLUZ03C7qZVs2rH-:21 a=Bc_q9Cznz1F_rGEM:21 X-Virus-Scanned: clamav-milter 0.99.3 at MailSecurity X-Virus-Status: Clean X-MailSecurity-Status: 0 X-Scanned-By: WeCloud MailSecurity X-MailSecurity-Score: 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, 05 Mar 2018 17:17:54 -0000 I've recently gotten a (Dell-branded) Seagate drive which seems to be formatted with something called "Protection Information (PI) type 2". CDB read/write commands of size 6 seems to work, but any read/write commands of size 10 (or larger) do not work: (da20:mps0:0:11:0): READ(10). CDB: 28 00 00 00 00 00 00 01 00 00 (da20:mps0:0:11:0): CAM status: SCSI Status Error (da20:mps0:0:11:0): SCSI status: Check Condition (da20:mps0:0:11:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code) (da20:mps0:0:11:0): Error 22, Unretryable error smartctl output says: === START OF INFORMATION SECTION === Vendor: SEAGATE Product: ST600MM0238 Revision: BS04 Compliance: SPC-4 User Capacity: 600,127,266,816 bytes [600 GB] Logical block size: 512 bytes Formatted with type 2 protection LU is fully provisioned Rotation Rate: 10000 rpm Form Factor: 2.5 inches Logical Unit id: XXX Serial number: YYY Device type: disk Transport protocol: SAS (SPL-3) Local Time is: Mon Mar 5 17:54:09 2018 CET SMART support is: Available - device has SMART capability. SMART support is: Enabled Temperature Warning: Disabled or Not Supported Read Cache is: Enabled Writeback Cache is: Disabled Any advice? Does this "Protection Information" work at all with FreeBSD? Or do I simply need to reformat the drive without this "PI" stuff? Bengt From owner-freebsd-fs@freebsd.org Mon Mar 5 17:35: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 A6CC8F42249 for ; Mon, 5 Mar 2018 17:35:21 +0000 (UTC) (envelope-from karli@inparadise.se) Received: from mail.inparadise.se (h-246-50.A444.priv.bahnhof.se [155.4.246.50]) (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 2955B8571B for ; Mon, 5 Mar 2018 17:35:19 +0000 (UTC) (envelope-from karli@inparadise.se) Received: from localhost (localhost [127.0.0.1]) by mail.inparadise.se (Postfix) with ESMTP id C843142D3A; Mon, 5 Mar 2018 18:27:36 +0100 (CET) Received: from mail.inparadise.se ([127.0.0.1]) by localhost (mail.inparadise.se [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id M1Z6O0Ltc6sp; Mon, 5 Mar 2018 18:27:34 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.inparadise.se (Postfix) with ESMTP id 44F1342D3B; Mon, 5 Mar 2018 18:27:34 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.inparadise.se 44F1342D3B X-Virus-Scanned: amavisd-new at inparadise.se Received: from mail.inparadise.se ([127.0.0.1]) by localhost (mail.inparadise.se [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id c6eAybADF6V5; Mon, 5 Mar 2018 18:27:33 +0100 (CET) Received: from mail.inparadise.se (localhost [127.0.0.1]) by mail.inparadise.se (Postfix) with ESMTP id EA92F42D3A; Mon, 5 Mar 2018 18:27:33 +0100 (CET) Date: Mon, 5 Mar 2018 18:27:33 +0100 (CET) Subject: Re: "PI - Protection Information" drives? Message-ID: X-Android-Message-ID: To: Bengt Ahlgren Cc: freebsd-fs@FreeBSD.org Importance: Normal X-Priority: 3 X-MSMail-Priority: Normal From: =?utf-8?B?S2FybGkgU2rDtmJlcmc=?= X-Originating-IP: [172.16.1.122, 127.0.0.1] X-Mailer: Zimbra 8.7.11_GA_1854 (Android-Mail/8.2.11.186835846.release(...883836) devip=172.16.1.122 ZPZB/66) In-Reply-To: References: Thread-Topic: "PI - Protection Information" drives? Thread-Index: EUjrIG/CbeIiNtX0xWKFg6pZBTFlwQ== 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: Mon, 05 Mar 2018 17:35:21 -0000 From owner-freebsd-fs@freebsd.org Mon Mar 5 17:56:20 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 C880DF43691 for ; Mon, 5 Mar 2018 17:56:20 +0000 (UTC) (envelope-from bengt.ahlgren@ri.se) Received: from se-out1.mx-wecloud.net (se-out1.mx-wecloud.net [89.221.255.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.mx-wecloud.net", Issuer "GeoTrust SHA256 SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 569188640B for ; Mon, 5 Mar 2018 17:56:20 +0000 (UTC) (envelope-from bengt.ahlgren@ri.se) Received: from sp-mail-3.sp.se (unknown [194.218.146.197]) by se-out1.mx-wecloud.net (Postfix) with ESMTPS id 3881120540B; Mon, 5 Mar 2018 17:56:17 +0000 (UTC) Received: from P142s.sics.se (10.116.0.226) by sp-mail-3.sp.se (10.100.0.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.35; Mon, 5 Mar 2018 18:56:18 +0100 Received: (from bengta@localhost) by P142s.sics.se (8.15.2/8.15.2/Submit) id w25HtX7l006720; Mon, 5 Mar 2018 18:55:33 +0100 (CET) (envelope-from bengt.ahlgren@ri.se) X-Authentication-Warning: P142s.sics.se: bengta set sender to bengt.ahlgren@ri.se using -f From: Bengt Ahlgren To: Karli =?iso-8859-1?Q?Sj=F6berg?= CC: Subject: Re: "PI - Protection Information" drives? In-Reply-To: ("Karli =?iso-8859-1?Q?Sj=F6berg=22's?= message of "Mon, 5 Mar 2018 18:27:33 +0100 (CET)") References: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix) Date: Mon, 5 Mar 2018 18:55:33 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Originating-IP: [10.116.0.226] X-ClientProxiedBy: sp-mail-3.sp.se (10.100.0.163) To sp-mail-3.sp.se (10.100.0.163) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=cdiiljLM c=1 sm=1 tr=0 a=L5DDne6A+dD0FbDkt2Fblw==:117 a=L5DDne6A+dD0FbDkt2Fblw==:17 a=sZ8rJzgPlrQA:10 a=8nJEP1OIZ-IA:10 a=v2DPQv5-lfwA:10 a=9sJiun-3AAAA:8 a=kXTTJs9nzwDTBVYrw7IA:9 a=cqisCOBPvHMNWI2_:21 a=qRZpR7f2glkuSXAg:21 a=wPNLvfGTeEIA:10 a=E9LtQix4xlUA:10 a=NxUpaCPaS5wA:10 a=6IWsxHMPXfbp9B873oa7:22 X-Virus-Scanned: clamav-milter 0.99.3 at MailSecurity X-Virus-Status: Clean X-MailSecurity-Status: 0 X-Scanned-By: WeCloud MailSecurity X-MailSecurity-Score: 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, 05 Mar 2018 17:56:21 -0000 Karli Sj=F6berg writes: > Den 5 mars 2018 18:19 skrev Bengt Ahlgren : > > I've recently gotten a (Dell-branded) Seagate drive which seems to be > formatted with something called "Protection Information (PI) type 2". > > CDB read/write commands of size 6 seems to work, but any read/write > commands of size 10 (or larger) do not work: > > (da20:mps0:0:11:0): READ(10). CDB: 28 00 00 00 00 00 00 01 00 00=20 > (da20:mps0:0:11:0): CAM status: SCSI Status Error > (da20:mps0:0:11:0): SCSI status: Check Condition > (da20:mps0:0:11:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid comman= d operation code) > (da20:mps0:0:11:0): Error 22, Unretryable error > > smartctl output says: > > =3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D > Vendor: SEAGATE > Product: ST600MM0238 > Revision: BS04 > Compliance: SPC-4 > User Capacity: 600,127,266,816 bytes [600 GB] > Logical block size: 512 bytes > Formatted with type 2 protection > LU is fully provisioned > Rotation Rate: 10000 rpm > Form Factor: 2.5 inches > Logical Unit id: XXX > Serial number: YYY > Device type: disk > Transport protocol: SAS (SPL-3) > Local Time is: Mon Mar 5 17:54:09 2018 CET > SMART support is: Available - device has SMART capability. > SMART support is: Enabled > Temperature Warning: Disabled or Not Supported > Read Cache is: Enabled > Writeback Cache is: Disabled > > Any advice? Does this "Protection Information" work at all with > FreeBSD? Or do I simply need to reformat the drive without this "PI" > stuff? > > Had this problem except they were IBM branded. After much googling I foun= d this: > https://forums.freenas.org/index.php?threads/scsi-errors-unable-to-wipe-d= rives-9240-9211-w-ibm-seagate-disks.43453/#post-287162 > > > PIA if you ask me :) Thanks for the pointer! Do I need that sg_format utility, or will camcontrol format also do the right thing? Bengt From owner-freebsd-fs@freebsd.org Mon Mar 5 18:01:09 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 9E509F43AF2 for ; Mon, 5 Mar 2018 18:01:09 +0000 (UTC) (envelope-from karli@inparadise.se) Received: from mail.inparadise.se (h-246-50.A444.priv.bahnhof.se [155.4.246.50]) (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 0FF808674E for ; Mon, 5 Mar 2018 18:01:08 +0000 (UTC) (envelope-from karli@inparadise.se) Received: from localhost (localhost [127.0.0.1]) by mail.inparadise.se (Postfix) with ESMTP id 5B69C42D3D; Mon, 5 Mar 2018 19:01:07 +0100 (CET) Received: from mail.inparadise.se ([127.0.0.1]) by localhost (mail.inparadise.se [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id MhSXsRS1ExVT; Mon, 5 Mar 2018 19:01:06 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.inparadise.se (Postfix) with ESMTP id 57F0742D3E; Mon, 5 Mar 2018 19:01:06 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.10.3 mail.inparadise.se 57F0742D3E X-Virus-Scanned: amavisd-new at inparadise.se Received: from mail.inparadise.se ([127.0.0.1]) by localhost (mail.inparadise.se [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id mzvJlPvIVIiz; Mon, 5 Mar 2018 19:01:06 +0100 (CET) Received: from mail.inparadise.se (localhost [127.0.0.1]) by mail.inparadise.se (Postfix) with ESMTP id 38CF842D3D; Mon, 5 Mar 2018 19:01:06 +0100 (CET) Date: Mon, 5 Mar 2018 19:01:05 +0100 (CET) Subject: Re: "PI - Protection Information" drives? Message-ID: X-Android-Message-ID: To: Bengt Ahlgren Cc: freebsd-fs@FreeBSD.org Importance: Normal X-Priority: 3 X-MSMail-Priority: Normal From: =?utf-8?B?S2FybGkgU2rDtmJlcmc=?= X-Originating-IP: [172.16.1.122, 127.0.0.1] X-Mailer: Zimbra 8.7.11_GA_1854 (Android-Mail/8.2.11.186835846.release(...883836) devip=172.16.1.122 ZPZB/66) In-Reply-To: References: Thread-Topic: "PI - Protection Information" drives? Thread-Index: c/AFE0BzJtqCoF3RfafVjVG+gmuaUg== 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: Mon, 05 Mar 2018 18:01:09 -0000 From owner-freebsd-fs@freebsd.org Mon Mar 5 18:10: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 4391EF44396 for ; Mon, 5 Mar 2018 18:10:51 +0000 (UTC) (envelope-from arthur_ramsey@mediture.com) Received: from zimbra.mediture.com (zimbra.mediture.com [198.181.114.30]) (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 DFE6786B5F for ; Mon, 5 Mar 2018 18:10:50 +0000 (UTC) (envelope-from arthur_ramsey@mediture.com) Received: from zimbra.mediture.com (localhost.localdomain [127.0.0.1]) by mail01.mediture.dom (Postfix) with ESMTPS id A5C2B1E2DCF; Mon, 5 Mar 2018 12:01:42 -0600 (CST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail01.mediture.dom (Postfix) with ESMTP id 9A6A51E261D; Mon, 5 Mar 2018 12:01:42 -0600 (CST) X-Amavis-Modified: Mail body modified (using disclaimer) - mail01.mediture.dom Received: from zimbra.mediture.com ([127.0.0.1]) by localhost (mail01.mediture.dom [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Dat0M7uRrYS5; Mon, 5 Mar 2018 12:01:42 -0600 (CST) Received: from [192.168.1.11] (c-68-47-45-5.hsd1.mn.comcast.net [68.47.45.5]) by mail01.mediture.dom (Postfix) with ESMTPSA id 6AE7E1E100B; Mon, 5 Mar 2018 12:01:42 -0600 (CST) Subject: Re: "PI - Protection Information" drives? To: Bengt Ahlgren , freebsd-fs@FreeBSD.org References: From: Arthur Ramsey Message-ID: <12866633-3997-91b9-91c9-3e1e320d210b@mediture.com> Date: Mon, 5 Mar 2018 12:01:47 -0600 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed 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: Mon, 05 Mar 2018 18:10:51 -0000 It should work fine with FreeBSD but I haven't tried.=C2=A0 I've had the = same=20 issue when using PI Type 2 protected disk from another system and just=20 removed it since other disks didn't have it enabled. sg_format -v --format --fmtpinfo=3D0 /dev/... =0A This e-mail and any attachments may contain CONFIDENTIAL information, including PROTECTED HEALTH INFORMATION. If you are not the intended recipient, any use or disclosure of this information is STRICTLY PROHIBITED; you are requested to delete this e-mail and any attachments, notify the sender immediately, and notify the Mediture Privacy Officer at privacyofficer@mediture.com.=0A From owner-freebsd-fs@freebsd.org Mon Mar 5 20:38: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 7B0BEF268EE for ; Mon, 5 Mar 2018 20:38:27 +0000 (UTC) (envelope-from bengt.ahlgren@ri.se) Received: from se-out1.mx-wecloud.net (se-out1.mx-wecloud.net [89.221.255.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.mx-wecloud.net", Issuer "GeoTrust SHA256 SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 066816CBDC for ; Mon, 5 Mar 2018 20:38:26 +0000 (UTC) (envelope-from bengt.ahlgren@ri.se) Received: from sp-mail-3.sp.se (unknown [194.218.146.197]) by se-out1.mx-wecloud.net (Postfix) with ESMTPS id 20E5820539F; Mon, 5 Mar 2018 20:38:23 +0000 (UTC) Received: from P142s.sics.se (10.116.0.226) by sp-mail-3.sp.se (10.100.0.163) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1261.35; Mon, 5 Mar 2018 21:38:24 +0100 Received: (from bengta@localhost) by P142s.sics.se (8.15.2/8.15.2/Submit) id w25KbeYH001709; Mon, 5 Mar 2018 21:37:40 +0100 (CET) (envelope-from bengt.ahlgren@ri.se) X-Authentication-Warning: P142s.sics.se: bengta set sender to bengt.ahlgren@ri.se using -f From: Bengt Ahlgren To: Karli =?iso-8859-1?Q?Sj=F6berg?= CC: Subject: Re: "PI - Protection Information" drives? In-Reply-To: ("Karli =?iso-8859-1?Q?Sj=F6berg=22's?= message of "Mon, 5 Mar 2018 19:01:05 +0100 (CET)") References: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (berkeley-unix) Date: Mon, 5 Mar 2018 21:37:39 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Originating-IP: [10.116.0.226] X-ClientProxiedBy: sp-mail-3.sp.se (10.100.0.163) To sp-mail-3.sp.se (10.100.0.163) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=cdiiljLM c=1 sm=1 tr=0 a=L5DDne6A+dD0FbDkt2Fblw==:117 a=L5DDne6A+dD0FbDkt2Fblw==:17 a=sZ8rJzgPlrQA:10 a=8nJEP1OIZ-IA:10 a=v2DPQv5-lfwA:10 a=9sJiun-3AAAA:8 a=SJGkUz6zoyZA-hrs1s8A:9 a=_gFpU0izUA-tIVNw:21 a=3OfQ3edhQFPWTjao:21 a=wPNLvfGTeEIA:10 a=E9LtQix4xlUA:10 a=NxUpaCPaS5wA:10 a=6IWsxHMPXfbp9B873oa7:22 X-Virus-Scanned: clamav-milter 0.99.3 at MailSecurity X-Virus-Status: Clean X-MailSecurity-Status: 0 X-Scanned-By: WeCloud MailSecurity X-MailSecurity-Score: 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, 05 Mar 2018 20:38:27 -0000 Karli Sj=F6berg writes: > Den 5 mars 2018 18:56 skrev Bengt Ahlgren : > > Karli Sj=F6berg writes: > > > Den 5 mars 2018 18:19 skrev Bengt Ahlgren : > > > > I've recently gotten a (Dell-branded) Seagate drive which seems to be > > formatted with something called "Protection Information (PI) type 2". > > > > CDB read/write commands of size 6 seems to work, but any read/write > > commands of size 10 (or larger) do not work: > > > > (da20:mps0:0:11:0): READ(10). CDB: 28 00 00 00 00 00 00 01 00 00=20 > > (da20:mps0:0:11:0): CAM status: SCSI Status Error > > (da20:mps0:0:11:0): SCSI status: Check Condition > > (da20:mps0:0:11:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid comm= and > operation code) > > (da20:mps0:0:11:0): Error 22, Unretryable error > > > > smartctl output says: > > > > =3D=3D=3D START OF INFORMATION SECTION =3D=3D=3D > > Vendor: SEAGATE > > Product: ST600MM0238 > > Revision: BS04 > > Compliance: SPC-4 > > User Capacity: 600,127,266,816 bytes [600 GB] > > Logical block size: 512 bytes > > Formatted with type 2 protection > > LU is fully provisioned > > Rotation Rate: 10000 rpm > > Form Factor: 2.5 inches > > Logical Unit id: XXX > > Serial number: YYY > > Device type: disk > > Transport protocol: SAS (SPL-3) > > Local Time is: Mon Mar 5 17:54:09 2018 CET > > SMART support is: Available - device has SMART capability. > > SMART support is: Enabled > > Temperature Warning: Disabled or Not Supported > > Read Cache is: Enabled > > Writeback Cache is: Disabled > > > > Any advice? Does this "Protection Information" work at all with > > FreeBSD? Or do I simply need to reformat the drive without this "PI" > > stuff? > > > > Had this problem except they were IBM branded. After much googling I f= ound this: > > > https://forums.freenas.org/index.php?threads/scsi-errors-unable-to-wipe-= drives-9240-9211-w-ibm-seagate-disks.43453/#post-287162 >=20=20 > > > > > > PIA if you ask me :) > > Thanks for the pointer! > > Do I need that sg_format utility, or will camcontrol format also do the > right thing? > > Bengt > > No idea, but the 'sg_format' utility is part of the 'sg3_utils' package, = so it's easy enough to > come by. Tried sg_format - it did the trick! Thanks again! Bengt From owner-freebsd-fs@freebsd.org Tue Mar 6 18:35:57 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 18CE5F497B3 for ; Tue, 6 Mar 2018 18:35:57 +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 AA88D841A0 for ; Tue, 6 Mar 2018 18:35:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id CF0CF4669 for ; Tue, 6 Mar 2018 18:35:55 +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 w26IZti6055113 for ; Tue, 6 Mar 2018 18:35:55 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w26IZtuC055112 for freebsd-fs@FreeBSD.org; Tue, 6 Mar 2018 18:35:55 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: freebsd-fs@FreeBSD.org Subject: [Bug 216368] [samba] Network group, machine, and share browsing does not work correctly. Date: Tue, 06 Mar 2018 18:35:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: w.schwarzenfeld@utanet.at X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Not A Bug X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status cc resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2018 18:35:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216368 w.schwarzenfeld@utanet.at changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed CC| |w.schwarzenfeld@utanet.at Resolution|--- |Not A Bug --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Mar 7 06:04:12 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 26FEAF2F165 for ; Wed, 7 Mar 2018 06:04:12 +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 990327FBC9 for ; Wed, 7 Mar 2018 06:04:11 +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 D70CA1262A for ; Wed, 7 Mar 2018 06:04:10 +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 w2764AUC015353 for ; Wed, 7 Mar 2018 06:04:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2764AWX015352 for freebsd-fs@FreeBSD.org; Wed, 7 Mar 2018 06:04:10 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: freebsd-fs@FreeBSD.org Subject: [Bug 219972] Unable to zpool export following some zfs recv Date: Wed, 07 Mar 2018 06:04:10 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: dr_sweety_1337@hotmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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, 07 Mar 2018 06:04:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219972 dr_sweety_1337@hotmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dr_sweety_1337@hotmail.com --- Comment #9 from dr_sweety_1337@hotmail.com --- I ran into this bug as well with my backup script (which uses snapshots and import/export). My workaround: delete /boot/zfs/zpool.cache (make a backup first) and restart your system. Afterwards all pools (except for zroot) will have to be reimported but at least the locked pool is gone. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Mar 7 06:15: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 54B46F2F97C; Wed, 7 Mar 2018 06:15:27 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 EE9A58033C; Wed, 7 Mar 2018 06:15:26 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 052FA20DD9; Wed, 7 Mar 2018 01:15:26 -0500 (EST) Received: from web4 ([10.202.2.214]) by compute4.internal (MEProxy); Wed, 07 Mar 2018 01:15:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=U2sL02wso5H+LbA3Dv/bVTM9DbqX+LYxffds5XzKVHg=; b=mnzyhIPu gMVLlGYw2CMu1OcrOguFl0wvfhh8LUA9pXWwk4b0pTZn9RC7VAxk9XxYGxxOg9Ny wNuT3QCRHYc0xHkfMmNdEhiEHEWHZERegz39FlgK/0BOLub1RXv+hD3EVJICK0wv YU3kY8JueF6LfT60N/qa3LsmmUboZlk/iZb/ZlzE0NztyKIVs2OUDm1Twn3G7gcv vNvBGjBNh6s8iDcRWFx8vrdZbJ6RUvyxF4BkD4y2D+mUAEtwqTxCRtsN09jzIS9e 4dY1yNqp8OMb0bx4o4rlgXBUeF4uohlbUbYzoN5DxNlY7kBX3SIODTjiocpxhIzQ s2Czs7gSt6h4oQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=U2sL02wso5H+LbA3Dv/bVTM9DbqX+ LYxffds5XzKVHg=; b=e615j9CBRbvs/aIGiJxdVwjbZaXgCpyIR3ofaJqw7hYYn 4w2u1y6cTUfwIUi7fDYhharGTtvDCpWXkJQKITUiSx/1TC4VOxcmUYQ16h2YDm64 HCXPmxqIPFN+nAwbgjmwWGE7lhtKDTaX/g/UlklyspuPdp/CapAtnv8+sdCIH+5v dxz//2yYRgGTs0nuAnzKGlz1zOke4fkWh13178zKCaN20J2fahB2jyU5Sw5lhNxx xpQhWQToECMVrIMXsF+aOE+aRApjx7ru+55Dw6tuSfxl9FNHPg0yshwi4YFNSLgu JAOO1zGWX0TIA5oHBL3zeWWDoJIa+RAFwMTQTyXoQ== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id BDF30BA43B; Wed, 7 Mar 2018 01:15:25 -0500 (EST) Message-Id: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> From: John To: freebsd-current@freebsd.org Cc: freebsd-arm@freebsd.org, freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-54087d22 Subject: best settings for usb2 and attached disks, and sdcards Date: Wed, 07 Mar 2018 06:15:25 +0000 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, 07 Mar 2018 06:15:27 -0000 Hi, [cc'd to arm@ and fs@ where it's also relevant] I have a number of rpi3 & rpi3 machines. Usually I want to attach a usb keydrive to them so that the sdcard isn't thrashed. They're all running -current. usr/src and usr/ports at least are mounted on the keydrive. When initially updating eg the ports tree, svn will time out/crash because of the poor write performance of these devices in a rpi2/3 context. The fs on the usb keys is always ufs2. I have tried mounting these devices as -o async and also in fstab but this parameter seems not to 'take' in that mount doesn't report the async property set: [...] /dev/da0p2 on /ext (ufs, local, noatime, soft-updates) [...] was mounted with the command "mount -o async,noatime,rw /dev/da0s2 /ext" but I can't tell if async is on or just ignored, no error message. And I still have to run svnlite cleanup /ext/ports until svnlite stops bailing out. When newfs was written, I passed -t to it to enable trim, which seems to make a difference on this for deletes but not writes. Can anyone please suggest anything I can so to speed up disk i/o? And is async being applied or ignored? thanks, -- John tech-lists@zyxst.net From owner-freebsd-fs@freebsd.org Wed Mar 7 07:07:32 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 6B6F0F31F12 for ; Wed, 7 Mar 2018 07:07:32 +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 045E881E7D for ; Wed, 7 Mar 2018 07:07: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 4171612E92 for ; Wed, 7 Mar 2018 07:07: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 w2777Vb3027799 for ; Wed, 7 Mar 2018 07:07:31 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2777VLX027798 for freebsd-fs@FreeBSD.org; Wed, 7 Mar 2018 07:07: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: freebsd-fs@FreeBSD.org Subject: [Bug 219972] Unable to zpool export following some zfs recv Date: Wed, 07 Mar 2018 07:07: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: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: matthias.pfaller@familie-pfaller.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 07:07:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219972 --- Comment #10 from Matthias Pfaller = --- (In reply to dr_sweety_1337 from comment #9) Hmm. For me after a "geli detach -f ..." and a reboot did the trick. No mes= sing around with /boot/zfs/zpool.cache. Without the "geli detach -f ..." the reb= oot would hang. With the "geli detach -f ..." i can at least skip the power cyc= le. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Mar 7 08:25: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 1F2CDF39769 for ; Wed, 7 Mar 2018 08:25: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 AB5E58654F for ; Wed, 7 Mar 2018 08:25: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 D74DA1398D for ; Wed, 7 Mar 2018 08:24: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 w278Oxve035460 for ; Wed, 7 Mar 2018 08:24:59 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w278Ox94035459 for freebsd-fs@FreeBSD.org; Wed, 7 Mar 2018 08:24: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: freebsd-fs@FreeBSD.org Subject: [Bug 210409] zfs: panic during boot Date: Wed, 07 Mar 2018 08:24:59 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 08:25:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210409 --- Comment #11 from Andriy Gapon --- (In reply to Bryan Drewery from comment #10) This information does not tell anything particular... I think that the problem might correlate with ZFS restarting some pool acti= vity after a reboot (like processing async free list). --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Mar 7 13:50:28 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 C09AAF2DDCC for ; Wed, 7 Mar 2018 13:50:28 +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 579577475F for ; Wed, 7 Mar 2018 13:50:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 64443165D4 for ; Wed, 7 Mar 2018 13:50:27 +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 w27DoRcF075922 for ; Wed, 7 Mar 2018 13:50:27 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w27DoRoY075921 for freebsd-fs@FreeBSD.org; Wed, 7 Mar 2018 13:50:27 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 216886] ZFS with aclinherit and aclmode set to passthrough adds an extra default ACLs Date: Wed, 07 Mar 2018 13:50:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 13:50:29 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216886 --- Comment #3 from commit-hook@freebsd.org --- A commit references this bug: Author: avg Date: Wed Mar 7 13:49:27 UTC 2018 New revision: 330592 URL: https://svnweb.freebsd.org/changeset/base/330592 Log: MFV r330591: 8984 fix for 6764 breaks ACL inheritance illumos/illumos-gate@e9bacc6d1a71ea3f7082038b2868de8c4dd98bdc =20 https://github.com/illumos/illumos-gate/commit/e9bacc6d1a71ea3f7082038b2868= de8c4dd98bdc https://www.illumos.org/issues/8984 Consider a directory configured as: drwx-ws---+ 2 henson cpp 3 Jan 23 12:35 dropbox/ user:henson:rwxpdDaARWcC--:f-i----:allow owner@:--------------:f-i----:allow group@:--------------:f-i----:allow everyone@:--------------:f-i----:allow owner@:rwxpdDaARWcC--:-di----:allow group:cpp:-wx-----------:-------:allow owner@:rwxpdDaARWcC--:-------:allow A new file created in this directory ends up looking like: rw-r--r-+ 1 astudent cpp 0 Jan 23 12:39 testfile user:henson:rw-pdDaARWcC--:------I:allow owner@:--------------:------I:allow group@:--------------:------I:allow everyone@:--------------:------I:allow owner@:rw-p--aARWcCos:-------:allow group@:r-----a-R-c--s:-------:allow everyone@:r-----a-R-c--s:-------:allow with extraneous group@ and everyone@ entries allowing read access that shouldn't exist. Per Albert Lee on the zfs mailing list: "aclinherit=3Dpassthrough/passthrough-x should still ignore the requested mode when an inheritable ACE for owner@ group@, or everyone@ is present in the parent directory. It appears there was an oversight in my fix for https://www.illumos.org/issues/6764 which made calling zfs_acl_chmod from zfs_acl_inherit unconditional. I think the parent ACL check for aclinherit=3Dpassthrough needs to be reintroduced in zfs_acl_inherit." We have a large number of faculty who use dropbox directories like the example to have students submit projects. All of these directories are now allo= wing Reviewed by: Sam Zaydel Reviewed by: Paul B. Henson Reviewed by: Prakash Surya Approved by: Matthew Ahrens Author: Dominik Hassler PR: 216886 MFC after: 2 weeks Changes: _U head/sys/cddl/contrib/opensolaris/ head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_acl.c --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Mar 7 13:53:00 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 05288F2E305 for ; Wed, 7 Mar 2018 13:53:00 +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 94EE574B07 for ; Wed, 7 Mar 2018 13:52:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id C780E16723 for ; Wed, 7 Mar 2018 13:52:58 +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 w27DqwQE088777 for ; Wed, 7 Mar 2018 13:52:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w27Dqw9J088776 for freebsd-fs@FreeBSD.org; Wed, 7 Mar 2018 13:52:58 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: freebsd-fs@FreeBSD.org Subject: [Bug 216886] ZFS with aclinherit and aclmode set to passthrough adds an extra default ACLs Date: Wed, 07 Mar 2018 13:52:58 +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: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: avg@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2018 13:53:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216886 Andriy Gapon changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |In Progress Assignee|freebsd-fs@FreeBSD.org |avg@FreeBSD.org --- Comment #4 from Andriy Gapon --- Anyone having this problem, could you please test the commit from comment #3 and see if it actually fixes the problem on FreeBSD as well? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Wed Mar 7 17:16:36 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 C02C5F41A61 for ; Wed, 7 Mar 2018 17:16:36 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 1BE1181EBC for ; Wed, 7 Mar 2018 17:16:35 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-User: 35ee8aa1-222b-11e8-bb8e-b35b57339d60 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.ore.mailhop.org (Halon) with ESMTPSA id 35ee8aa1-222b-11e8-bb8e-b35b57339d60; Wed, 07 Mar 2018 17:16:02 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w27HGR9h002443; Wed, 7 Mar 2018 10:16:27 -0700 (MST) (envelope-from ian@freebsd.org) Message-ID: <1520442987.84937.12.camel@freebsd.org> Subject: Re: best settings for usb2 and attached disks, and sdcards From: Ian Lepore To: John , freebsd-current@freebsd.org Cc: freebsd-arm@freebsd.org, freebsd-fs@freebsd.org Date: Wed, 07 Mar 2018 10:16:27 -0700 In-Reply-To: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> References: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 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: Wed, 07 Mar 2018 17:16:36 -0000 On Wed, 2018-03-07 at 06:15 +0000, John wrote: > Hi, > [cc'd to arm@ and fs@ where it's also relevant] > > I have a number of rpi3 & rpi3 machines. Usually I want to attach a usb keydrive to them so that the sdcard isn't thrashed. They're all running -current. usr/src and usr/ports at least are mounted on the keydrive. > > When initially updating eg the ports tree, svn will time out/crash because of the poor write performance of these devices in a rpi2/3 context. The fs on the usb keys is always ufs2. I have tried mounting these devices as -o async and also in fstab but this parameter seems not to 'take' in that mount doesn't report the async property set: > > [...] > /dev/da0p2 on /ext (ufs, local, noatime, soft-updates) > [...] > > was mounted with the command "mount -o async,noatime,rw /dev/da0s2 /ext" > but I can't tell if async is on or just ignored, no error message. And I still have to run svnlite cleanup /ext/ports until svnlite stops bailing out. When newfs was written, I passed -t  to it to enable trim, which seems to make a difference on this for deletes but not writes. Can anyone please suggest anything I can so to speed up disk i/o? And is async being applied or ignored? > > thanks, If your ufs2 filesystem is formatted with soft dependencies, the async mount option does nothing (the ufs mount code forces it off when the softdeps flag is on).  Basically, softdeps IS async for ufs. If you have journaling enabled on the usb or sdcard filesystems, turn it off.  It just amplifies the writes to devices that are already very slow on writes, and the only benefit to journaling is that it speeds up fsck recovery.  Since sdcard and thumb drive filesystems tend to be very small already, the speed up from having journaling enabled amounts to a few seconds at best, and even that benefit only comes after a crash. -- Ian From owner-freebsd-fs@freebsd.org Wed Mar 7 17:43:38 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 CF410F44059; Wed, 7 Mar 2018 17:43:37 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 77A1183AB2; Wed, 7 Mar 2018 17:43:37 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id C32F320D4A; Wed, 7 Mar 2018 12:43:36 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 07 Mar 2018 12:43:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=6B2C3TIbVTffR3XnCzbOLfgGbejfPlXdHV7sEpjB34I=; b=RMnN0EXd wZWBvyq5v2xlTfOSpJGrOHXavvjVtsOgayuhV5KWpLtRvstbHzPz0qmNbId6b5cQ s1JnrZQ1kzyKMQgHm9F9qZmQINFsURIHZga7eMQm7HnICyvF2l+rlsRPwoJ41djl RitlPXwVC+NBNkC+SyhvAb5/1GYZTjt5V4XxiFD4V1/cq6T6A+puAH+Glrk2N9XJ aEx0DAOOzt5pYwKXKqYibXfTITgNWXsYKhpidcek4sVC7KKajjWScB0MGKICxhD8 2yM5rfewQuLDm3BolSDdOKWOpP7fRNudIqHV8ILAJK5/0tMQL2KuVptxsrJKdJRU bmfQEIyop5v05Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=6B2C3TIbVTffR3XnCzbOLfgGbejfP lXdHV7sEpjB34I=; b=GOV9wJr2NiXg1nFZ68wBFu9KyyZGuFGaKrgWkPrFBehXP LhF1kPRppFj99/Uz4HLAb/SXIqAgzgFxuK5nPyjQQl2kE7EaJC6wwh28QFQXfNqS 7+gX9QSeqg+/u2dEO7qnclWHieaHYUqU/wVfAMm4mXtmMDjDB/AX3d/oLTvD78WN Yf0WzkEUD4z3RToc55hS5ntdZwV3e2t+0iqczy+p9v+ACGTH7NiCHy/YyzFtA+hR xlZkopzgv9FAV776JnJtRaUqKtrHKzXCbCmCRLgvzNKCfC3V7B8wmPvYpnKVGTxY RLmmVh/4C1rnL7zdxIrrplygiMIUZNX0uYagpdxbw== X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 27C79246D5; Wed, 7 Mar 2018 12:43:36 -0500 (EST) To: freebsd-fs Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org From: tech-lists Subject: updating via svn and usb2 thumbdrives Message-ID: <5f3f4e06-c72f-0384-a428-823a30810368@zyxst.net> Date: Wed, 7 Mar 2018 17:43:35 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 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: Wed, 07 Mar 2018 17:43:38 -0000 Hi, When updating, particularly when downloading the src or ports tree for the first time, even though I've taken all approaches possible to speed up access to attached usb2 drives, I'll get these errors which will cause the update to bail: A ports/www/py-django-otp svn: E120106: ra_serf: The server sent a truncated HTTP response body. where it'll remain until I restart it but sometimes it'll crash so badly svn will demand svn cleanup on the dir I'm downloading to, like this: A ports/www/elgg/files svn: E120106: ra_serf: The server sent a truncated HTTP response body. # svnlite co https://svn0.eu.FreeBSD.org/ports/head /ext/ports svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) svn: E155004: Working copy '/ext/ports' locked. svn: E155004: '/ext/ports' is already locked. So I do this: # svnlite cleanup /ext/ports ...and I can start svnlite again. I'm sure this has to do with the thumbdrive 'catching up' with writing. So my question is this: Is there some switch in svnlite or some tool or parameter I can give to the process that will either buffer or limit the demands made of the device? It's UFS2 mounted with -o async[might be redundant],rw and has soft-updates but no journalling. My connection speed is 23Mbit so I'm thinking that on usb2 this might be approaching its random write speed but i'm unsure. What's the best way to permanently fix this? thanks, -- J. From owner-freebsd-fs@freebsd.org Wed Mar 7 18:05:06 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 A866DF45AD2; Wed, 7 Mar 2018 18:05:06 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 4F35C84BDC; Wed, 7 Mar 2018 18:05:06 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id B197620DC5; Wed, 7 Mar 2018 13:05:05 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Wed, 07 Mar 2018 13:05:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=bzrbeGB+9oxp3z8KHDw+8bsPTqB9x u64kHn2l7IK0oc=; b=gSa9oMyU0bzj/2nRvpDi7okBYshqIijHr8uXMVt4r57EI 4+OeNOA2TaaoAi+F3oCUhB/uaBVRT67G7X2lO9as3tat7BhJUB12Zf+n/vNz+a5z YdsbkozT5mJO/Hb3LbQXWtxkdIQ4Qb7/cpIICPYqaqvokEYclVxMqMmgeU44zjBx PeP+E/cROCsrYjmJz6BJxUZuHSmnQH7LfIcOG7Qy3Ex4e/zq36/ZIJhlBdoovEvE oGa16oEOMYm91jel12CcB5aA9Vt4wD7sXkvWs/jA1F188IpaUPp9c94ERtv7b8dK gKsPBbTLHzawsFsXhuMU8v4NHJMiBlMIpDuSc6a7w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=bzrbeG B+9oxp3z8KHDw+8bsPTqB9xu64kHn2l7IK0oc=; b=cCnypJMg3238Eo6KO0gio6 K0iwLYaxK1NAsxigkPDuVVOlbYrgu140KXlowdvYaJsL7gr3QUhYbAuItNuBmAkA v93P4+91RkDPe9WYpwo1lYohkkMONsXUhFTRzn/0OoqYgJtZZQ/sOJRVcdGqdMde 8WeH0Pge0uFxCVsp+rMCp6LR/33Xx7efcKa0DqCL2I26AZN7RmyKgDb+A5b/5f3R Z5ug2PBAYjiqj2qMYmez9FbmmkczZcIX3LIfB2pKZHhHzQ/hwHhLcAIkdnV88gvD wQdgM5rHw+We0DqNMximwagjZRtxKKPtDLVzHFlbKQ+nw4qhAUw6TKCVNRPsjolw == X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 0784E24505; Wed, 7 Mar 2018 13:05:04 -0500 (EST) Subject: Re: best settings for usb2 and attached disks, and sdcards To: Ian Lepore , freebsd-current@freebsd.org Cc: freebsd-arm@freebsd.org, freebsd-fs@freebsd.org References: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> <1520442987.84937.12.camel@freebsd.org> From: tech-lists Message-ID: Date: Wed, 7 Mar 2018 18:05:04 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1520442987.84937.12.camel@freebsd.org> Content-Type: text/plain; charset=utf-8 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: Wed, 07 Mar 2018 18:05:06 -0000 On 07/03/2018 17:16, Ian Lepore wrote: > If you have journaling enabled on the usb or sdcard filesystems, turn > it off. Yes, it's turned off. The new fs was made with newfs -U -n -t. I found later that the thumb drives didn't have TRIM functionality but didn't know for sure at the time (only found out when a notification popped up on the console that TRIM was switched on the filesystem but the disk didn't support it). thanks, -- J. From owner-freebsd-fs@freebsd.org Thu Mar 8 09:27:43 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 3F4A2F453E3 for ; Thu, 8 Mar 2018 09:27:43 +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 CE3DE7071B for ; Thu, 8 Mar 2018 09:27:42 +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 2111E209B5 for ; Thu, 8 Mar 2018 09:27:42 +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 w289RfCW058249 for ; Thu, 8 Mar 2018 09:27:41 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w289RfDH058248 for freebsd-fs@FreeBSD.org; Thu, 8 Mar 2018 09:27:41 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: freebsd-fs@FreeBSD.org Subject: [Bug 225663] FreeBSD 11.1-STABLE on root zfs panics on boot Date: Thu, 08 Mar 2018 09:27:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-STABLE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: dog@virtual.org.ua X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Mar 2018 09:27:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225663 --- Comment #2 from dog@virtual.org.ua --- Unfortunately I cannot catch the moment of panic (or maybe it's not even a panic, but some problem with zfs that causes my root zfs pool to collapse during the root mount). My system starts booting, loads kernel and all kernel modules ( I tried to remove all of them except of zfs from loader.conf, but it didn't help) and = then at the moment of mounting root zfs pool it momentarily shows some lines of error messages and PC immediately reboots. As far as my root zfs pool takes= the whole disk space I have no space for non-zfs kernel dumps and therefor ther= e's no any dumps saved. Nothing's written in logs too, because (as I understand= ) it happens before system can open any file to write. The reboot starts too fast and I cannot even make a photo of the screen to recognize what errors exact= ly happen. I tried to update the system to the most recent version from Mar 08 2018, but the problem still exists. Is there any way to make the system not reboot immediately after root zfs p= ool mounting error, but freeze and just show me the error until I press a key or something like that? Otherwise I'm not able to pick any additional informat= ion. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Mar 8 09:46: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 D46A8F4688C; Thu, 8 Mar 2018 09:46:52 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 36E0371396; Thu, 8 Mar 2018 09:46:51 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w289khtX001252 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 10:46:44 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w289kb0s007764 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 10:46:37 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w289kbvh084359 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 10:46:37 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w289ka53084358; Thu, 8 Mar 2018 10:46:36 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 10:46:36 +0100 From: Bernd Walter To: John Cc: freebsd-current@freebsd.org, freebsd-fs@freebsd.org, freebsd-arm@freebsd.org Subject: Re: best settings for usb2 and attached disks, and sdcards Message-ID: <20180308094636.GA80981@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de 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: Thu, 08 Mar 2018 09:46:53 -0000 On Wed, Mar 07, 2018 at 06:15:25AM +0000, John wrote: > Hi, > [cc'd to arm@ and fs@ where it's also relevant] > > I have a number of rpi3 & rpi3 machines. Usually I want to attach a usb keydrive to them so that the sdcard isn't thrashed. They're all running -current. usr/src and usr/ports at least are mounted on the keydrive. > > When initially updating eg the ports tree, svn will time out/crash because of the poor write performance of these devices in a rpi2/3 context. The fs on the usb keys is always ufs2. I have tried mounting these devices as -o async and also in fstab but this parameter seems not to 'take' in that mount doesn't report the async property set: I'm currently very pleased with the SanDisk Extreme Plus micro SD cards. They are quite expensive, but behave way better with random writes. Event better in random write performance are the SanDisk Extreme USB sticks. Also quite expensive though and quite big. I can't tell, however, if they are better in case of power loss related data corruption. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-fs@freebsd.org Thu Mar 8 10:06:30 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 0ABF4F481F5; Thu, 8 Mar 2018 10:06:30 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9EC46723A6; Thu, 8 Mar 2018 10:06:29 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1etsRK-0005to-2u; Thu, 08 Mar 2018 11:06:22 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-fs@freebsd.org, "freebsd-arm@freebsd.org" Date: Thu, 08 Mar 2018 11:06:23 +0100 Subject: gstat more writes per seconds than there are seconds per write MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 2ecd0b53b7de9511489f92806276a3d7 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: Thu, 08 Mar 2018 10:06:30 -0000 Hello, I'm confused by this output. w/s = 5, but ms/w is 1108; how can I put 5 writes in a second if the average write takes more than a second? Is my SD card super parallel? :-) Sometimes the numbers are even higher. dT: 1.010s w: 1.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0 0 0 0 0 0.0 0 0 0.0 0.0 da0 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s1 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0s2 0 0 0 0 0.0 0 0 0.0 0.0 msdosfs/MSDOSBOOT 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0s2a 17 5 0 0 0.0 5 420 1108 81.7 ufs/rootfs [root@rpi2 ~]# uname -a dmesg | grep mmc FreeBSD rpi2 11.1-RELEASE-p6 FreeBSD 11.1-RELEASE-p6 #0 r328567: Tue Jan 30 20:10:37 CET 2018 root@rpi2:/mnt/usbdisk/usr/obj/mnt/usbdisk/usr/src/sys/RPI2 arm [root@rpi2 ~]# dmesg | grep mmc mmc0: on sdhci_bcm0 mmc0: CMD8 failed, RESULT: 1 mmcsd0: 2GB at mmc0 41.6MHz/4bit/65535-block Regards, Ronald. From owner-freebsd-fs@freebsd.org Thu Mar 8 10:20: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 152B2F492E6; Thu, 8 Mar 2018 10:20:17 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C5B872C2F; Thu, 8 Mar 2018 10:20:16 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w28AKDPS001769 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 11:20:14 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w28AKBdp008201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 11:20:11 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w28AKAs0084498 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 11:20:10 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w28AKAR8084497; Thu, 8 Mar 2018 11:20:10 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 11:20:10 +0100 From: Bernd Walter To: Ronald Klop Cc: freebsd-fs@freebsd.org, "freebsd-arm@freebsd.org" Subject: Re: gstat more writes per seconds than there are seconds per write Message-ID: <20180308102010.GB80981@cicely7.cicely.de> Reply-To: ticso@cicely.de References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de 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: Thu, 08 Mar 2018 10:20:17 -0000 On Thu, Mar 08, 2018 at 11:06:23AM +0100, Ronald Klop wrote: > Hello, > > I'm confused by this output. > w/s = 5, but ms/w is 1108; how can I put 5 writes in a second if the > average write takes more than a second? It is the time a request has to wait until it is done. But your L(q) says that 17 are queued. > Is my SD card super parallel? :-) Maybe, maybe not, flash device vendors don't tell how they work internally, which is a shame, but you can only request a single transaction with an SD card. On USB sticks you might be able to do tagged command queuing, not that many support that... Nevertheless you can always queue more than one request at the OS layer. > Sometimes the numbers are even higher. > > dT: 1.010s w: 1.000s > L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name > 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0 > 0 0 0 0 0.0 0 0 0.0 0.0 da0 > 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s1 > 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0s2 > 0 0 0 0 0.0 0 0 0.0 0.0 msdosfs/MSDOSBOOT > 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0s2a > 17 5 0 0 0.0 5 420 1108 81.7 ufs/rootfs > > [root@rpi2 ~]# uname -a > dmesg | grep mmc > FreeBSD rpi2 11.1-RELEASE-p6 FreeBSD 11.1-RELEASE-p6 #0 r328567: Tue Jan > 30 20:10:37 CET 2018 > root@rpi2:/mnt/usbdisk/usr/obj/mnt/usbdisk/usr/src/sys/RPI2 arm > > [root@rpi2 ~]# dmesg | grep mmc > mmc0: on sdhci_bcm0 > mmc0: CMD8 failed, RESULT: 1 > mmcsd0: 2GB at mmc0 > 41.6MHz/4bit/65535-block > > Regards, > Ronald. > _______________________________________________ > freebsd-arm@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-fs@freebsd.org Thu Mar 8 10:42:36 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 178C0F4AE20; Thu, 8 Mar 2018 10:42:36 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A682173C40; Thu, 8 Mar 2018 10:42:35 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1ett0L-0000DB-Ms; Thu, 08 Mar 2018 11:42:34 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Bernd Walter" , ticso@cicely.de Cc: freebsd-fs@freebsd.org, "freebsd-arm@freebsd.org" Subject: Re: gstat more writes per seconds than there are seconds per write References: <20180308102010.GB80981@cicely7.cicely.de> Date: Thu, 08 Mar 2018 11:42:36 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <20180308102010.GB80981@cicely7.cicely.de> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 4cc6a862e0a753e674eb374334b394fd 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: Thu, 08 Mar 2018 10:42:36 -0000 On Thu, 08 Mar 2018 11:20:10 +0100, Bernd Walter wrote: > On Thu, Mar 08, 2018 at 11:06:23AM +0100, Ronald Klop wrote: >> Hello, >> >> I'm confused by this output. >> w/s = 5, but ms/w is 1108; how can I put 5 writes in a second if the >> average write takes more than a second? > > It is the time a request has to wait until it is done. > But your L(q) says that 17 are queued. Thanks, that makes sense. Any ideas how to retrieve the ms/w without the time-in-queue included? Regards, Ronald. > >> Is my SD card super parallel? :-) > > Maybe, maybe not, flash device vendors don't tell how they work > internally, which is a shame, but you can only request a single > transaction with an SD card. > On USB sticks you might be able to do tagged command queuing, > not that many support that... > Nevertheless you can always queue more than one request at the OS layer. > >> Sometimes the numbers are even higher. >> >> dT: 1.010s w: 1.000s >> L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name >> 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0 >> 0 0 0 0 0.0 0 0 0.0 0.0 da0 >> 0 0 0 0 0.0 0 0 0.0 0.0 mmcsd0s1 >> 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0s2 >> 0 0 0 0 0.0 0 0 0.0 0.0 >> msdosfs/MSDOSBOOT >> 17 5 0 0 0.0 5 420 1108 81.7 mmcsd0s2a >> 17 5 0 0 0.0 5 420 1108 81.7 ufs/rootfs >> >> [root@rpi2 ~]# uname -a >> dmesg | grep mmc >> FreeBSD rpi2 11.1-RELEASE-p6 FreeBSD 11.1-RELEASE-p6 #0 r328567: Tue Jan >> 30 20:10:37 CET 2018 >> root@rpi2:/mnt/usbdisk/usr/obj/mnt/usbdisk/usr/src/sys/RPI2 arm >> >> [root@rpi2 ~]# dmesg | grep mmc >> mmc0: on sdhci_bcm0 >> mmc0: CMD8 failed, RESULT: 1 >> mmcsd0: 2GB at mmc0 >> 41.6MHz/4bit/65535-block >> >> Regards, >> Ronald. >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-fs@freebsd.org Thu Mar 8 10:49:11 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 53739F4B50C; Thu, 8 Mar 2018 10:49:11 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E5A6E74033; Thu, 8 Mar 2018 10:49:10 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1ett6j-0002Ej-G7; Thu, 08 Mar 2018 11:49:09 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: vbox@freebsd.org, freebsd-fs@freebsd.org, "FreeBSD Current" Subject: Re: vboxvfs: Not a directory References: Date: Thu, 08 Mar 2018 11:49:12 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: a2d32f98be707cbcda8602d5fffa976a 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: Thu, 08 Mar 2018 10:49:11 -0000 Including the virtualbox port maintainer in the loop. Any thoughts? Ronald. On Sun, 04 Mar 2018 22:04:05 +0100, Ronald Klop wrote: > Hi, > > I'm trying to use vboxfs on # uname -a > FreeBSD sjakie 12.0-CURRENT FreeBSD 12.0-CURRENT #4 r329516M: Sun Feb 18 > 12:37:36 CET 2018 > ronald@sjakie:/data/ronald/obj-freebsd-current/data/ronald/freebsd-current/amd64.amd64/sys/GENERIC-NODEBUG > amd64 > > I run VirtualBox on Windows 10 using FreeBSD 12 as a guest. > virtualbox-ose-additions-5.2.8 is installed by pkg. > I configured C:\Temp as 'win' in VirtualBox. > > Modules are loaded: > kldstat | grep vbox > 5 2 0xffffffff82e26000 2d9e0 vboxguest.ko > 13 1 0xffffffff82e7e000 1f320 vboxvfs.ko > > [root@sjakie ~]# mount_vboxvfs win /mnt/win > [root@sjakie ~]# ls /mnt/win/ > ls: /mnt/win/: Not a directory > > I tried different Windows directories and different users/rights on the > /mnt/win directory. > Am I doing something wrong? > I can't find a lot documentation about vboxvfs. > > Regards, > Ronald. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-fs@freebsd.org Thu Mar 8 13:54:04 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 BC1A6F3383F for ; Thu, 8 Mar 2018 13:54:04 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-ua0-x230.google.com (mail-ua0-x230.google.com [IPv6:2607:f8b0:400c:c08::230]) (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 183397B84C for ; Thu, 8 Mar 2018 13:54:04 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-ua0-x230.google.com with SMTP id f6so3965949ual.0 for ; Thu, 08 Mar 2018 05:54:04 -0800 (PST) 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=A4IlQeuqiYsDQ4SAUvSOxD4U847D4YvgodIGA6E77gc=; b=smrDQu7q4JkTiTK54v4KdayvKzMgcaLx0lbL4YfGYlY1KkgBF4WJfAFIENAuyN4CzQ qofKxkRddRdp9r3wGCDLwmUuFfCRXlaLdXn4+0hJH6lIscotp6ufVpJd1nxy4/4lWZml fD/vLXsPAhBbSYdWlXQ+DvRHMzdjGjDCTJNE7mgkR/YyEdhE8ZG2fAHEkPJ9Xi3CRB3K e6gN7kvl+4d9iKeNrvOlVGULxz+YmvWAnKAlXIVZa6w8KZePi/TJDhIL1JkgTCgXOA8G xIBVhfJp4Mm3963I0zk7K5JbEN3iwh0gIr9IUwrhtP+4TqC4S/wa1nK9pfLHqF0JRAyt bw5w== 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=A4IlQeuqiYsDQ4SAUvSOxD4U847D4YvgodIGA6E77gc=; b=VL5P3GSYcRGPqzrDyAlfiqF2sCWilZ4jdHAo0JpRL/8xramv8+kmbM3RZfQkiLTWxH Ta2oeyfDe4FLa5Pfv5O3yUhNmrr1P3ZHEDxBfMGHtZUAhFKmWnb5iDTzZF7n6Yhg0OIn i8CSQOyhI5wK5mLvgItaOxCxz9Kx//CCL83jJMruJQ5uIo48nzF1l2VU2h/PTaMgI4WB Aw9qvURtbQjTn/5Kg3Q36gZqR1ix++KdLMc7K/EV6/275MKeQRj3UVo3PRQcTmdJ0MwX ASepTw9ZgVt5uhCn1fMyN3j25qpubrbcRet+NXjel3ouDf1rnG3yyQK85v+XuOf8EWsv f3dw== X-Gm-Message-State: APf1xPDTZLx2ygWIRS5TdEQaNO+xN10hB/tlkk7PdhqGPy9Tm8XkhYvy RIsc5HzECaUmVtYP8riWwFLj5SZWapehskx11NY= X-Google-Smtp-Source: AG47ELu2yP0uDJM3HY9s8/trMNgFRSq+EpbSXy5XuNvfDqEygAdLT1SLIpN+sjH9qmG4gD2e8UwS0h6BZwp9kBAjfcc= X-Received: by 10.176.24.161 with SMTP id t33mr19577386uag.198.1520517243505; Thu, 08 Mar 2018 05:54:03 -0800 (PST) MIME-Version: 1.0 Sender: etnapierala@gmail.com Received: by 10.176.7.2 with HTTP; Thu, 8 Mar 2018 05:54:03 -0800 (PST) In-Reply-To: References: <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> <5A9A4B1E.8070206@anarchy.in.the.ph> <20180303113306.GB2029@brick> From: Edward Napierala Date: Thu, 8 Mar 2018 13:54:03 +0000 X-Google-Sender-Auth: cj0rPg62bAGGl7Dvy-Ike4BFAdo Message-ID: Subject: Re: growfs only works on GPT partitioning schemes? To: Mars G Miro Cc: Warner Losh , Martin Simmons , FreeBSD FS 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: Thu, 08 Mar 2018 13:54:05 -0000 2018-03-03 15:29 GMT+00:00 Mars G Miro : > On Sat, Mar 3, 2018 at 7:33 PM, Edward Tomasz Napiera=C5=82a > wrote: > >> On 0303T1513, Mars G. Miro wrote: >> > On 02/26/18 22:30, Warner Losh wrote: >> > > >> > > On Mon, Feb 26, 2018 at 7:11 AM, Martin Simmons > > > > wrote: >> > > >> > > >>>>> On Mon, 26 Feb 2018 11:55:10 +0800, Mars G Miro said: >> > > > >> > > > It seems that growfs only works on GPT partitioned schemes = ? >> > > > >> > > > When I first installed my FreeBSD, I unfortunately chose BS= D >> during the >> > > > FS creation. Now that I ran out of space, I wanted to increase >> the >> > > > filesystem size. Successfully did so in Virtualbox but after >> rebooting, the >> > > > HD doesn't see the new allocated space. It has another virtual >> HD, one >> > > > created with GPT and I was able to increase it via growfs. >> > > >> > > For the BSD scheme, I think you also have to resize the slice >> (i.e. >> > > the MBR >> > > entry) and then resize the BSD partition within the slice. >> > > >> > > >> > > You do. The /etc/rc.d script that does resize on boot does that >> > > automatically, but we have no other automation for the process. >> > > >> > > Warner >> > >> > You guys have any idea how to resize the slice ? >> > >> > I have 2 HDs, both have already been increased (in VirtualBox). The BS= D >> > partitioned scheme below doesn't see the newly allocated disk space, >> > only the GPT one. >> > >> > camcontrol reprobe / gpart recover / etc doesn't do anything. >> > >> > mars@fbsd11vm1:~ % gpart show >> > =3D> 0 83886080 ada0 BSD (40G) >> > 0 4194304 1 freebsd-ufs (2.0G) >> > 4194304 16777216 2 freebsd-ufs (8.0G) >> > 20971520 62914559 4 freebsd-ufs (30G) >> > 83886079 1 - free - (512B) >> > >> > =3D> 40 104857520 ada1 GPT (60G) [CORRUPT] >> > 40 12582912 1 freebsd-swap (6.0G) >> > 12582952 92274608 2 freebsd-ufs (44G) >> >> What does "geom disk list" show? >> >> > > Supposedly the first drive should already have been 80Gb but: > > mars@fbsd11vm1:~ % geom disk list > ... > Geom name: ada0 > Providers: > 1. Name: ada0 > Mediasize: 42949672960 (40G) > Sectorsize: 512 > Mode: r3w3e6 > descr: VBOX HARDDISK > ident: VB1e5e1cab-a4c47c87 > rotationrate: 0 > fwsectors: 63 > fwheads: 16 > > Geom name: ada1 > Providers: > 1. Name: ada1 > Mediasize: 64424509440 (60G) > Sectorsize: 512 > Mode: r2w2e3 > descr: VBOX HARDDISK > ident: VBef5bd266-afbdd2b4 > rotationrate: 0 > fwsectors: 63 > fwheads: 16 > Okay, so this explains why you can't resize the partition: it's not the partitioning scheme, but the actual device size. Does a reboot make "geom disk list" show expected sizes? If not, what does a "dmesg | grep ada" show? From owner-freebsd-fs@freebsd.org Thu Mar 8 14:37:03 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 A9C9EF370BC for ; Thu, 8 Mar 2018 14:37:03 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from lwfs1-cam.cam.lispworks.com (mail.lispworks.com [46.17.166.21]) by mx1.freebsd.org (Postfix) with ESMTP id 3E3FF7D3EE for ; Thu, 8 Mar 2018 14:37:02 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (higson.cam.lispworks.com [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.15.2/8.15.2) with ESMTP id w28EQNxM031590; Thu, 8 Mar 2018 14:26:23 GMT (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (localhost.localdomain [127.0.0.1]) by higson.cam.lispworks.com (8.14.4) id w28EQNXn003602; Thu, 8 Mar 2018 14:26:23 GMT Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id w28EQNE6003598; Thu, 8 Mar 2018 14:26:23 GMT Date: Thu, 8 Mar 2018 14:26:23 GMT Message-Id: <201803081426.w28EQNE6003598@higson.cam.lispworks.com> From: Martin Simmons To: Mars G Miro CC: Warner Losh , freebsd-fs@freebsd.org In-reply-to: (message from Edward Napierala on Thu, 8 Mar 2018 13:54:03 +0000) Subject: Re: growfs only works on GPT partitioning schemes? References: <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> <5A9A4B1E.8070206@anarchy.in.the.ph> <20180303113306.GB2029@brick> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 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: Thu, 08 Mar 2018 14:37:04 -0000 >>>>> On Thu, 8 Mar 2018 13:54:03 +0000, Edward Napierala said: > > 2018-03-03 15:29 GMT+00:00 Mars G Miro : > > > On Sat, Mar 3, 2018 at 7:33 PM, Edward Tomasz NapieraƂa > > wrote: > > > >> On 0303T1513, Mars G. Miro wrote: > >> > On 02/26/18 22:30, Warner Losh wrote: > >> > > > >> > > On Mon, Feb 26, 2018 at 7:11 AM, Martin Simmons >> > > > wrote: > >> > > > >> > > >>>>> On Mon, 26 Feb 2018 11:55:10 +0800, Mars G Miro said: > >> > > > > >> > > > It seems that growfs only works on GPT partitioned schemes ? > >> > > > > >> > > > When I first installed my FreeBSD, I unfortunately chose BSD > >> during the > >> > > > FS creation. Now that I ran out of space, I wanted to increase > >> the > >> > > > filesystem size. Successfully did so in Virtualbox but after > >> rebooting, the > >> > > > HD doesn't see the new allocated space. It has another virtual > >> HD, one > >> > > > created with GPT and I was able to increase it via growfs. > >> > > > >> > > For the BSD scheme, I think you also have to resize the slice > >> (i.e. > >> > > the MBR > >> > > entry) and then resize the BSD partition within the slice. > >> > > > >> > > > >> > > You do. The /etc/rc.d script that does resize on boot does that > >> > > automatically, but we have no other automation for the process. > >> > > > >> > > Warner > >> > > >> > You guys have any idea how to resize the slice ? > >> > > >> > I have 2 HDs, both have already been increased (in VirtualBox). The BSD > >> > partitioned scheme below doesn't see the newly allocated disk space, > >> > only the GPT one. > >> > > >> > camcontrol reprobe / gpart recover / etc doesn't do anything. > >> > > >> > mars@fbsd11vm1:~ % gpart show > >> > => 0 83886080 ada0 BSD (40G) > >> > 0 4194304 1 freebsd-ufs (2.0G) > >> > 4194304 16777216 2 freebsd-ufs (8.0G) > >> > 20971520 62914559 4 freebsd-ufs (30G) > >> > 83886079 1 - free - (512B) > >> > > >> > => 40 104857520 ada1 GPT (60G) [CORRUPT] > >> > 40 12582912 1 freebsd-swap (6.0G) > >> > 12582952 92274608 2 freebsd-ufs (44G) > >> > >> What does "geom disk list" show? > >> > >> > > > > Supposedly the first drive should already have been 80Gb but: > > > > mars@fbsd11vm1:~ % geom disk list > > ... > > Geom name: ada0 > > Providers: > > 1. Name: ada0 > > Mediasize: 42949672960 (40G) > > Sectorsize: 512 > > Mode: r3w3e6 > > descr: VBOX HARDDISK > > ident: VB1e5e1cab-a4c47c87 > > rotationrate: 0 > > fwsectors: 63 > > fwheads: 16 > > > > Geom name: ada1 > > Providers: > > 1. Name: ada1 > > Mediasize: 64424509440 (60G) > > Sectorsize: 512 > > Mode: r2w2e3 > > descr: VBOX HARDDISK > > ident: VBef5bd266-afbdd2b4 > > rotationrate: 0 > > fwsectors: 63 > > fwheads: 16 > > > > Okay, so this explains why you can't resize the partition: it's not > the partitioning scheme, but the actual device size. > > Does a reboot make "geom disk list" show expected sizes? If not, > what does a "dmesg | grep ada" show? Also, check the size using "vboxmanage showhdinfo" on the host and check that the virtual disk doesn't have any vbox snapshots. __Martin From owner-freebsd-fs@freebsd.org Thu Mar 8 15:26:20 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 56EB0F3B405; Thu, 8 Mar 2018 15:26:20 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C5C3A7F4D8; Thu, 8 Mar 2018 15:26:19 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w28FQCpG061089 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 07:26:13 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w28FQBp1061088; Thu, 8 Mar 2018 07:26:11 -0800 (PST) (envelope-from fbsd) Date: Thu, 8 Mar 2018 07:26:11 -0800 From: bob prohaska To: ticso@cicely.de Cc: John , freebsd-fs@freebsd.org, freebsd-arm@freebsd.org, freebsd-current@freebsd.org, bob prohaska Subject: Re: best settings for usb2 and attached disks, and sdcards Message-ID: <20180308152611.GA61027@www.zefox.net> References: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> <20180308094636.GA80981@cicely7.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308094636.GA80981@cicely7.cicely.de> User-Agent: Mutt/1.5.24 (2015-08-30) 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: Thu, 08 Mar 2018 15:26:20 -0000 On Thu, Mar 08, 2018 at 10:46:36AM +0100, Bernd Walter wrote: > > I'm currently very pleased with the SanDisk Extreme Plus micro SD > cards. > They are quite expensive, but behave way better with random writes. > I don't think I've seen Sandisk Extreme Plus devices, how do they differ from "ordinary" Sandisk extreme devices? I think there is a "Pro" version, is that the same thing? > Event better in random write performance are the SanDisk Extreme > USB sticks. > Also quite expensive though and quite big. > Likewise, my experiece, spread over 4 RPi2's and 2 RPi3's, has been good. > I can't tell, however, if they are better in case of power loss > related data corruption. > Never done a systematic test, but accidental unplugs and power cycles after a crash have never caused problems fsck -f won't fix. hth, bob prohaska From owner-freebsd-fs@freebsd.org Thu Mar 8 16:02: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 A2A7BF3ECCB; Thu, 8 Mar 2018 16:02:51 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [IPv6:2a02:21e0:16e0:fe::101:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "raven.bwct.de", Issuer "raven.bwct.de" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 33CB78229C; Thu, 8 Mar 2018 16:02:51 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.15.2/8.15.2) with ESMTPS id w28G2lvR007513 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 17:02:47 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id w28G2djo012490 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 8 Mar 2018 17:02:39 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.15.2/8.15.2) with ESMTPS id w28G2dkl085959 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 8 Mar 2018 17:02:39 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.15.2/8.15.2/Submit) id w28G2c4j085958; Thu, 8 Mar 2018 17:02:38 +0100 (CET) (envelope-from ticso) Date: Thu, 8 Mar 2018 17:02:38 +0100 From: Bernd Walter To: bob prohaska Cc: ticso@cicely.de, freebsd-fs@freebsd.org, freebsd-arm@freebsd.org, freebsd-current@freebsd.org Subject: Re: best settings for usb2 and attached disks, and sdcards Message-ID: <20180308160238.GD80981@cicely7.cicely.de> Reply-To: ticso@cicely.de References: <1520403325.3513270.1294320744.0B1DE142@webmail.messagingengine.com> <20180308094636.GA80981@cicely7.cicely.de> <20180308152611.GA61027@www.zefox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180308152611.GA61027@www.zefox.net> X-Operating-System: FreeBSD cicely7.cicely.de 11.0-STABLE amd64 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de 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: Thu, 08 Mar 2018 16:02:51 -0000 On Thu, Mar 08, 2018 at 07:26:11AM -0800, bob prohaska wrote: > On Thu, Mar 08, 2018 at 10:46:36AM +0100, Bernd Walter wrote: > > > > I'm currently very pleased with the SanDisk Extreme Plus micro SD > > cards. > > They are quite expensive, but behave way better with random writes. > > > I don't think I've seen Sandisk Extreme Plus devices, how do they differ > from "ordinary" Sandisk extreme devices? I think there is a "Pro" version, > is that the same thing? I don't know any other SanDisk Extreme SD cards than the Extreme Plus I have. The Ultra, I usually use, have those typical long delay problems, while the Extreme Plus never showed up in gstat with more than 100ms absolute worst case, usually below 25ms under random write load with 4-8MB/s datarate. Those I have are labeled as SDSQXBG-032G-GN6MA. > > Event better in random write performance are the SanDisk Extreme > > USB sticks. > > Also quite expensive though and quite big. > > > Likewise, my experiece, spread over 4 RPi2's and 2 RPi3's, has been good. > > > I can't tell, however, if they are better in case of power loss > > related data corruption. > > > > Never done a systematic test, but accidental unplugs and power cycles > after a crash have never caused problems fsck -f won't fix. I've had those problems with any kind of card I've used. This even happened for me with fully readonly mounted cards. Cards have to do ocassional refresh writes for reads, which means at low level there's no such thing as read-only, but it is amazing that customers even mange to catch those. The Extreme Plus however are new for me and I can't tell yet. At least they are way better during development. So far I've went to NFS, but NFS has a higher latency and 100MBit ethernet is slower than local cards could deliver. -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-fs@freebsd.org Thu Mar 8 21:29:53 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 81B55F32291 for ; Thu, 8 Mar 2018 21:29:53 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E5FC0716B6 for ; Thu, 8 Mar 2018 21:29:52 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id w128so464893wmw.0 for ; Thu, 08 Mar 2018 13:29:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=k1pZmw6lFx1Hit+KPauq7bYMYRUWvTHevlTDQfJ/dMk=; b=ZegQtsVXwbJ/RLOHLpfmdfrhMwalIYulsvVbq2GUfvU5MkWi7AQUmD7pXpZRLUHUo4 nTwFLlX++KbQwVSiSKIX7V+DO4XCJGxJBn+MrzjyNTjkb33yoZINmCoGc5uskO8Tmpqv qTr8UNP+sgn+TsA2PDuwnGzJvI2EfFGrzxuHSXh2s70EOsEHwUx82jJg3qagS+oWjEvT Y2Oo16oDeexYXw3c0+OvR4XQKnjXkbBTv/k1QeGa+2DJFVW5lgRpgaxhYeab8C84gf4i ybmhm4k/L0Ad4wyk6WQqsWWG5cCemVXmtKx+MSXpFLeXNiPDW7jCWk844pG3MAUZ11Lt 2TDA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=k1pZmw6lFx1Hit+KPauq7bYMYRUWvTHevlTDQfJ/dMk=; b=pDh43R4jGgX4q5sE7q3RbetxFGe4qcPMzpGhcID1Rw/MIWJfJo0exbsBewEJ/x827A rSMeVZUPl6bICQsYoazJi929FvFe3Ad2To1ry6/x/WXU4750dYDYQbgYrvVCdXMPNUR1 Fsx1ck5MIxvaVNpl0xkk+2mmlWivWdcl7OTYXz4vDa+n4KK7bW3SULmn26LDJ3KHt+gq ae9NLzWIushT6wi7PicJh7Q+fJk09zDT73Fu7xxDb3nyu54scHF3p3PrQahL82mbPEtv A4BoxmxT68nMA1uPOhywBx1rQ+pCMJik1Ld97lro8ohi/Br7wfYDDmAL+wCrCmNMP3XL XeUQ== X-Gm-Message-State: AElRT7HJjKIUzhl/6zWz7cP5WaJeKa7R/adBVe2t2b7cx9ozaTbAOFZj g+8jnVnOnct59vPwDg3G/OnhBRXX X-Google-Smtp-Source: AG47ELvXEmSCo8vKND5LrpmGCh8kiqBRmnsnr4SilXtFp7kpy4yXcFQLAjo9kWf3b3sTzQbNfolDdQ== X-Received: by 10.28.125.150 with SMTP id y144mr174446wmc.75.1520544591032; Thu, 08 Mar 2018 13:29:51 -0800 (PST) Received: from bens-mac-1.home (LFbn-NIC-1-211-113.w2-15.abo.wanadoo.fr. [2.15.58.113]) by smtp.gmail.com with ESMTPSA id y23sm22591754wra.9.2018.03.08.13.29.50 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 08 Mar 2018 13:29:50 -0800 (PST) From: Ben RUBSON Content-Type: text/plain; charset=us-ascii; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit Subject: Fuse jail-friendly Message-Id: <8C80C2ED-0021-4BB6-86BB-A7C9BA06E1E7@gmail.com> Date: Thu, 8 Mar 2018 22:29:50 +0100 To: Freebsd fs Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) 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: Thu, 08 Mar 2018 21:29:53 -0000 Hi, Is there any reason why fuse is not jail-friendly ? Many thanks ! Ben From owner-freebsd-fs@freebsd.org Fri Mar 9 07:03:08 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 24320F32102 for ; Fri, 9 Mar 2018 07:03:08 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B9F988768F for ; Fri, 9 Mar 2018 07:03:07 +0000 (UTC) (envelope-from spry@anarchy.in.the.ph) Received: by mail-qt0-x234.google.com with SMTP id m13so9653453qtg.13 for ; Thu, 08 Mar 2018 23:03:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarchy-in-the-ph.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XGCregocTVWpMgy0YaxjSDC7fuEOmPxDJp0SxgrENzI=; b=gVqIczIoWn6nZURA3ai5getZo3Y4HUuNzcXiBnI6nSOQiHzI4N3CKEKuj0OlVQNhCe wD7zta2oCAgq3v+X0Pip8EByBp/PGL3vnfljwQhyLLIQilkw7ZL7a4rT3otqiZ4Skwnj 0RAAJ1IiIlq8eizbzD6PjZlILhPk6yRzO4m0BQpzLYhzfHITleYpnR7FnMm1UJSev7tu 2Msrey/0pCRXN8dwqyzFWxAQNlHdNdnFgFD3Yi7aHt9knaAmwcGPdSBnaS6rVwFqwY7N nAJjWPUtv/nU9tQe9GZMh1aRYo223mWBepp8jUeZ9ZtCMZt5RqDFJzn6MUyqWvU90ZxG e39g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XGCregocTVWpMgy0YaxjSDC7fuEOmPxDJp0SxgrENzI=; b=LSHaJnOc3plOZg4t2QtnsHqbXj4Pb2B86uhOjZPTEEJM/vAN+bxzuhtyZ8ku4WkbwO BaP16+xsaCZngdWryyKYZAO8A4FPWNg8/4F0DngbDhBmLyiZ2EnIo8+3Yl2d7ESw3Qa3 BCuz7dML32qyxbKcyHdmDH2iWaF6tm106U9sXyjTyyZV7mUq2CGTuUGY0gl3iFOAuDpi 2iTQoPA2CD2tcYjIT8LVcCQRSZ4d/xbQvVfLE9W0GEicDpUllvyNYTpqSwbyskyflxPX WGB7zsKIvqdDoTqoGhOBmeSerO+NrBp9BC5Yl3+TPk6lw+6fw8MwTWE+JpVgen0vFi17 jU+Q== X-Gm-Message-State: AElRT7ErCJQdjdhsf8KwKztAQ9k5mIRnXjFiucYdRUPCoEioSDXJ3OHY 8JBQqpqPD1Fd/8dlFoR6yzDR4ulwO2OF1amF7WIhFA== X-Google-Smtp-Source: AG47ELseNB4P6vHOHVNfztLvT17tQJyU+hU/pMh80/YQSupn/VcME9pLBNppKHhRQ0Bb7K5eH2T1IDuQD/bow5neD2M= X-Received: by 10.200.10.3 with SMTP id b3mr43251985qti.236.1520578987060; Thu, 08 Mar 2018 23:03:07 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.149.120 with HTTP; Thu, 8 Mar 2018 23:03:06 -0800 (PST) In-Reply-To: <201803081426.w28EQNE6003598@higson.cam.lispworks.com> References: <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> <5A9A4B1E.8070206@anarchy.in.the.ph> <20180303113306.GB2029@brick> <201803081426.w28EQNE6003598@higson.cam.lispworks.com> From: Mars G Miro Date: Fri, 9 Mar 2018 15:03:06 +0800 Message-ID: Subject: Re: growfs only works on GPT partitioning schemes? To: Martin Simmons , =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Cc: Warner Losh , FreeBSD FS 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: Fri, 09 Mar 2018 07:03:08 -0000 On Thu, Mar 8, 2018 at 10:26 PM, Martin Simmons wrote: > >>>>> On Thu, 8 Mar 2018 13:54:03 +0000, Edward Napierala said: > > > > 2018-03-03 15:29 GMT+00:00 Mars G Miro : > > > > > On Sat, Mar 3, 2018 at 7:33 PM, Edward Tomasz Napiera=C5=82a < > trasz@freebsd.org > > > > wrote: > > > > > >> On 0303T1513, Mars G. Miro wrote: > > >> > On 02/26/18 22:30, Warner Losh wrote: > > >> > > > > >> > > On Mon, Feb 26, 2018 at 7:11 AM, Martin Simmons < > martin@lispworks.com > > >> > > > wrote: > > >> > > > > >> > > >>>>> On Mon, 26 Feb 2018 11:55:10 +0800, Mars G Miro said: > > >> > > > > > >> > > > It seems that growfs only works on GPT partitioned > schemes ? > > >> > > > > > >> > > > When I first installed my FreeBSD, I unfortunately chos= e > BSD > > >> during the > > >> > > > FS creation. Now that I ran out of space, I wanted to > increase > > >> the > > >> > > > filesystem size. Successfully did so in Virtualbox but aft= er > > >> rebooting, the > > >> > > > HD doesn't see the new allocated space. It has another > virtual > > >> HD, one > > >> > > > created with GPT and I was able to increase it via growfs. > > >> > > > > >> > > For the BSD scheme, I think you also have to resize the slic= e > > >> (i.e. > > >> > > the MBR > > >> > > entry) and then resize the BSD partition within the slice. > > >> > > > > >> > > > > >> > > You do. The /etc/rc.d script that does resize on boot does that > > >> > > automatically, but we have no other automation for the process. > > >> > > > > >> > > Warner > > >> > > > >> > You guys have any idea how to resize the slice ? > > >> > > > >> > I have 2 HDs, both have already been increased (in VirtualBox). Th= e > BSD > > >> > partitioned scheme below doesn't see the newly allocated disk spac= e, > > >> > only the GPT one. > > >> > > > >> > camcontrol reprobe / gpart recover / etc doesn't do anything. > > >> > > > >> > mars@fbsd11vm1:~ % gpart show > > >> > =3D> 0 83886080 ada0 BSD (40G) > > >> > 0 4194304 1 freebsd-ufs (2.0G) > > >> > 4194304 16777216 2 freebsd-ufs (8.0G) > > >> > 20971520 62914559 4 freebsd-ufs (30G) > > >> > 83886079 1 - free - (512B) > > >> > > > >> > =3D> 40 104857520 ada1 GPT (60G) [CORRUPT] > > >> > 40 12582912 1 freebsd-swap (6.0G) > > >> > 12582952 92274608 2 freebsd-ufs (44G) > > >> > > >> What does "geom disk list" show? > > >> > > >> > > > > > > Supposedly the first drive should already have been 80Gb but: > > > > > > mars@fbsd11vm1:~ % geom disk list > > > ... > > > Geom name: ada0 > > > Providers: > > > 1. Name: ada0 > > > Mediasize: 42949672960 (40G) > > > Sectorsize: 512 > > > Mode: r3w3e6 > > > descr: VBOX HARDDISK > > > ident: VB1e5e1cab-a4c47c87 > > > rotationrate: 0 > > > fwsectors: 63 > > > fwheads: 16 > > > > > > Geom name: ada1 > > > Providers: > > > 1. Name: ada1 > > > Mediasize: 64424509440 (60G) > > > Sectorsize: 512 > > > Mode: r2w2e3 > > > descr: VBOX HARDDISK > > > ident: VBef5bd266-afbdd2b4 > > > rotationrate: 0 > > > fwsectors: 63 > > > fwheads: 16 > > > > > > > Okay, so this explains why you can't resize the partition: it's not > > the partitioning scheme, but the actual device size. > > > The actual size is already increased in Virtualbox but the FreeBSD BSD partitioned HD does not see it. The second GPT partitioned HD did not have problems (I was able to growfs it). > > Does a reboot make "geom disk list" show expected sizes? If not, > > what does a "dmesg | grep ada" show? > > I've rebooted it many times. See more below. > Also, check the size using "vboxmanage showhdinfo" on the host and check > that > the virtual disk doesn't have any vbox snapshots. > > __Martin > It does have 2 snapshots in fact, this is a known problem ? root@fbsd11z51vm1:~ # gpart list Geom name: ada0 modified: false state: OK fwheads: 16 fwsectors: 63 last: 83886079 first: 0 entries: 8 scheme: BSD Providers: 1. Name: ada0a Mediasize: 2147483648 (2.0G) Sectorsize: 512 Mode: r1w1e1 rawtype: 7 length: 2147483648 offset: 0 type: freebsd-ufs index: 1 end: 4194303 start: 0 2. Name: ada0b Mediasize: 8589934592 (8.0G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 2147483648 Mode: r1w1e1 rawtype: 7 length: 8589934592 offset: 2147483648 type: freebsd-ufs index: 2 end: 20971519 start: 4194304 3. Name: ada0d Mediasize: 32212254720 (30G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 2147483648 Mode: r1w1e1 rawtype: 7 length: 32212254720 offset: 10737418240 type: freebsd-ufs index: 4 end: 83886079 start: 20971520 Consumers: 1. Name: ada0 Mediasize: 42949672960 (40G) Sectorsize: 512 Mode: r3w3e6 Geom name: ada1 modified: false state: OK fwheads: 16 fwsectors: 63 last: 125829079 first: 40 entries: 152 scheme: GPT Providers: 1. Name: ada1p1 Mediasize: 6442450944 (6.0G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 20480 Mode: r1w1e0 rawuuid: 1a11b419-f839-11e7-9145-080027d107ad rawtype: 516e7cb5-6ecf-11d6-8ff8-00022d09712b label: (null) length: 6442450944 offset: 20480 type: freebsd-swap index: 1 end: 12582951 start: 40 2. Name: ada1p2 Mediasize: 57982017536 (54G) Sectorsize: 512 Stripesize: 0 Stripeoffset: 2147504128 Mode: r1w1e1 rawuuid: 288ccc2c-f839-11e7-9145-080027d107ad rawtype: 516e7cb6-6ecf-11d6-8ff8-00022d09712b label: (null) length: 57982017536 offset: 6442471424 type: freebsd-ufs index: 2 end: 125829079 start: 12582952 Consumers: 1. Name: ada1 Mediasize: 64424509440 (60G) Sectorsize: 512 Mode: r2w2e3 root@fbsd11z51vm1:~ # dmesg -a | grep ^ada ada0 at ata0 bus 0 scbus0 target 0 lun 0 ada0: cd0: ATA8-ACS device ada0: Serial Number VB1e5e1cab-a4c47c87 ada0: 16.700MB/s transferscd0: 16.700MB/s transfers ( (WDMA2, ATAPI 12bytes, PIO 65534bytes)WDMA2, ada0: 40960MB (83886080 512 byte sectors) ada1 at ata0 bus 0 scbus0 target 1 lun 0 ada1: ATA8-ACS device ada1: Serial Number VBef5bd266-afbdd2b4 ada1: 16.700MB/s transfers (WDMA2, PIO 65536bytes) ada1: 61440MB (125829120 512 byte sectors) root@fbsd11z51vm1:~ # vboxmanage showhdinfo FreeBSD11.1x64_1.vdi UUID: 1e5e1cab-2281-445c-9ded-10e7877cc4a4 Parent UUID: base State: locked read Type: normal (base) Location: C:\XXXXXXXXXXX\FreeBSD11.1x64_1.vdi Storage format: VDI Format variant: dynamic default Capacity: 81920 MBytes Size on disk: 28419 MBytes Encryption: disabled In use by VMs: FreeBSD11.1x64#1 (UUID: 2231222c-b7aa-4976-ba5e-a4524a7d7287) [Snapshot#1 (UUID: 54b79fb2-faa3-4072-a651-2f270022b950)] Child UUIDs: 46e7ebef-dd79-4147-b82d-f4abf75e50d2 vboxmanage showhdinfo FreeBSD11.1x64_2.vdi UUID: ef5bd266-fc22-402b-9ee6-126cb4d2bdaf Parent UUID: base State: locked write Type: normal (base) Location: C:\XXXXXXXXXXXXXXXXXX\FreeBSD11.1x64_2.vdi Storage format: VDI Format variant: dynamic default Capacity: 61440 MBytes Size on disk: 12084 MBytes Encryption: disabled In use by VMs: FreeBSD11.1x64#1 (UUID: 2231222c-b7aa-4976-ba5e-a4524a7d7287) Thanks all! --=20 cheers mars ----- From owner-freebsd-fs@freebsd.org Fri Mar 9 14:33:03 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 BAFBCF2D14A for ; Fri, 9 Mar 2018 14:33:03 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from lwfs1-cam.cam.lispworks.com (mail.lispworks.com [46.17.166.21]) by mx1.freebsd.org (Postfix) with ESMTP id D117179750; Fri, 9 Mar 2018 14:33:02 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (higson.cam.lispworks.com [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.15.2/8.15.2) with ESMTP id w29EWqCg029706; Fri, 9 Mar 2018 14:32:52 GMT (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (localhost.localdomain [127.0.0.1]) by higson.cam.lispworks.com (8.14.4) id w29EWp8d015595; Fri, 9 Mar 2018 14:32:51 GMT Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id w29EWpnH015591; Fri, 9 Mar 2018 14:32:51 GMT Date: Fri, 9 Mar 2018 14:32:51 GMT Message-Id: <201803091432.w29EWpnH015591@higson.cam.lispworks.com> From: Martin Simmons To: Mars G Miro CC: trasz@freebsd.org, imp@bsdimp.com, freebsd-fs@freebsd.org In-reply-to: (message from Mars G Miro on Fri, 9 Mar 2018 15:03:06 +0800) Subject: Re: growfs only works on GPT partitioning schemes? References: <201802261411.w1QEBRt1002026@higson.cam.lispworks.com> <5A9A4B1E.8070206@anarchy.in.the.ph> <20180303113306.GB2029@brick> <201803081426.w28EQNE6003598@higson.cam.lispworks.com> 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: Fri, 09 Mar 2018 14:33:03 -0000 >>>>> On Fri, 9 Mar 2018 15:03:06 +0800, Mars G Miro said: > > It does have 2 snapshots in fact, this is a known problem ? > > ... > > vboxmanage showhdinfo FreeBSD11.1x64_1.vdi > > UUID: 1e5e1cab-2281-445c-9ded-10e7877cc4a4 > Parent UUID: base > State: locked read > Type: normal (base) > Location: C:\XXXXXXXXXXX\FreeBSD11.1x64_1.vdi > Storage format: VDI > Format variant: dynamic default > Capacity: 81920 MBytes > Size on disk: 28419 MBytes > Encryption: disabled > In use by VMs: FreeBSD11.1x64#1 (UUID: > 2231222c-b7aa-4976-ba5e-a4524a7d7287) [Snapshot#1 (UUID: > 54b79fb2-faa3-4072-a651-2f270022b950)] > Child UUIDs: 46e7ebef-dd79-4147-b82d-f4abf75e50d2 > > > vboxmanage showhdinfo FreeBSD11.1x64_2.vdi > > UUID: ef5bd266-fc22-402b-9ee6-126cb4d2bdaf > Parent UUID: base > State: locked write > Type: normal (base) > Location: C:\XXXXXXXXXXXXXXXXXX\FreeBSD11.1x64_2.vdi > Storage format: VDI > Format variant: dynamic default > Capacity: 61440 MBytes > Size on disk: 12084 MBytes > Encryption: disabled > In use by VMs: FreeBSD11.1x64#1 (UUID: > 2231222c-b7aa-4976-ba5e-a4524a7d7287) Yes, that is the problem (your first disk has snapshots, but you probably only resized the base vdi). Some people on the internet report success after resizing all the snapshots as well (see the "Child UUIDs" in the output and recurse). I would make a backup before doing this. Your second disk doesn't have snapshots, which is why resizing it worked. __Martin From owner-freebsd-fs@freebsd.org Fri Mar 9 17:32: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 6861CF3BF43 for ; Fri, 9 Mar 2018 17:32:26 +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 2025E829D1 for ; Fri, 9 Mar 2018 17:32:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6BE0411AEE for ; Fri, 9 Mar 2018 17:32:25 +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 w29HWPWI085754 for ; Fri, 9 Mar 2018 17:32:25 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w29HWPbx085753 for freebsd-fs@FreeBSD.org; Fri, 9 Mar 2018 17:32:25 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: freebsd-fs@FreeBSD.org Subject: [Bug 210409] zfs: panic during boot Date: Fri, 09 Mar 2018 17:32:25 +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: bdrewery@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Mar 2018 17:32:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210409 --- Comment #12 from Bryan Drewery --- Something weird is that I've consistently seen that if I drop to loader for= a moment and then boot, the problem does not show up. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Mar 9 17:51:43 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 AF1DAF3DADD for ; Fri, 9 Mar 2018 17:51:43 +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 4D68D839E4 for ; Fri, 9 Mar 2018 17:51:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 7EB2C11CAF for ; Fri, 9 Mar 2018 17:51:42 +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 w29Hpg0o027688 for ; Fri, 9 Mar 2018 17:51:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w29Hpgq5027687 for freebsd-fs@FreeBSD.org; Fri, 9 Mar 2018 17:51:42 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: freebsd-fs@FreeBSD.org Subject: [Bug 223015] [tmpfs] [patch] tmpfs does not support sparse files Date: Fri, 09 Mar 2018 17:51: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: emaste@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: see_also 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: Fri, 09 Mar 2018 17:51:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223015 Ed Maste changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=3D2= 101 | |83 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Mar 10 01:54: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 63275F3C1B8 for ; Sat, 10 Mar 2018 01:54:56 +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 F0A487A459 for ; Sat, 10 Mar 2018 01:54: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 15E0616029 for ; Sat, 10 Mar 2018 01:54:55 +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 w2A1ssMe041882 for ; Sat, 10 Mar 2018 01:54:54 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2A1ss3M041881 for freebsd-fs@FreeBSD.org; Sat, 10 Mar 2018 01:54: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: freebsd-fs@FreeBSD.org Subject: [Bug 225877] panic: solaris assert: newds == os->os_dsl_dataset during "zpool upgrade" Date: Sat, 10 Mar 2018 01:54:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: asomers@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Mar 2018 01:54:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225877 Alan Somers changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|asomers@FreeBSD.org |freebsd-fs@FreeBSD.org --- Comment #2 from Alan Somers --- Reassign back to the pool. I'm no longer working on ZFS. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Mar 10 19:46:28 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 83AB9F2D8DF for ; Sat, 10 Mar 2018 19:46:28 +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 078FE814B3 for ; Sat, 10 Mar 2018 19:46:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 46BF91F41D for ; Sat, 10 Mar 2018 19:46:27 +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 w2AJkRKo068579 for ; Sat, 10 Mar 2018 19:46:27 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2AJkRK4068578 for freebsd-fs@FreeBSD.org; Sat, 10 Mar 2018 19:46:27 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: freebsd-fs@FreeBSD.org Subject: [Bug 208882] zfs root filesystem mount failure on startup in FreeBSD 10.3-RELEASE if USB hdd with zpool is attached to another port Date: Sat, 10 Mar 2018 19:46:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: ian@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: ian@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to cc bug_status Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Mar 2018 19:46:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208882 Ian Lepore changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-fs@FreeBSD.org |ian@FreeBSD.org CC| |ian@FreeBSD.org Status|New |Open --- Comment #20 from Ian Lepore --- To expand a little bit on Warner's comment, based on a discussion we had on irc... The current root mount hold system is incomplete, and it may be inadequate overall to ever help with the zfs situations. One way the current system is incomplete is illustrated by the usb subsyste= m.=20 A root hold is placed for each usb bus while it is scanned, and released wh= en the scan is complete. That allows any umass devices on the bus to be creat= ed before releasing the hold. The problem is that a umass device is not the t= hing that hosts the root filesystem, it needs to attach to CAM and eventually ha= ve a da device created, then geom needs to taste that device and create all geom= s on it, and so on. All this work ends up happening asynchronously after the usb bus root hold is released. To fix this properly, the umass device would ha= ve to place its own root hold which didn't get released until CAM had created = and attached the da device(s). CAM would have to place its own root holds that would have to remain in place until geom had finished tasting the new devic= es.=20 All this same extra plumbing of holds would have to be replicated in the mm= c/sd subsystem as well. Because of all the existing races you can't actually re= ly on the releasing of all mount holds to indicate that devices are ready. So= the scheme only works for devices that are mounted by specifying a /dev/somethi= ng name, because that allows the code in vfs_mountroot.c to keep looping until= a name lookup succeeds. Which brings us to zfs, a way to host root filesystems that doesn't mount t= hem based on names in /dev, so there's no way the existing root mount hold syst= em and detection of availability can even be extended to zfs. A much simpler alternative is the idea contained in the patch with this PR: detect the availability of the root filesystem by attempting to mount it, a= nd if that fails, pause briefly and try again, until the timeout expires. With this new retry loop in place, there is little reason for the whole root mou= nt hold system to continue to exist as well, but removing it is more complicat= ed and should be handled separately after this simple fix is comitted. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Mar 10 23:40: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 D09F0F408D1 for ; Sat, 10 Mar 2018 23:40:21 +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 6831C6BCEC for ; Sat, 10 Mar 2018 23:40:21 +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 9AB7F213FB for ; Sat, 10 Mar 2018 23:40:20 +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 w2ANeKD8014377 for ; Sat, 10 Mar 2018 23:40:20 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w2ANeKYB014376 for freebsd-fs@FreeBSD.org; Sat, 10 Mar 2018 23:40:20 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: freebsd-fs@FreeBSD.org Subject: [Bug 226499] Partial system freeze via ZFS rename and possible other operations Date: Sat, 10 Mar 2018 23:40:20 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Mar 2018 23:40:22 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D226499 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.=