From owner-freebsd-fs@freebsd.org Sun Oct 22 12:41:50 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 757B0E51F0D for ; Sun, 22 Oct 2017 12:41:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5CE9764C67 for ; Sun, 22 Oct 2017 12:41:50 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9MCfnb5027382 for ; Sun, 22 Oct 2017 12:41:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223015] [tmpfs] tmpfs does not support sparse files Date: Sun, 22 Oct 2017 12:41:49 +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: kwhite@site.uottawa.ca X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Oct 2017 12:41:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223015 --- Comment #5 from Keith White --- (In reply to Konstantin Belousov from comment #4) After some dtracing (and head scratching), I believe I see a solution for my problem by using resident_page_count instead of size. It will complicate tmpfs_write() though... ...keith --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 22 23:53:46 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2FFC3E3A4CD for ; Sun, 22 Oct 2017 23:53:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1E3097EA13 for ; Sun, 22 Oct 2017 23:53:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9MNrjZ9044840 for ; Sun, 22 Oct 2017 23:53:45 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223015] [tmpfs] tmpfs does not support sparse files Date: Sun, 22 Oct 2017 23:53:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kwhite@site.uottawa.ca X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Oct 2017 23:53:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223015 Keith White changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #187197|0 |1 is obsolete| | --- Comment #6 from Keith White --- Created attachment 187384 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D187384&action= =3Dedit POC for using resident_page_count This patch allows me to use large files with holes. e.g. # mkdir /tmp/_x # mount -t tmpfs -osize=3D10m tmp /tmp/_x # truncate -s4g /tmp/_x/4g # ls -ls /tmp/_x/4g 0 -rw-r--r-- 1 root wheel 4294967296 Oct 22 19:51 /tmp/_x/4g # df /tmp/_x Filesystem 1K-blocks Used Avail Capacity Mounted on tmpfs 10240 4 10236 0% /tmp/_x # du /tmp/_x 0 /tmp/_x # umount /tmp/_x # rmdir /tmp/_x --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sun Oct 22 23:54:17 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 009EAE3A531 for ; Sun, 22 Oct 2017 23:54:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E354F7EAA3 for ; Sun, 22 Oct 2017 23:54:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9MNsGqs045647 for ; Sun, 22 Oct 2017 23:54:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223015] [tmpfs] [patch] tmpfs does not support sparse files Date: Sun, 22 Oct 2017 23:54:17 +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: kwhite@site.uottawa.ca 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: short_desc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Oct 2017 23:54:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223015 Keith White changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[tmpfs] tmpfs does not |[tmpfs] [patch] tmpfs does |support sparse files |not support sparse files --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Oct 23 07:50:06 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A049E440D3 for ; Mon, 23 Oct 2017 07:50:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1C94A66460 for ; Mon, 23 Oct 2017 07:50:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9N7o5TS063730 for ; Mon, 23 Oct 2017 07:50:05 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 221075] regression: 11.1 is unable to mount ZFS / on boot Date: Mon, 23 Oct 2017 07:50:05 +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: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: freebsd-bugs@virtualtec.ch X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2017 07:50:06 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221075 Markus Wild changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-bugs@virtualtec.ch --- Comment #15 from Markus Wild --- Just wanted to add a "me too" mention for this bug. Short summary: - Supermicro X10DRI-T motherboard, using UEFI boot, 128G RAM, 2 CPUs - 2 Intel DC P3700 NVME cards, to be used as mirrored zfs root and mirrored= log devices for a data pool - FreeBSD-11.1 release installs fine off memstick, and the built system boo= ts correctly, but this system uses the entire disks (so I need to shrink the system to make room for log partitions) - so I then rebooted into usb live system, and did a gpart backup of the nv= me drives (see later). zfs snapshot -r, zfs send -R > backup, gpart delete last index and recreate with shorter size = on both drives, recreate zroot pool with correct ashift, restore with zfs receive from backup, set bootfs, reboot - the rebooting system bootloader finds the zroot pool correctly, and proce= eds to load the kernel. However, when it's supposed to mount the root filesystem, I get: Trying to mount root from zfs:zroot/ROOT/default []... Mounting from zfs:zroot/ROOT/default failed with error 6. - when I list the available boot devices, all partitions of the nvme disks = are listed - I can import this pool without any issues with the usb live system, there= are no errors on import. - I then redid the whole exercise, but restored the previously backed up partition tables (full size zfs partition), did exactly the same steps as described above to restore the previous zfs filesystem, rebooted, and the system started up normally. I then tried to recreate the pool using nvd0p3/nvd1p3 instead of gpt-labels, but this didn't help. But, when I built a custom kernel as suggested here: include GENERIC ident CUSTOM nodevice mmc nodevice mmcsd nodevice sdhci this kernel booted fine! So, whatever went into the system for MMC support = is messing with correct mounting of zfs root pools... --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Oct 23 08:41:18 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 242A8E45B69 for ; Mon, 23 Oct 2017 08:41:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1232D6850B for ; Mon, 23 Oct 2017 08:41:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9N8fHPE010378 for ; Mon, 23 Oct 2017 08:41:17 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223015] [tmpfs] [patch] tmpfs does not support sparse files Date: Mon, 23 Oct 2017 08:41:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2017 08:41:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223015 --- Comment #7 from Konstantin Belousov --- (In reply to Keith White from comment #5) object->resident_page_fault is equally meaningless for your purposes. What= is not clear in my comment #4 ? The patch does not require any of these dynamic calculations using meaningl= ess (for this purpose) values. If you want to limit the tmpfs mount memory use, specify explicit limit to mount_tmpfs. The attempts to mis-use some pageda= emon or object internal counters would not work out, their purpose is very diffe= rent and they do not match with resource limiting for tmpfs. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Oct 23 13:08:39 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB455E4B52E for ; Mon, 23 Oct 2017 13:08:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 99EC56FE75 for ; Mon, 23 Oct 2017 13:08:39 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9ND8cXt060426 for ; Mon, 23 Oct 2017 13:08:39 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223015] [tmpfs] [patch] tmpfs does not support sparse files Date: Mon, 23 Oct 2017 13:08:38 +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: kwhite@site.uottawa.ca X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2017 13:08:39 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223015 --- Comment #8 from Keith White --- I read but probably misunderstood! If I create a file with holes I don't wa= nt to be "charged" for it until the holes are filled in. I may want to create= a disk image file, say, that is 4g but I know that I will only be storing 20m= in total. ffs-like filesystems allow this. tmpfs has a more straight-forward idea of a file (allocate up-front, no hole management?). A "BUGS" section = in tmpfs(5) would have guided me away from attempting to use tmpfs for sparse files. Othersize tmpfs is an excellent fit for me since I'm running diskless+swapless. I'll re-read your comments. I see a drawing-board over there that I should = get back to... ...keith --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Oct 23 13:48:33 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EAFF8E4C59E for ; Mon, 23 Oct 2017 13:48:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D86607168A for ; Mon, 23 Oct 2017 13:48:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9NDmXNX074091 for ; Mon, 23 Oct 2017 13:48:33 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 221077] Boot from ZFS fails following freebsd-update Date: Mon, 23 Oct 2017 13:48:33 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.3-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bacon4000@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2017 13:48:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221077 --- Comment #8 from Jason Bacon --- Just for the sake of completeness, I should mention that I've had this issu= e on two machines, and both were running ZFS on top of a PERC hardware RAID. I = have used root on ZFS on other systems over the past few years, where ZFS is doi= ng the volume management (raidz2) and have not had any issues so far. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Oct 23 14:53:49 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0304FE4DA26 for ; Mon, 23 Oct 2017 14:53:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E5D7A73381 for ; Mon, 23 Oct 2017 14:53:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9NErmqc067950 for ; Mon, 23 Oct 2017 14:53:48 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223015] [tmpfs] [patch] tmpfs does not support sparse files Date: Mon, 23 Oct 2017 14:53:48 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kib@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2017 14:53:49 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223015 --- Comment #9 from Konstantin Belousov --- (In reply to Keith White from comment #8) Let me explain it in full: 1. tmpfs should not try to use current counters of the active/inactive or f= ree queues, since they are irrelevant to the system ability to satisfy page requests. If page is needed, the queues are scanned and a usable page might appear even if there is no free pages or all swap space is used (e.g. we can write out dirty file page or reuse clean file page). 2. tmpfs should provide a global limit on the number of used pages, in fact= it already has it "-o size". The limit is compared against the maintained cou= nter of the supposedly used pages tm_pages_used. 3. Your problem is because tm_pages_used is too harsh. It just sums up all files sizes, while it really should only count file pages which were really written to. In other words, instead of adjusting tm_pages_used in tmpfs_reg_resize(), it should be adjusted in tmpfs_write(). [There is additional complication, see below]. 4. The tmpfs_mem_avail() should be removed. See item 1. The complication is due to the tmpfs using in-place mapping, i.e. the vm ob= ject which contains the pages with the file data, directly provides the pages us= ed for file mapping. This was highly desirable feature, because it avoids duplicating memory for the mmapped tmpfs files, and makes mmap zero-copy. Problem is, page faults in the sparcerly allocated mmaped file range instantiate the file pages, which must be accounted for in tm_pages_max. T= he tmpfs vm objects are already flagged so this is not too hard to do, just th= at you cannot limit the patch to fs/tmpfs only. This is my current opinion on the issue, hope this is clean enough. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Mon Oct 23 16:04:00 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16450E4EDED for ; Mon, 23 Oct 2017 16:04: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 mx1.freebsd.org (Postfix) with ESMTPS id 0475975648 for ; Mon, 23 Oct 2017 16:04:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9NG3wGA009501 for ; Mon, 23 Oct 2017 16:03:59 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223015] [tmpfs] [patch] tmpfs does not support sparse files Date: Mon, 23 Oct 2017 16:03: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: kwhite@site.uottawa.ca X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Oct 2017 16:04:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223015 --- Comment #10 from Keith White --- (In reply to Konstantin Belousov from comment #9) Yes, this helps to clear things up. Very many thanks! ...keith --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Tue Oct 24 00:06:23 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 498C3E2F24B for ; Tue, 24 Oct 2017 00:06:23 +0000 (UTC) (envelope-from matthew.ahrens@delphix.com) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 CA7FE6598D for ; Tue, 24 Oct 2017 00:06:22 +0000 (UTC) (envelope-from matthew.ahrens@delphix.com) Received: by mail-lf0-x22d.google.com with SMTP id 75so22001049lfx.1 for ; Mon, 23 Oct 2017 17:06:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphix.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=os+tvk/eEWWFHPn0D9+sZPSnv5PALN0MkxsBj7rbhGg=; b=SdsBETmygtjpagWyDNy2Da0/dipKwAHR4uXBMuKRUjdozh6pCMVCz1OcpaOaUVNNy3 DorkZHkIDRTvp9Jf+yA1CAcef3G41iiIkijCUohZhISWY+SaBsolQQ528sAexCv2z0wb keG9tNjaQLSQlf8zDz/O/guHg4MEepRggMIos= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=os+tvk/eEWWFHPn0D9+sZPSnv5PALN0MkxsBj7rbhGg=; b=GZ10aK5vqkIN318vR49RK1QszxaYgiQ2J5isNcarBJIkOGcn2y8JgCa3VdiI6t78Z3 F9+VcFnUTJq4YRDYFuPcTpWBev0ZJ4cyB6sGOQWHTJ9cSy0oEoAfC/ilgHJj9o68qpKx MsSFLIuqn/bJATB0UMjuvaXS/3vGZ/WB7uZbmQwASJu+pNYXpKmMpXmr813PHKqtlgCl +RJhl9fQoO9LhY1btCs9qNONb/Ojn+9S1pKsnYU6bZ+8aaYU/E4NrkQUkYWhLeeMwH1N 3Zja7yVvRlca4NKLH9QTOP0rogmEvC+9zDkOc5yBTN4QL7gLx6me8BhSoAa5trP+Cn97 NNzw== X-Gm-Message-State: AMCzsaVp2QLJKFxD0bGnYCTVzsxaHV3CK1rq0byVTH/9H393sko8bJVX dhDZ6JL3fjBLJO8yqmMfTbRbr+T8zBlik+BUsoQmJQ== X-Google-Smtp-Source: ABhQp+R1pw2hOZX+pf0jcDhjjn5Vq9TIz8MAWBxc5CZSz1x+cFIHROTYbQqh2YZRb3RXZXn8CwX4nSbTN0QuGw5uu30= X-Received: by 10.25.67.73 with SMTP id m9mr2558750lfj.69.1508803580140; Mon, 23 Oct 2017 17:06:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.198.71 with HTTP; Mon, 23 Oct 2017 17:06:19 -0700 (PDT) From: Matthew Ahrens Date: Mon, 23 Oct 2017 17:06:19 -0700 Message-ID: Subject: OpenZFS Developer Summit 2017 - streaming live tomorrow To: "admin@open-zfs.org" , developer , illumos-zfs , zfs-devel@list.zfsonlinux.org, zfs-devel@freebsd.org, freebsd-fs , zfs-discuss Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Oct 2017 00:06:23 -0000 The OpenZFS Developer Summit is tomorrow (Tuesday)! We will be live-streaming the talks, starting at 9AM Pacific time. You can view here: https://livestream.com/accounts/26168990/OpenZFS2017 (we'll also have a link up on the open-zfs.org webpage) I've seen all the speakers' slides and I'm really excited about this year's talks. There are at least 2 surprising announcements that you won't want to miss! --matt On Mon, Sep 25, 2017 at 12:11 PM, Matthew Ahrens wrote: > The fifth annual OpenZFS Developer Summit will be held in 4 weeks, in San > Francisco, *October 24-25, 2017* (Tuesday-Wednesday). > > See http://www.open-zfs.org/wiki/OpenZFS_Developer_Summit for all of the > details, including slides and videos from previous years' conferences. > > *Talks: Day 1* > TitleSpeakerCompany > State of the Union Matt Ahrens Delphix > Keynote: ZFS Past & Future Mark Maybee Oracle > MMP: Safe "zpool import" for Clusters Olaf Faaland LLNL > ZIL Performance: How I Doubled Sync Write Speed Prakash Sruya Delphix > iFlash: Dynamic Adaptive L2ARC Caching Shailendra Tripathi Tegile > Faster Allocation with the Log Spacemap Serapheim Dimitropoulos Delphix > DRAID Isaac Huang Intel > Porting With OSX Jorgen Lundman independent > Fast Clone Deletion Sara Hartse Delphix > ZSTD Compression Allan Jude ScaleEngine > > *Talks: Day 2* > TitleSpeakerCompany > A proposal for 1,000x better dedup performance Matt Ahrens Delphix > Improving resilver: results & operational impacts Saso Kiselkov Nexenta > Storage Pool Checkpoint Serapheim Dimitropoulos Delphix > New prefetcher for sequential scrub Tom Caputi Datto > RAID-Z Expansion Matt Ahrens Delphix + FreeBSD Foundation > From owner-freebsd-fs@freebsd.org Thu Oct 26 07:41:06 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1BC07E40DAC for ; Thu, 26 Oct 2017 07:41:06 +0000 (UTC) (envelope-from maurizio@metaljonica.it) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id EB1E06FE9C for ; Thu, 26 Oct 2017 07:41:05 +0000 (UTC) (envelope-from maurizio@metaljonica.it) Received: by mailman.ysv.freebsd.org (Postfix) id EA65EE40DA6; Thu, 26 Oct 2017 07:41:05 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EA005E40DA5 for ; Thu, 26 Oct 2017 07:41:05 +0000 (UTC) (envelope-from maurizio@metaljonica.it) Received: from mail-out-01.it.net (mailprofe01-152.it.net [151.1.195.152]) by mx1.freebsd.org (Postfix) with ESMTP id 521D16FE96 for ; Thu, 26 Oct 2017 07:41:04 +0000 (UTC) (envelope-from maurizio@metaljonica.it) Received: from mail-fe-avasout01.mail.int (10.213.52.33) by mail-out-01.it.net (8.6.060.05) id 5981871300771F44 for fs@freebsd.org; Thu, 26 Oct 2017 09:39:08 +0200 X-Junkmail-Premium-Raw: score=26/50, refid=2.7.2:2017.10.26.44516:17:26.894, ip=, rules=__HAS_FROM, __FRAUD_SUBJ_ALLCAPS, __SUBJ_ALPHA_END, __TO_MALFORMED_2, __TO_NAME, __CT, __CTYPE_MULTIPART_ALT, __CTYPE_HAS_BOUNDARY, __CTYPE_MULTIPART, __MIME_VERSION, __UNUSABLE_MSGID, __MIME_TEXT_P2, __MIME_TEXT_H2, __ANY_URI, __URI_WITH_PATH, LINK_TO_IMAGE, URI_ENDS_IN_HTML, __FRAUD_CONTACT_NUM, __PHISH_PHRASE5, __CP_MEDIA_BODY, __FRAUD_CONTACT_ADDY, __C230066_P5, __FRAUD_MONEY_DENOMINATION, __LINES_OF_YELLING, SUPERLONG_LINE, __URI_IN_BODY, __URI_NOT_IMG, __HTTP_IMAGE_TAG, __HTML_BOLD, __HTML_AHREF_TAG, __URI_WITHOUT_PATH, __HTML_TAG_CENTER, __STYLE_TAG, __HAS_HTML, __HTML_TAG_TABLE, __HTML_TAG_DIV, BODY_SIZE_10000_PLUS, BODYTEXTP_SIZE_3000_LESS, BODYTEXTH_SIZE_3000_MORE, __MIME_TEXT_H1, __MIME_TEXT_P1, __MIME_HTML, __TAG_EXISTS_HTML, LINES_OF_YELLING_3, LEO_OBFU_FLOAT, __URI_NS, HTML_70_90, NO_MESSAGE_ID, __MIME_TEXT_H, __MIME_TEXT_P, NO_URI_HTTPS, STYLE_RATWARE_COMBINED Received: from host52-226-static.226-95-b.business.telecomitalia.it (95.226.226.52) by mail-fe-avasout01.mail.int (9.0.019.04) (authenticated as maurizio@metaljonica.it) id 59B3AA5501499D10 for fs@freebsd.org; Thu, 26 Oct 2017 09:39:05 +0200 Message-ID: <59B3AA5501499D10@mail-fe-avasout01.mail.int> (added by postmaster@mail-fe-avasout01.mail.int) From: "Maurizio Pisano" Subject: NEW BEACH CLEANER 2017 - EVOLUTION 205 HD - WITH HIGH DUMP To: "fs" MIME-Version: 1.0 Organization: Metaljonica snc Date: Thu, 26 Oct 2017 09:39:04 +0200 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2017 07:41:06 -0000 =EF=BB=BFNewsletter MetaljonicaIf you do not see this newsletter prope= rly, consult the online version. Add info@puliscispiaggia.com to your address book contacts and always = arrive in your inbox.=20 =20 EVOLUTION HD NEW MODEL 2017 - with high dump =20 =20 Evolution Series =20 Read MoreP Series =20 Read MoreS Series =20 Read More METALJONICA MACHINE CLEAN BEACH =20 Welcome to METALJONICA =E2=80=93 Italy=E2=80=99s Leader in the product= ion of Beach cleaner machines. METALJONICA has been producing Beach cl= eaner machines for about 20 years. To satisfy the market=E2=80=99s nee= ds, we produce several types of beach cleaner machine. They all work according to an exclusive system planned by our company = which makes them strong and efficient. Our machine do not fear stones,= where the other ones stop, we go ahead. To make the difference contri= butes our consolidated experience like producers of beach cleaner mach= ines. We are already located in different geographic areas of the worl= d, always looking for new partnerships. GO TO NEW WEB SITESHOW VIDEODOWNLOAD CATALOG BUY DIRECTLY IN FACTORY SALES MANAGER Maurizio Pisano=20 TEL: +39 335.16 35 168 EMAIL: Info@puliscispiaggia.com Call with Skype OFFICES AND PRODUCTION A14 exit (Zone Autoporto) 64026 Roseto degli Abruzzi (TE)=20 VAT: 01489870673=20 TEL: +39 +39 085.89 37 973=20 EMAIL: Info@puliscispiaggia.com =20 METALJONICA SNC Zona Artigianale Autoporto ZIP CODE 64026 - Roseto deg= li Abruzzi ITALY PHONE/FAX +39 085 8937973 www.puliscispiaggia.com info@puliscispiaggia= =2Ecom - Unsubscribe by email=20 This message, for the D.lgs n.196 / 30.06.03 (Privacy Code), may conta= in confidential and/or privileged information. If you are not the addr= essee or authorized to receive this for the addressee, you must not us= e, copy, disclose or take any action based on this message or any info= rmation herein. If you have received this message in error, please adv= ise the sender immediately by reply e-mail and delete this message. Th= ank you for your cooperation. Your e-mail has been retrieved from the = web or from public directories. Our intention is only to provide infor= mation. If no you like our communications, with simple e-mail communic= ation and nothing more will be delivered. Guarantee of confidentiality= Metaljonica s.n.c. guarantees the confidentiality of the data provide= d pursuant to Legislative Decree 196/2003 (Privacy Code). At any time = you can exercise your rights under art. 7 of Legislative Decree 196/20= 03., Including those to rectify and delete data or to oppose the treat= ment, writing to info@puliscispiaggia.com The data controller is Metal= jonica s.n.c.=20 From owner-freebsd-fs@freebsd.org Thu Oct 26 10:16:28 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC7ADE449EC for ; Thu, 26 Oct 2017 10:16:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AA7D8741EE for ; Thu, 26 Oct 2017 10:16:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9QAGRiZ023901 for ; Thu, 26 Oct 2017 10:16:28 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 219049] ftruncate() slow on UFS+journaled softupdates Date: Thu, 26 Oct 2017 10:16:27 +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 Only Me X-Bugzilla-Who: dol@ngcom.ru X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Oct 2017 10:16:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219049 dol@ngcom.ru changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dol@ngcom.ru --- Comment #5 from dol@ngcom.ru --- I have the same problem after upgrade from 10.1 to 11.1 - very slow pkg extract LSI Raid1 mps0, UFS filesystem pkg-1.10.1=20 kernel=20 11.1-RELEASE-p1 FreeBSD 11.1-RELEASE-p1 #0: Wed Aug 9 11:55:48 UTC 2017=20= =20=20=20 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Oct 27 15:39:05 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B649E496E3 for ; Fri, 27 Oct 2017 15:39:05 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d: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 B87B16BD53 for ; Fri, 27 Oct 2017 15:39:04 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-qk0-x22c.google.com with SMTP id m189so8813057qke.4 for ; Fri, 27 Oct 2017 08:39:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:subject:message-id:mime-version :content-disposition:user-agent; bh=reRKSJICjdTv64LuIddq2Lifq6/MWNI2hgw7sp5AvwI=; b=UaTrlO34atXg2t4bB1bHHCwnuzMOfHz4szhgiOmkQzL8TGmA31nmRUedhLr3wDYBqU POjwe2QwFCEnycaqmJp5kSFugPs7X3VWmDjuMeOOP8PXDOO2BIpCEV06c7fetcvtZN+T AcBlb1AW2FR2tyzMti53jYsBk4OqthrFtYIsMUu6epzB0BceXGqIi4oSLXV4SffxNwgg Q3aU6KfoAtGfRc8hOJKL396roPM2L3cv+O4tT/20XEV6Cd9HX5CdTvpMbw+aV7qc2H93 jYHKfF5pyQ5Um3CxxlGpjXtV1TtRfN4rGEzfxL6s83TpCH341TfZZRE05Jh7ynSmzmrJ aCGg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:subject:message-id :mime-version:content-disposition:user-agent; bh=reRKSJICjdTv64LuIddq2Lifq6/MWNI2hgw7sp5AvwI=; b=M5zCp4q5vy+4uwzWPX2NzrDUPrS1RvzCFxW2HsbxH1g55jbwrspYoRN6pMAy8IPo/v 3PlnW+4yRWtY89op+4YL1fXFTOI4vzDImz9OflKXpHZxKJ309lBV2h5oPsPT1uizBjQ4 mhRhtJ+mvQBEqumkI9cqYfBoNq8fgU4cKfK0teEGMrqQiYl2G/YKb9xeiCq7YvXeEYX+ MCr/yX0cYo/b7OjhPyER9N8cr6yxkqAbqRdfRLBQoa1DA6poS3mllXC1lp8hkQaGhMqi j6OOaZukBzJPrpwFUt3aj73w0W6BeXJ2CXFFTp1+5cBdFG4SwAyqFKe2ki7rrpQ3cT/C ry8g== X-Gm-Message-State: AMCzsaWWUsYemSKtFr/WHbhqGM2DzfRB9bgEvk2PIdcpoLlcVcJJUApU tK5mgrcTPLoedF3fh/9oCGPI9g== X-Google-Smtp-Source: ABhQp+TRyQshy6TpjLG5MKaIlfOwoMO/Qa03Jo1RiHIFWx9HKHzNAM0xIPxMkrztVguXDO6iuYu33g== X-Received: by 10.233.230.10 with SMTP id z10mr1358061qkf.8.1509118743507; Fri, 27 Oct 2017 08:39:03 -0700 (PDT) Received: from raichu (toroon0560w-lp140-01-69-159-38-22.dsl.bell.ca. [69.159.38.22]) by smtp.gmail.com with ESMTPSA id 42sm5264674qkx.27.2017.10.27.08.39.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Oct 2017 08:39:02 -0700 (PDT) Sender: Mark Johnston Date: Fri, 27 Oct 2017 11:39:00 -0400 From: Mark Johnston To: freebsd-fs@FreeBSD.org Subject: softdep as a mount(8) option Message-ID: <20171027153859.GC2385@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2017 15:39:05 -0000 Hi, I'd like to finally enable the use of SU (not SU+J) on some small UFS filesystems. The fact that SU is enabled using a flag in the superblock poses a problem for me, however: the systems containing these filesystems may at any time be repurposed to run a kernel that supports SU but contains bugs[*] that render it unusable. I therefore can't persistently enable SU in these systems. I'm wondering if it would be possible to enable SU using a mount option rather than with a persistent flag. fsck_ffs conditionalizes some of its logic on whether SU is configured - is this necessary for correctness? That is, if I run fsck on an unclean filesystem that had been mounted with SU, and fsck runs as though SU hadn't been configured, what problems might arise? [*] These bugs are a result of local modifications and aren't in FreeBSD. From owner-freebsd-fs@freebsd.org Fri Oct 27 15:51:51 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8D6E3E4A3EC for ; Fri, 27 Oct 2017 15:51:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7A3536D119 for ; Fri, 27 Oct 2017 15:51:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9RFpppZ015903 for ; Fri, 27 Oct 2017 15:51:51 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223275] zfsloader fails to see datasets Date: Fri, 27 Oct 2017 15:51:51 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: linimon@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2017 15:51:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223275 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Oct 27 17:20:06 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1327E4CD89 for ; Fri, 27 Oct 2017 17:20:06 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2FC0C70DD3 for ; Fri, 27 Oct 2017 17:20:06 +0000 (UTC) (envelope-from ben.rubson@gmail.com) Received: by mail-wm0-x22a.google.com with SMTP id r68so5134511wmr.3 for ; Fri, 27 Oct 2017 10:20:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=OZUtfqBVQ+LpG6iK6NDAB26y9WKXhxLxL1e8dbRVmC4=; b=GlfqDsDgMqFnDNrcpnU7VTZvSJlzMufUovo/s48RerUE2HUlXnHmKnZlq7AGdVj3zV 7Vx1ap+OGdVzRfF8n5sJEicw9lXUm5sTCg+FqXlyOMyszF/zNaqzIBrM6G1Wc1j7vk6V NUuQt4et3TrBY3lhNUx/atDBnNOFZZmbqN69WVzoOHYm9zKevoJ9NXCBpDBP2mO32GvY QUZJ8BprTJq+bHa0XxFHhlNFU3GSbLoZtEuAOaUK+EUuHBxTsIUzQuE2tmCB6qLFKtKO IFy9LmjJMGmBOL7/74rFgshfGjCWnYAX2Y+D0+gp8Z9Ag4scH4XATTsRKoTObV9+WnVU k9fw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=OZUtfqBVQ+LpG6iK6NDAB26y9WKXhxLxL1e8dbRVmC4=; b=OlAK+LvvvuHswJkXx1W6DINsVkHBaU3ArT/zDWnVh6275HN2BsAbV1KSOseLyr6FiE 457hS4I6JeT1iGIX+M6caOBbc2K/KTf6htZ6cKzKlgPam61l/lgyV3iV+yCg+OgPS89O qV324ya5TbbPPrMtO4bk1xnOJxWnminbnoeI/6VG+G/N/62zBMGNE7LJE+9BBzzbQ8Vr NLJDUztj2GdxcxNfZxJX9NC1gzWp9NOlq1E4Dq1gz5Wu6g97Wo5iwHinVwA+/zW9vQuJ LjyyJ/BR6JU9JhXeoHIZfmrj7YQZf4S9VbuAREbRSacrFxTM4Jc/Qpiuet9AdV8srHAE qT3A== X-Gm-Message-State: AMCzsaURQmHZfVmpjl5/2L1CmCbxayPtGs/a4OWq2IOe+DqIEapbKxpe +mylYRYTnLOo0MPLbALP7JMnX60o X-Google-Smtp-Source: ABhQp+T0aWyKaTzDLA50HeO1NFmVZHUcQQgSmC/rwvLybsQS/tXJ9yGBoYpsu1x44j1J5ObH2sa7tg== X-Received: by 10.28.154.137 with SMTP id c131mr1090507wme.142.1509124804333; Fri, 27 Oct 2017 10:20:04 -0700 (PDT) Received: from bens-mac.home (LFbn-MAR-1-416-163.w2-15.abo.wanadoo.fr. [2.15.241.163]) by smtp.gmail.com with ESMTPSA id w75sm1062680wmw.17.2017.10.27.10.20.03 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 27 Oct 2017 10:20:03 -0700 (PDT) Content-Type: text/plain; charset=us-ascii; delsp=yes; format=flowed Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: ZFS stalled after some mirror disks were lost From: Ben RUBSON In-Reply-To: <13AF09F5-3ED9-4C81-A5E2-94BA770E991B@gmail.com> Date: Fri, 27 Oct 2017 19:20:01 +0200 Content-Transfer-Encoding: 7bit Message-Id: <84A3920F-9143-40E9-A91D-13E7B7FB733E@gmail.com> References: <4A0E9EB8-57EA-4E76-9D7E-3E344B2037D2@gmail.com> <82632887-E9D4-42D0-AC05-3764ABAC6B86@gmail.com> <20171007150848.7d50cad4@fabiankeil.de> <6d1c80df-7e9f-c891-31ae-74dad3f67985@internetx.com> <13AF09F5-3ED9-4C81-A5E2-94BA770E991B@gmail.com> To: Freebsd fs X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2017 17:20:06 -0000 On 13 Oct 2017 18:58, Ben RUBSON wrote: > The issue only happens when I disconnect iSCSI drives, it does not occurs > suddenly by itself. > So I would say the issue is on FreeBSD side, not network hardware :) > > 2 distinct behaviours/issues : > - 1 : when I disconnect iSCSI drives from the server running the pool > (iscsictl -Ra), some iSCSI drives remain on the system, leaving ZFS > stalled ; > - 2 : when I disconnect iSCSI drives from the target (shut NIC down / > shutdown ctld), server running the pool sometimes panics (traces in my > previous mail, 06/10). > > (...) > > Andriy, who took many debug traces from my system, managed to reproduce > the first issue locally, using a 3-way ZFS mirror with one local disk > plus two iSCSI disks. > Sounds like there is a deadlock issue on iSCSI initiator side. So, Andriy proposed a patch which solves this first issue : https://reviews.freebsd.org/D12652 > Regarding the second issue, I'm not able to reproduce it if I don't use > geom-labels. > There may then be an issue on geom-label side (which could then also > affect fully-local ZFS pools using geom-labels). and another one for the second issue : https://reviews.freebsd.org/D12809 Many thanks to the list, to Andriy for his nice & impressive work, Alexander & Edward for their reviews. Ben From owner-freebsd-fs@freebsd.org Fri Oct 27 18:22:38 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5BFE4E4E025 for ; Fri, 27 Oct 2017 18:22:38 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout07.t-online.de (mailout07.t-online.de [194.25.134.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1AE9372BAE; Fri, 27 Oct 2017 18:22:37 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd29.aul.t-online.de (fwd29.aul.t-online.de [172.20.26.134]) by mailout07.t-online.de (Postfix) with SMTP id 14184425EEAC; Fri, 27 Oct 2017 20:22:29 +0200 (CEST) Received: from Stefans-MBP-2.fritz.box (ZwgTmZZEZh5zxIny947n0+8Yqy1ah-4J+VSyJ9rxSNbSbRuJ2yJn+I+9PnzEA3fQmZ@[84.154.121.171]) by fwd29.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1e89Gz-2Rde8u0; Fri, 27 Oct 2017 20:22:25 +0200 Subject: Re: softdep as a mount(8) option To: Mark Johnston , freebsd-fs@FreeBSD.org References: <20171027153859.GC2385@raichu> From: Stefan Esser Message-ID: <4d7a735b-c7b3-8fa0-dbea-36e3b0d54191@freebsd.org> Date: Fri, 27 Oct 2017 20:22:24 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.4.0 MIME-Version: 1.0 In-Reply-To: <20171027153859.GC2385@raichu> Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: 7bit X-ID: ZwgTmZZEZh5zxIny947n0+8Yqy1ah-4J+VSyJ9rxSNbSbRuJ2yJn+I+9PnzEA3fQmZ X-TOI-MSGID: 2ae47868-80ed-4231-877b-7edd2233cc76 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Oct 2017 18:22:38 -0000 Am 27.10.17 um 17:39 schrieb Mark Johnston: > Hi, > > I'd like to finally enable the use of SU (not SU+J) on some small UFS > filesystems. The fact that SU is enabled using a flag in the superblock > poses a problem for me, however: the systems containing these > filesystems may at any time be repurposed to run a kernel that supports > SU but contains bugs[*] that render it unusable. I therefore can't > persistently enable SU in these systems. > > I'm wondering if it would be possible to enable SU using a mount > option rather than with a persistent flag. fsck_ffs conditionalizes some > of its logic on whether SU is configured - is this necessary for > correctness? That is, if I run fsck on an unclean filesystem that had > been mounted with SU, and fsck runs as though SU hadn't been configured, > what problems might arise? Yes, this is not only possible, I have implemented this functionality more than 10 years, ago I and have used it for many years, but later converted all systems to ZFS and thus lost interest. My reasoning was just as yours: Whether a file-system was last mounted with SU enabled is relevant for FSCK, but not for the next mount. If a file-system with SU enabled in the superblock is mounted on a system that does not support SU in the kernel, then FSCK will assume that the SU consistency guarantees are given, while they are not. At the time, I in fact hat got agreement from Kirk McKusck, that the mount option ought to be the way SU should be enabled, but I could not get agreement in the project to commit those patches (one reason being, that NetBSD used the tunefs method and that FreeBSD should not diverge, IIRC). Anyway, my patches do still exist and apply - but the the addition of journalling changed the picture. Now there are 3 modes: plain UFS, UFS with SU and UFS with SU+, and I have not attempted to add support for SU+. I had maintained these patches some time after last using it, I guess they cleanly apply to FreeBSD-10, not sure about later versions. And as I said, they did not even try to cover SU+ ... Regards, STefan From owner-freebsd-fs@freebsd.org Sat Oct 28 19:41:19 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 358CEE4BB1A for ; Sat, 28 Oct 2017 19:41: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 mx1.freebsd.org (Postfix) with ESMTPS id 2428B7E57C for ; Sat, 28 Oct 2017 19:41:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v9SJfHf6078888 for ; Sat, 28 Oct 2017 19:41:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 223287] posix_fallocate(2) attempts to allocate impossibly large files and cannot be killed on ZFS Date: Sat, 28 Oct 2017 19:41:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-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.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2017 19:41:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D223287 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-bugs@FreeBSD.org |freebsd-fs@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Oct 28 22:27:58 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DFE9AE4F014 for ; Sat, 28 Oct 2017 22:27:58 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (chez.mckusick.com [70.36.157.235]) (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 C63EF825A0; Sat, 28 Oct 2017 22:27:58 +0000 (UTC) (envelope-from mckusick@mckusick.com) Received: from chez.mckusick.com (localhost [IPv6:::1]) by chez.mckusick.com (8.15.2/8.15.2) with ESMTP id v9SMPDCZ074228; Sat, 28 Oct 2017 15:25:13 -0700 (PDT) (envelope-from mckusick@chez.mckusick.com) Message-Id: <201710282225.v9SMPDCZ074228@chez.mckusick.com> From: Kirk McKusick To: Mark Johnston Subject: Re: softdep as a mount(8) option cc: freebsd-fs@FreeBSD.org In-reply-to: <20171027153859.GC2385@raichu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <74226.1509229513.1@chez.mckusick.com> Date: Sat, 28 Oct 2017 15:25:13 -0700 X-Spam-Status: No, score=-1.4 required=5.0 tests=BAYES_00,MISSING_MID, UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on chez.mckusick.com X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2017 22:27:59 -0000 > Date: Fri, 27 Oct 2017 11:39:00 -0400 > From: Mark Johnston > To: freebsd-fs@FreeBSD.org > Subject: softdep as a mount(8) option > > Hi, > > I'd like to finally enable the use of SU (not SU+J) on some small UFS > filesystems. The fact that SU is enabled using a flag in the superblock > poses a problem for me, however: the systems containing these > filesystems may at any time be repurposed to run a kernel that supports > SU but contains bugs[*] that render it unusable. I therefore can't > persistently enable SU in these systems. > > I'm wondering if it would be possible to enable SU using a mount > option rather than with a persistent flag. fsck_ffs conditionalizes some > of its logic on whether SU is configured - is this necessary for > correctness? That is, if I run fsck on an unclean filesystem that had > been mounted with SU, and fsck runs as though SU hadn't been configured, > what problems might arise? > > [*] These bugs are a result of local modifications and aren't in > FreeBSD. While it is safe and possible to add soft-updates (but not journalled soft updates) as a mount option, it means that fsck will not know that soft updates were in use, so it will always run in full (slow) mode at boot time. This is why I have not added it as an option. Kirk McKusick From owner-freebsd-fs@freebsd.org Sat Oct 28 23:49:50 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3857CE50E9C for ; Sat, 28 Oct 2017 23:49:50 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-io0-f171.google.com (mail-io0-f171.google.com [209.85.223.171]) (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 0A0F0B6C; Sat, 28 Oct 2017 23:49:49 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-io0-f171.google.com with SMTP id 134so19885906ioo.0; Sat, 28 Oct 2017 16:49:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=7XDEBJh5b/hGKN0UiTWitGd9cbqgi3YytbWgbx3TZfk=; b=J6hpdZlWuzau/VhkbnLiRcD+UbX/hsfnpj0Qi35TBQuwijb11Zbgix+7RvJu8VnfbE SgXTKtqXYJD7gqRonoj0iDr/AMVEY0agKAFKq8UaxqX8BMqKfY+rFMW0yRe2HVn+0PkI YA8x3gX6iqvPYpHLIaxzmKPmGsoh2DIxEERumMeZ28O1BtfDxeLiTJxO0vQ1t4JRDESs RDYY5T6KjgwLK4/JgIO/RK0Zd+0ztub4/1TNoBSVOch2OHpawVXOXxZqvYLxE32EA7CP G824j9BD2+uQUuRCyQsGs5WZdayZTZzUKHvXwXjiqQqhGoQA5/jcgneF2uDiXu0pE8NK Vl8g== X-Gm-Message-State: AMCzsaWc59gq3bIaZtjsE66SvU4vjOQn7rkM+Tcb0nMzCuraIDvqJ8z6 N9v2ZXlcN90OGZoB2tTUqdc2aaRL X-Google-Smtp-Source: ABhQp+RMJLV4gVc3uXOOSM+98hEfW6D71vnilhay6kuKJNOhHgz/f09Xs2KDWJcX95bHXzN6xQascw== X-Received: by 10.36.29.208 with SMTP id 199mr680648itj.40.1509234099913; Sat, 28 Oct 2017 16:41:39 -0700 (PDT) Received: from mail-io0-f180.google.com (mail-io0-f180.google.com. [209.85.223.180]) by smtp.gmail.com with ESMTPSA id r124sm261273ita.13.2017.10.28.16.41.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 28 Oct 2017 16:41:39 -0700 (PDT) Received: by mail-io0-f180.google.com with SMTP id b186so19867929iof.8; Sat, 28 Oct 2017 16:41:39 -0700 (PDT) X-Received: by 10.36.1.136 with SMTP id 130mr655243itk.119.1509234099608; Sat, 28 Oct 2017 16:41:39 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.2.164.130 with HTTP; Sat, 28 Oct 2017 16:41:38 -0700 (PDT) In-Reply-To: <201710282225.v9SMPDCZ074228@chez.mckusick.com> References: <20171027153859.GC2385@raichu> <201710282225.v9SMPDCZ074228@chez.mckusick.com> From: Conrad Meyer Date: Sat, 28 Oct 2017 16:41:38 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: softdep as a mount(8) option To: Kirk McKusick Cc: Mark Johnston , freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Oct 2017 23:49:50 -0000 On Sat, Oct 28, 2017 at 3:25 PM, Kirk McKusick wrote: > While it is safe and possible to add soft-updates (but not journalled > soft updates) as a mount option, it means that fsck will not know that > soft updates were in use, so it will always run in full (slow) mode at > boot time. This is why I have not added it as an option. Hi Kirk, Would it be possible to add a bit, like the dirty bit, that fsck can use to determine that the last mount of a filesystem used SU? That way we can retain fsck performance at the same time as enabling mount-time choice of SU. Best, Conrad