From owner-freebsd-fs@freebsd.org Sun Jul 29 21:00:48 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C4AD10633E1 for ; Sun, 29 Jul 2018 21:00:48 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D852979B98 for ; Sun, 29 Jul 2018 21:00:47 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9D71F10633DE; Sun, 29 Jul 2018 21:00:47 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7BD1A10633DB for ; Sun, 29 Jul 2018 21:00:47 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D36579B8A for ; Sun, 29 Jul 2018 21:00:47 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6B6A319E67 for ; Sun, 29 Jul 2018 21:00:46 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6TL0kcI076251 for ; Sun, 29 Jul 2018 21:00:46 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6TL0kXi076233 for fs@FreeBSD.org; Sun, 29 Jul 2018 21:00:46 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201807292100.w6TL0kXi076233@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: fs@FreeBSD.org Subject: Problem reports for fs@FreeBSD.org that need special attention Date: Sun, 29 Jul 2018 21:00:46 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jul 2018 21:00:48 -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 | 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 6 problems total for which you should take action. From owner-freebsd-fs@freebsd.org Mon Jul 30 06:38: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 EC975104C187 for ; Mon, 30 Jul 2018 06:38:25 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vtr.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E3D08A8B1 for ; Mon, 30 Jul 2018 06:38:24 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp59-167-167-3.static.internode.on.net [59.167.167.3]) by vtr.rulingia.com (8.15.2/8.15.2) with ESMTPS id w6U6cDro032634 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Mon, 30 Jul 2018 16:38:19 +1000 (AEST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id w6U6c5rX061721 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 30 Jul 2018 16:38:07 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id w6U6c5No061720; Mon, 30 Jul 2018 16:38:05 +1000 (AEST) (envelope-from peter) Date: Mon, 30 Jul 2018 16:38:04 +1000 From: Peter Jeremy To: Robert Clausecker Cc: freebsd-fs@freebsd.org Subject: Re: badsect(8) is gone -- what now? Message-ID: <20180730063804.GA4409@server.rulingia.com> References: <20180727130743.GB45967@fuz.su> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline In-Reply-To: <20180727130743.GB45967@fuz.su> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2018 06:38:26 -0000 --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2018-Jul-27 15:07:43 +0200, Robert Clausecker wrote: >Is there any way the kernel interface for badsect(8) or a utilitiy >fulfilling a similar purpose is going to come back? I understand that >kernel support was removed due to possible misuse of mknod(S_IFMT) >leading to crashes [1], but there really ought to be some way to mark a >sector as bad if the disk doesn't want to do it for you. All modern disks do bad sector mapping in the drive firmware. In general, if you disk reaches a point where it can't remap a visibly bad sector then the drive's internal set of spare blocks is exhausted and the disk is about to fail completely. The recommended solution is to replace the disk. Have you looked at the disk's SMART stats (using eg ports/sysutils/smartmontools= )? One approach I've used in the past is to create a file covering the bad sector(s), mark it immutable and stash it somewhere where you don't attempt to read it. --=20 Peter Jeremy --bg08WKrSYDhXBjb5 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAltesktfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi CzTYbQ//SfJwmfYr02IWfe/ahTmy38QYH7RPlGh4y1g/CxhYVDxLotGdvRYuC8oF Ua+q2huRQEC23qc+aefvS+kA+Qi4TMBSohU0NjsFH0bEzaTGwvEA3s1j0pB+1nxb 3Kn+eyRxNks68ADXxo7HYeNw19fc7XU3hf8BA/vxHkLzbMFXVUyodJRtw59bpqJC 9qNz96Y00J16NBQFIt2jJvvqRRLuZD/Kp0jqahj3OG91TidJmgrTWrsuIq9TkqtB J+FGo9PVF1t4o/dHAnr93OotFNefcsRePX3bRlNyVBOSoVaAxID541UujiPcXSn3 N5IS66M5lf6nESdJCvS3mchlRhNWXIa7D8qyiRweJfyYGJRRG4g4DxQvNfPKjz90 WmaHNKnWtw+RW78W5YkdOJyfFu11lYJ2zlDtgE2txJEgAubVkkooAT8HPKYglWHb NLAQ0RpMifPYq2bq3UK+b6VZ7ngljWKymfiw5D5dd47M8lhiSbyuOAmxr5x4LL4m QMSPPABpKqJL8WGAe3GRqdlbVPJOB6BDjPi6DDS65UTEbbjJX5waDyaeGX/6ycfI W6SUtI3EgyFVLbLvcPg4ddICXPV5PLl3dlOd7f9VPr/jd1uBC+A/DvQmZ0FLhYOv xwFAchPTMfs+kQCBlq14JBZmvuK8XPT39KpsM5xZ8AhQwzKwiwM= =V4vp -----END PGP SIGNATURE----- --bg08WKrSYDhXBjb5-- From owner-freebsd-fs@freebsd.org Mon Jul 30 06:44: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 DC529104C406 for ; Mon, 30 Jul 2018 06:44:05 +0000 (UTC) (envelope-from rob@nofocus.org) Received: from mail-qt0-x22a.google.com (mail-qt0-x22a.google.com [IPv6:2607:f8b0:400d:c0d::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 80C168ABEE for ; Mon, 30 Jul 2018 06:44:05 +0000 (UTC) (envelope-from rob@nofocus.org) Received: by mail-qt0-x22a.google.com with SMTP id c15-v6so11007595qtp.0 for ; Sun, 29 Jul 2018 23:44:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nofocus.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Y2JgKhh3yO6rMvF0H0bWYU50JwZg+f9lAeJ6bHhH5KY=; b=eWPSORF3LcClC3h2O9mi+GnBoH3JeLYfuoI9lkgVzSozVYcj2Kcmb5JNPl0oxJ6HSZ XcfStY3YUQaQj8q7zaelXYinxBFrJrL8P5q8+uzozL+jBqcajmi05TNwpuYX1wSjqEFG bYbTb0q9u86sWwYWDYJC2BAEKIViXdHqsBZG0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Y2JgKhh3yO6rMvF0H0bWYU50JwZg+f9lAeJ6bHhH5KY=; b=H8U/MGX7e+FPtuZwU7y8f92keebO4sQw6gU+wCwoQtTGgOJ8I4kIAXufn9KFDGzWsp 5bsEcy/6A83PExjlt9gm7t6EdulXjb/UbAkyGcjXb2TT7glF5/xSuRY7R+R7yzI0rdsL cSOGn8tQIcG8eScOoT72A5Hkvr/9roNAYjc7kLR0IZPQj/TB257EUCcFi5lxjUfCTjr8 QOIWB9oJg68vXaXUhsbqn7oYXGiZSL0YnFUD/eeIa3VCamsWjwJzOQ5GPgteeS/MI3/6 gp/xivlqeukmzyWGBMVAT1Fu0ot47ebGlE92bGqaO8yj5E8utNxRcsKzQq7J1Uoy74EJ sT4Q== X-Gm-Message-State: AOUpUlG8G1LFFeLq5UvYv97stZjLWa6zegDraMw8G+vbRon3w45RvN06 AXoNAok59Hbbx3p3oQ3e23f2FdR2B2jRYh7hPECCWVOq X-Google-Smtp-Source: AAOMgpdNjJkkeNyAKnvzk7oiU8O21pT0Vlm/WrsYr3jz8NAAuN07/5fM1qTr0IkePPdUrJvgDk5KPcWIWVU+yotj7EQ= X-Received: by 2002:aed:2d63:: with SMTP id h90-v6mr15273239qtd.190.1532933044235; Sun, 29 Jul 2018 23:44:04 -0700 (PDT) MIME-Version: 1.0 References: <20180727130743.GB45967@fuz.su> <20180730063804.GA4409@server.rulingia.com> In-Reply-To: <20180730063804.GA4409@server.rulingia.com> From: Robert Banz Date: Sun, 29 Jul 2018 23:43:53 -0700 Message-ID: Subject: Re: badsect(8) is gone -- what now? To: Peter Jeremy Cc: Robert Clausecker , freebsd-fs@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2018 06:44:06 -0000 And if you=E2=80=99re just trying to recover your data from said disk, try = out =E2=80=98ddrescue=E2=80=99 and dump the partition to a file or another disk= . On Mon, Jul 30, 2018 at 2:38 AM Peter Jeremy wrote: > On 2018-Jul-27 15:07:43 +0200, Robert Clausecker wrote: > >Is there any way the kernel interface for badsect(8) or a utilitiy > >fulfilling a similar purpose is going to come back? I understand that > >kernel support was removed due to possible misuse of mknod(S_IFMT) > >leading to crashes [1], but there really ought to be some way to mark a > >sector as bad if the disk doesn't want to do it for you. > > All modern disks do bad sector mapping in the drive firmware. In general= , > if you disk reaches a point where it can't remap a visibly bad sector the= n > the drive's internal set of spare blocks is exhausted and the disk is abo= ut > to fail completely. The recommended solution is to replace the disk. Ha= ve > you looked at the disk's SMART stats (using eg > ports/sysutils/smartmontools)? > > One approach I've used in the past is to create a file covering the bad > sector(s), mark it immutable and stash it somewhere where you don't attem= pt > to read it. > > -- > Peter Jeremy > From owner-freebsd-fs@freebsd.org Mon Jul 30 21:49:45 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7748E1061EDC for ; Mon, 30 Jul 2018 21:49:45 +0000 (UTC) (envelope-from matthew.ahrens@delphix.com) Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DBCC8639A for ; Mon, 30 Jul 2018 21:49:44 +0000 (UTC) (envelope-from matthew.ahrens@delphix.com) Received: by mail-ua0-x236.google.com with SMTP id p22-v6so8898157uao.7 for ; Mon, 30 Jul 2018 14:49:44 -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=hlYta6B3r0Azt5Yf1m64h9Cq6OoDCJfuTM0Piwqani8=; b=LnA7XuKiyIOKki99eO19qMZZOdDBuMRXg9bKOc0DQRTUNAVbvLt6i8DQRyOADRM5Y1 4dgmCIyIlUymMT0R0N+qzyR6H9QVTH8BMWett0Rsfd/IsLkmDlyKgScXyIqiar4AvOkB sfnDBqnolp7bwZZLGM/ABatZLYJzcRsTNrUZw= 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=hlYta6B3r0Azt5Yf1m64h9Cq6OoDCJfuTM0Piwqani8=; b=eikSIcjiuBfTQ+vUxCzxOCDblfouCq881e75cp4t+40LDtuufMTBq5rCCWbSl+4hqO VLHtexjD9H7TU5wXn3ivbCfwRiXq5gfvxTKstvrP5nj+GA2829KeuZ7gJ0VFEeEEoMh4 YnEQBHptrT9U+iI4k3G9ntl5IDyWsoc9O0fcjPTmepUbWvP1XZ58zhIa1AqmZIvwcUH8 Y1bQuOGaRjRFhK3ldhlm/CFrXpDTY0OHGGGDqCRh/pL9vdW3XjB4nSq/Ik8V6379sNJ3 Rewi+pQGw2OlB2gPpf0eJYGPjA+ST0twTWCn/LBkHg41vgHsiGKGNTKERzKoTFU6+Vx/ 8kKw== X-Gm-Message-State: AOUpUlE+AnUybYQkdjm+gzsS2QyvReJ+ThWGwEoOt+wX+aagJk0v+dhf 9aH6xCQOtAwI9HTbrHRe0+4HN7R/froqAuYvotGmpQ== X-Google-Smtp-Source: AAOMgpd9F9oW9M1HrPbAgJa8Ykuj0HV+sivp8en/cebpfXxA/jJqEsiL7cm7CCl7+iSYD+YD6wbP2zenEs9uvI2GeNw= X-Received: by 2002:ab0:4505:: with SMTP id r5-v6mr13650684uar.77.1532987384263; Mon, 30 Jul 2018 14:49:44 -0700 (PDT) MIME-Version: 1.0 From: Matthew Ahrens Date: Mon, 30 Jul 2018 14:49:33 -0700 Message-ID: Subject: OpenZFS Developer Summit 2018 - Speakers announced To: 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.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2018 21:49:45 -0000 The sixth annual OpenZFS Developer Summit will be held in San Francisco, *September 10-11, 2018*. Everyone interested in OpenZFS is invited to participate, and registration is now open. See http://www.open-zfs.org/wiki/OpenZFS_Developer_Summit for all of the details, including slides and videos from previous years' conferences. The goals of the event are 1. to foster cross-community discussions of OpenZFS work and 2. to make progress on some of the projects we have proposed, at a 1-day hackathon. We have a great lineup of talks this year: TitleSpeakerCompany State of the Union Matt Ahrens Delphix ZIO Pipeline George Wilson Delphix zrepl , a one-stop ZFS replication solution Christian Schwartz Student Observing and Monitoring ZFS Metrics Using Open Source Tools Richard Elling Newisys Managing ZVOLs with vzvol Samantha Smith Moogsoft ZFS Hardware Acceleration with QAT Weigang Li Intel ZoL Releases Tony Hutter LLNL Device Removal Matt Ahrens Delphix iRAID Shailendra Tripathi Tegile, a Western Digital Brand TitleSpeakerCompany Log Spacemap: Flushing algorithm and performance Serapheim Dimitropoulos Delphix DRAID Rebuild Performance Carles Mateo Newisys Send Dedup Paul Dagnelie Delphix Allocation Classes Don Brady Delphix Vdev Properties Allan Jude Klara Systems This event is only possible because of the efforts and contributions of the community of developers and companies that sponsor the event. Special thanks to our early Diamond sponsors: Delphix , Datto , and OsNexus . Additional sponsorship opportunities are available. Please see the website for details and send email to Karyn.Ritter@delphix.com if you have any questions. --matt From owner-freebsd-fs@freebsd.org Tue Jul 31 01:04:39 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 B36511067145 for ; Tue, 31 Jul 2018 01:04:39 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail110.syd.optusnet.com.au (mail110.syd.optusnet.com.au [211.29.132.97]) by mx1.freebsd.org (Postfix) with ESMTP id 5506070E6E for ; Tue, 31 Jul 2018 01:04:37 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from [192.168.0.102] (c110-21-101-228.carlnfd1.nsw.optusnet.com.au [110.21.101.228]) by mail110.syd.optusnet.com.au (Postfix) with ESMTPS id D011D10937D; Tue, 31 Jul 2018 11:04:15 +1000 (AEST) Date: Tue, 31 Jul 2018 11:04:15 +1000 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Robert Clausecker cc: freebsd-fs@freebsd.org Subject: Re: badsect(8) is gone -- what now? In-Reply-To: <20180727130743.GB45967@fuz.su> Message-ID: <20180731101215.P2056@besplex.bde.org> References: <20180727130743.GB45967@fuz.su> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.2 cv=EseilWUA c=1 sm=1 tr=0 a=PalzARQSbocsUSjMRkwAPg==:117 a=PalzARQSbocsUSjMRkwAPg==:17 a=kj9zAlcOel0A:10 a=V3VVewBL9YRdEGTVxaoA:9 a=CjuIK1q_8ugA:10 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jul 2018 01:04:39 -0000 On Fri, 27 Jul 2018, Robert Clausecker wrote: > I recently tried to use badsect(8) to salvage a slightly broken disk > with some janky sectors which the drive doesn't remap but still likes to > complain about, just to find out that kernel support for badsect(8) is > no longer available in FreeBSD 11.2. This is an annoying situation as I > have no way to stop these sectors from being used otherwise. > > Is there any way the kernel interface for badsect(8) or a utilitiy > fulfilling a similar purpose is going to come back? I understand that > kernel support was removed due to possible misuse of mknod(S_IFMT) > leading to crashes [1], but there really ought to be some way to mark a > sector as bad if the disk doesn't want to do it for you. badsect(8) was removed when I pointed out that removing the kernel support for it was a bug. The bug is larger now. You can hide the bad sectors manually no worse than badsect(8)+fsck did after first finding them and allocating them in files. This is much harder to do systematically than with badsect, but if you just wait for bad sectors to develop and chmod files to 000 and move them out of the way (and don't try to recover good sectors in then), the result is not much different than with badsect. Root can still read these files, so there tree walks might stumble over them. If a bad sector develops in metdata, then this doesn't work so well, but neither did badsect. Most metadata is for inodes and bad sectors for inodes cannot be handled. In practice, the slowest part might be finding the bad sectors. The whole disk must be read, and i/o on the bad sectors is especially slow due to retries. I once remapped bad sectors on mere 30GB and 100GB disks with a few thousand bad sectors, by reading and writing all sectors and hoping that the disk reallocated the bad ones (it mostly did at first on the 30GB disk, and mostly failed on the 80GB disk, but the 30GB eventually became unusable while the 80GB disk still works perfectly except for 1 region of ~20GB in the middle). Bad sectors must be read and written 1 sector a time to locate them, and this is already much slower than reading many at a time. I used dd to locate problem areas on the disks, and a simple utility do 1-sector reads and writes in these areas. The utility prints sector numbers in a form more useful than kernel or dd error messages. Bruce From owner-freebsd-fs@freebsd.org Tue Jul 31 21:23: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 792CD10657A4 for ; Tue, 31 Jul 2018 21:23:56 +0000 (UTC) (envelope-from jwd@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (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 341767E083 for ; Tue, 31 Jul 2018 21:23:56 +0000 (UTC) (envelope-from jwd@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 821) id 1245B1B0F6; Tue, 31 Jul 2018 21:23:56 +0000 (UTC) Date: Tue, 31 Jul 2018 21:23:56 +0000 From: John To: FreeBSD-FS Subject: Nfsroot .zfs/snapshot mounted on different mount? Message-ID: <20180731212355.GA19206@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jul 2018 21:23:56 -0000 --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi Folks, I ran into something today I didn't expect and was wondering how it is accomplished - or something is going on in the NFS code I've never seen. I have some remote nfs booted systems where the OS lives on ZFS volumes (the client is linux):. 10.121.56.21:/vol/nfsbt_sysgpu01 100G 4.7G 96G 5% / After installing the latest gpu drivers I was asked to compare a few things and went into the /.zfs/snapshot directory as typical. However, I then noticed a 2nd nfs mount had appeared: 10.121.56.21:/vol/nfsbt_sysgpu01/.zfs/snapshot/rb_20180727-185554_drivers 100G 4.7G 96G 5% /.zfs/snapshot/rb_20180727-185554_drivers To my knowledge, I have no auto-mounter that could have done the mount. I'm curious where this is hooked in. The server is: FreeBSD 11.1-STABLE #11 r327104: Sat Dec 23 08:19:22 EST 2017 with standard nfsv3 exports. Other than this curiousness the system is flawless. Thanks, John --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQF8BAEBCgBmBQJbYNNqXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwNDBGOTgxNzM0NzQ3OEFBNDYyODNGQzVC NjI0OTlBMTQyNEY3RjgxAAoJELYkmaFCT3+BJlMH/0ZCYBMrsLSW/ls5JNADaILF QuLLtduyP3DOkpITukNnOM54hc+2YRd+Hjv5uJkovOzoPiRbzuDw5++Ol0eYlAJM 5ts7gp/cbjG+H+iukNab8G8lBKsUP0Z4plgAlG1ubJCEonTIB/AzUXe2CEeYdYr0 E7NnnjsCbcMs9zBU7ZxFIsqeFAEascrSDUMKyPCAKHnVMcKs9R84uaD4vCRhSSVg b5aFRyCbx69S8+WIgjBIGbVxCXbZEJJ1ZBtvTelttqlhPoFmjzcrPSc/YeCW7Q3P 8Ta4s+orRdYtO1b0Ma0boEBLpHfoTDlnXGimTT9eFeaqSuK9paJQhTKuNwCKPPE= =aZeP -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc-- From owner-freebsd-fs@freebsd.org Tue Jul 31 21:32:14 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 AFDD91065AD6 for ; Tue, 31 Jul 2018 21:32:14 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 296717E74B; Tue, 31 Jul 2018 21:32:14 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by mail-lj1-x236.google.com with SMTP id u7-v6so15042848lji.3; Tue, 31 Jul 2018 14:32:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=b/+vVOFuaNykVj1XnMcHciEjNsxy73fs97lB2VdrPQQ=; b=faUMWzCWkJ0CtuN8at6emKVq4ljSkaEQW/wZfPyEDXBvDEzaKxNFdYxGhoxQrPe3Sf z7S10U2IUGqm4WvzXjgYbneczjolvsTkv8CucuwI61nugUzbPygFgmqCxiRl555Rj+am YUU3dEznn4iBDtj0yoFoSQlYCU68SaRcOWEwgvngVrRGtDT4VuEURycAh64zHtuUvF+7 hNXqA4IlThR5+1dEt5qhqmDmNe33vSjynJ2cA6pwdOmsl/t/Q3sAJtHXwyvQhdzLS6ZL KoptORNkq/OE9uP3597+ZW982iqnetkbcRIkrZ+/zprSF+c8ZKLF4FGGZ3OzMARZrzo+ Qstw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=b/+vVOFuaNykVj1XnMcHciEjNsxy73fs97lB2VdrPQQ=; b=H5SZZNnp6nnnkcDgZIuyR4eQL7XL7qzJdvJdMwQYRCOCMLfcQpxh//2EQ0Wlye0orf vdYcnXqDYq0kyFDvKBe2Uv6piXsc0js/oJFeeUQrRzLaidVwWxUVbEnmvV0+C+dCKdPo qw+WSZSr2Vh7cxDMeE/bY/vGcNPieuUp0tZz9abUl6HlXlYb8vJlY5v3r7xrt52DjG7Y AywFNNPrjpCGyTf1td6Z5B5Z48i7kEy+EyeR0bWigwRete3z0GwMyUOVUFqhGFgvqh5H djASptv4JXimdsLxJqEh56TU+46uPby72FN5JPZ15wbOw//8mG2YJyssVCkWY0c7hFO1 E6SQ== X-Gm-Message-State: AOUpUlHHeOhDcIaJNQkmd4jmonYpd/zJTfw3CsL26oxRf/17I17tqPxz DO4tMuSEQVRPzXN/v2qqJ5hLodT2sH8QJlnol2EsQw== X-Google-Smtp-Source: AAOMgpfwgOF1tk+eFvQTEzxKDmLhioOK1Y/wtUIxgwvvZk1A1H50WYB8iztUt0wdZad21sIJxfz2GpCkvanfa27Pf7U= X-Received: by 2002:a2e:89c5:: with SMTP id c5-v6mr18649102ljk.19.1533072732671; Tue, 31 Jul 2018 14:32:12 -0700 (PDT) MIME-Version: 1.0 References: <20180731212355.GA19206@FreeBSD.org> In-Reply-To: <20180731212355.GA19206@FreeBSD.org> From: Freddie Cash Date: Tue, 31 Jul 2018 14:32:01 -0700 Message-ID: Subject: Re: Nfsroot .zfs/snapshot mounted on different mount? To: John Cc: FreeBSD Filesystems Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jul 2018 21:32:14 -0000 On Tue, Jul 31, 2018 at 2:25 PM John wrote: > Hi Folks, > > I ran into something today I didn't expect and was wondering > how it is accomplished - or something is going on in the NFS > code I've never seen. > > I have some remote nfs booted systems where the OS lives > on ZFS volumes (the client is linux):. > > 10.121.56.21:/vol/nfsbt_sysgpu01 100G 4.7G 96G 5% / > > After installing the latest gpu drivers I was asked to > compare a few things and went into the /.zfs/snapshot directory > as typical. However, I then noticed a 2nd nfs mount had > appeared: > > 10.121.56.21:/vol/nfsbt_sysgpu01/.zfs/snapshot/rb_20180727-185554_drivers > 100G 4.7G 96G 5% /.zfs/snapshot/rb_20180727-185554_drivers > > To my knowledge, I have no auto-mounter that could have done > the mount. I'm curious where this is hooked in. > > The server is: > > FreeBSD 11.1-STABLE #11 r327104: Sat Dec 23 08:19:22 EST 2017 > > with standard nfsv3 exports. Other than this curiousness > the system is flawless. > Not sure about the NFS side of things, but the FreeBSD kernel has auto-mounted the .zfs/snapshot/ filesystem upon access from the first ZFS import into FreeBSD 7. Depending on how the NFS mount is setup, this may be carrying-over from the kernel auto-mount. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-fs@freebsd.org Thu Aug 2 03:21:02 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 C0639105332E for ; Thu, 2 Aug 2018 03:21:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5CE929681D for ; Thu, 2 Aug 2018 03:21:02 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 21D961053329; Thu, 2 Aug 2018 03:21:02 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1057F1053328 for ; Thu, 2 Aug 2018 03:21:02 +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 A664096815 for ; Thu, 2 Aug 2018 03:21:01 +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 114E1230C3 for ; Thu, 2 Aug 2018 03:21:01 +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 w723L0mE043521 for ; Thu, 2 Aug 2018 03:21:00 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w723L0k1043519 for fs@FreeBSD.org; Thu, 2 Aug 2018 03:21:00 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229986] Terminating virtualbox or ctld + zfs scrub + gstat leads to deadlock Date: Thu, 02 Aug 2018 03:21:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-RELEASE X-Bugzilla-Keywords: regression 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: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: assigned_to keywords 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2018 03:21:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229986 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |fs@FreeBSD.org Keywords| |regression CC| |virtualization@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Aug 2 08:44:16 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 BF77E105EF5D for ; Thu, 2 Aug 2018 08:44:15 +0000 (UTC) (envelope-from info@createandlisting.tech) Received: from mail.createandlisting.tech (mail.createandlisting.tech [205.147.101.13]) by mx1.freebsd.org (Postfix) with ESMTP id 172CA7D35E for ; Thu, 2 Aug 2018 08:44:14 +0000 (UTC) (envelope-from info@createandlisting.tech) Received: from [127.0.0.1] (unknown [27.97.244.89]) by mail.createandlisting.tech (Postfix) with ESMTPA id E50F74B4C5 for ; Thu, 2 Aug 2018 14:09:29 +0530 (IST) Message-Id: Mime-Version: 1.0 From: Admin To: freebsd-fs@freebsd.org Subject: Getting Hundreds of Clients Every Month from Your Website? Date: Thu, 2 Aug 2018 14:09:22 +0530 X-Bounce-Tracking-Info: Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2018 08:44:16 -0000 Hi I hope you are doing well=2E Do you want to see your Business website first page of the Google? Are you = looking for SEO service to rank your Website organically in Top 5 positions= of Google page 1? We provide guarantee to have more than 50% of the keywor= ds on Google page 1 within the projected Google page 1 time line, so let us= provide you the Google page 1 ranking=2E There will be no set up fee or any other hidden charge=2E So you just have = to pay your monthly SEO fee and no need to sign any contract=2E Please revert back to us if interested to know more information related to = price, past results & our proposal=2E I will look forward to your reply=2E Warm Regards, Melissa Bell SEO Consultant DISCLAIMER: This is an advertisement and a promotional email strictly on th= e guidelines of CAN-SPAM act of 2007=2E We have clearly mentioned the sourc= e mail-id of this` mail, also clearly mentioned the subject lines and they = are in no way misleading in any form=2E We have found your mail address thr= ough our own efforts on the web search and not through any illegal way= =2E If you find this mail unsolicited, please reply with" Unsubscribe" in t= he subject line and we will take care that you do not receive any further p= romotional mail From owner-freebsd-fs@freebsd.org Thu Aug 2 16:30:58 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 A6BAD106BD71 for ; Thu, 2 Aug 2018 16:30:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 438308F8C9 for ; Thu, 2 Aug 2018 16:30:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0854D106BD6F; Thu, 2 Aug 2018 16:30:58 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EB251106BD6E for ; Thu, 2 Aug 2018 16:30: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 8A4BF8F8C3 for ; Thu, 2 Aug 2018 16:30:57 +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 D8B5F29FC3 for ; Thu, 2 Aug 2018 16:30:56 +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 w72GUu47043132 for ; Thu, 2 Aug 2018 16:30:56 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w72GUuCl043131 for fs@FreeBSD.org; Thu, 2 Aug 2018 16:30:56 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229986] Terminating virtualbox or ctld + zfs scrub + gstat leads to deadlock Date: Thu, 02 Aug 2018 16:30:56 +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.2-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rgrimes@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2018 16:30:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229986 Rodney W. Grimes changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rgrimes@FreeBSD.org --- Comment #6 from Rodney W. Grimes --- If you have not done so, I would highly encorage you to reduce the max size= of the arc cache and see if your problems go away. Reduce it by the size of a= ny VM's your running in bhyve or virtual box. Add something like this to /boot/loader.conf: vfs.zfs.arc_max=3D6442450944 --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Aug 2 16:37: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 1DEE8106C06F for ; Thu, 2 Aug 2018 16:37:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id AF4548FFF6 for ; Thu, 2 Aug 2018 16:37:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 74534106C06C; Thu, 2 Aug 2018 16:37:27 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63135106C06B for ; Thu, 2 Aug 2018 16:37:27 +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 049FE8FFF0 for ; Thu, 2 Aug 2018 16:37:27 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 639D12A012 for ; Thu, 2 Aug 2018 16:37:26 +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 w72GbQTb058450 for ; Thu, 2 Aug 2018 16:37:26 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w72GbQd9058449 for fs@FreeBSD.org; Thu, 2 Aug 2018 16:37:26 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229986] Terminating virtualbox or ctld + zfs scrub + gstat leads to deadlock Date: Thu, 02 Aug 2018 16:37:26 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: d8zNeCFG@aon.at X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2018 16:37:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229986 --- Comment #7 from Martin Birgmeier --- I am already doing that, but the deadlock described here happens nonetheles= s. What gets better is that the machine does not lock up completely (see comme= nt #4). -- Martin --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Thu Aug 2 19:10:42 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 4661A104C033 for ; Thu, 2 Aug 2018 19:10:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C96D476DAE for ; Thu, 2 Aug 2018 19:10:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7B0B3104C030; Thu, 2 Aug 2018 19:10:41 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 65421104C02E for ; Thu, 2 Aug 2018 19:10:41 +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 E9DCC76DAB for ; Thu, 2 Aug 2018 19:10:40 +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 F3C992B4BD for ; Thu, 2 Aug 2018 19:10:39 +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 w72JAdtu072077 for ; Thu, 2 Aug 2018 19:10:39 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w72JAddO072076 for fs@FreeBSD.org; Thu, 2 Aug 2018 19:10:39 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229986] Terminating virtualbox or ctld + zfs scrub + gstat leads to deadlock Date: Thu, 02 Aug 2018 19:10:39 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.2-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rgrimes@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2018 19:10:42 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229986 --- Comment #8 from Rodney W. Grimes --- (In reply to Martin Birgmeier from comment #7) Are you sure that you are not in a memory deadlock? You say you did apply an arc cache limit, how much did you reduce it buy? = How big are your VM's? If you run top what is your free memory space? Is your system using any swap at all? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Aug 3 03:53:25 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 8D5A8105C0B1 for ; Fri, 3 Aug 2018 03:53:25 +0000 (UTC) (envelope-from andyf@andyit.com.au) Received: from alpine.spintel.net.au (alpine.spintel.net.au [IPv6:2407:e400:1::b]) (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 113048EDED for ; Fri, 3 Aug 2018 03:53:24 +0000 (UTC) (envelope-from andyf@andyit.com.au) Received: from drunkfish.andyit.com.au (210-1-210-40-cpe.spintel.net.au [210.1.210.40]) by alpine.spintel.net.au (Postfix) with ESMTPS id 9DBEA4C2903 for ; Fri, 3 Aug 2018 13:52:42 +1000 (AEST) Received: from snuggles.andyit.com.au (snuggles.andyit.com.au [172.22.2.2]) by drunkfish.andyit.com.au (8.15.2/8.15.2) with ESMTP id w733qdac022803 for ; Fri, 3 Aug 2018 13:52:41 +1000 (AEST) (envelope-from andyf@andyit.com.au) Message-ID: <5B63D187.2070709@andyit.com.au> Date: Fri, 03 Aug 2018 13:52:39 +1000 From: Andy Farkas User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120614 Thunderbird/13.0 MIME-Version: 1.0 To: freebsd-fs@freebsd.org Subject: Re: badsect(8) is gone -- what now? References: <20180727130743.GB45967@fuz.su> <20180731101215.P2056@besplex.bde.org> In-Reply-To: <20180731101215.P2056@besplex.bde.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Aug 2018 03:53:25 -0000 On 31/07/2018 11:04, Bruce Evans wrote: > In practice, the slowest part might be finding the bad sectors. I have some Maxtor XT-4380E disks and they have the bad block table printed on the top of the drive ;) -andyf From owner-freebsd-fs@freebsd.org Fri Aug 3 08:57: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 273431062AB3 for ; Fri, 3 Aug 2018 08:57:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A278E77BF1 for ; Fri, 3 Aug 2018 08:57:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6497A1062AB1; Fri, 3 Aug 2018 08:57:07 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 42A4D1062AB0 for ; Fri, 3 Aug 2018 08:57:07 +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 C459277BEF for ; Fri, 3 Aug 2018 08:57: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 mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 18989A8B7 for ; Fri, 3 Aug 2018 08:57:06 +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 w738v5NQ047714 for ; Fri, 3 Aug 2018 08:57:05 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w738v5o2047713 for fs@FreeBSD.org; Fri, 3 Aug 2018 08:57:05 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229986] Terminating virtualbox or ctld + zfs scrub + gstat leads to deadlock Date: Fri, 03 Aug 2018 08:57: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.2-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: d8zNeCFG@aon.at X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Aug 2018 08:57:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229986 --- Comment #9 from Martin Birgmeier --- Actually I am quite sure that the system *is* in a kind of memory deadlock = at least in the case where it ultimately gets stuck completely (comment #4). In that case, if I remember correctly, it also used quite some swap (around 5%= of 20G configured). But for the issue with scrubbing interacting badly with shutting down VMs a= nd stopping ctld, this happens without too much memory pressure. Specifically, I have: - 16G main memory; this initially gives vfs.zfs.arc_max: 15371956224, which= is high, considering that dmesg.boot shows real memory =3D 17179869184 (16384 MB) avail memory =3D 16344322048 (15587 MB) - Then use sysctl vfs.zfs.arc_max=3D9000000000 - The VM run directly on this machine has 3G simulated physical memory The scrub has completed in the meantime, and I don't really want to restart= it, having taken 360 hours in total, and with it being very taxing on the disks= . So it is difficult to replay the scenario now. However, what is still happening and may be related to memory pressure agai= n: When I shut down ctld after many hours of operation of this machine using 'service ctld onestop' (see comment #2), in contrast to 11.1 this operation= may take several minutes. I believe this happens especially if I forget to redu= ce arc_max. In this case again it looks to me like memory pressure and that the system takes a long time to get some free memory which seems to be required for th= is operation. Maybe it is related to zvols, both the VM running directly on the machine as well as the ctld reference zvols. -- Martin --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Aug 3 09:00:58 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 671A21062DA1 for ; Fri, 3 Aug 2018 09:00:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F0F4177DA5 for ; Fri, 3 Aug 2018 09:00:57 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22f.google.com with SMTP id p81-v6so7440462itp.1 for ; Fri, 03 Aug 2018 02:00:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=h+9WVSTwkbtAKoAmYZUZ0u2/prPLv4WMFcTmdWYc4Us=; b=kwY/k9TLKfT7ZYFghhyDr0n9PebUeRXL74kEerC1qHQY5c+CZGGfctCHuzvKshKurd Nv7ZUcb33VNWqiL/V18NGBCQd5IjqzRaEeLWIVgPsBrYY2J+HYZ+aeQQsdR+7tCqCcv0 U/a1ICFl7yZgV5+c0JC4V2pGBqw2BY+2ML2V7m/4WcnwHQqlbbTxoWD1Wd8hMNsGqCK8 mfHCj07WK6WBBxdclaM7h3iV2+7LVGkJNFz/YuUWOqORcRQgEU0W4vWU3LdWI+GDnzmW uwbRaoJiX2eqJaTRy+K3a6b5XRJoBMxvCVpPaQWimPFwxXXhJmRAwEAq2/l41rYAQLZQ Iszw== 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=h+9WVSTwkbtAKoAmYZUZ0u2/prPLv4WMFcTmdWYc4Us=; b=DC5+nHG9SAQBqdi/BC/wfyQ5B14f9/6K2o5tjpXIR+F/xv7gyYT9J6MaN0uVrX15wJ kBKfWeZrfl8FhuBW8nOPWR9Rb/MCPxrrRB46VxXncvIdqTas9tQgxKZGe+04fiFyX9U4 2j97pUV/x2JvLxV9yx2ISLKDpFQ12tlpYp+sGRPWAdBhvbqqGFY+WBe5JktVzQu/DBFA l/rtful/3WrEnqyzF9JPTZqSWSN3V4EdK0/iGw/t8N/soumgWTmbSyNNwK+L5dEsngr4 AvGOmUh4GSj5sqELrUW7tp01Atf51VaK+w1aAGGrs08JZ9895ujaY9T62vZCDfwC5/kS ts0g== X-Gm-Message-State: AOUpUlEMgOv2P7O+fBIx9uOpU0Sv8LSo0dXFZeahhLAWGd9zBCSKu5DU +zly2yvQ2mmJ0Jy2L1JGuEDKE9rYlVZElP6HhhEe1wOjSW9Qjg== X-Google-Smtp-Source: AAOMgpdZG22us7BL52lT53bP8IWcehH0elJJ87fzLThpEdmraxkAWgj1fPb/VaPFR0GYADgT6SDiW8jU66jXKscbLzo= X-Received: by 2002:a02:a701:: with SMTP id k1-v6mr2624481jam.140.1533286856989; Fri, 03 Aug 2018 02:00:56 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:4485:0:0:0:0:0 with HTTP; Fri, 3 Aug 2018 02:00:56 -0700 (PDT) X-Originating-IP: [86.153.210.77] In-Reply-To: <5B63D187.2070709@andyit.com.au> References: <20180727130743.GB45967@fuz.su> <20180731101215.P2056@besplex.bde.org> <5B63D187.2070709@andyit.com.au> From: Warner Losh Date: Fri, 3 Aug 2018 03:00:56 -0600 X-Google-Sender-Auth: LWd-sewlmjMaLHbVDY0UlvAkR1g Message-ID: Subject: Re: badsect(8) is gone -- what now? To: Andy Farkas Cc: FreeBSD FS Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Aug 2018 09:00:58 -0000 330MB ESDI drives aren't a very modern disk drive... These were king when FreeBSD 1.0 was being released, and we removed ESDI support from the tree around FreeBSD 3 or 4 or so. Warner On Thu, Aug 2, 2018 at 9:52 PM, Andy Farkas wrote: > On 31/07/2018 11:04, Bruce Evans wrote: > > In practice, the slowest part might be finding the bad sectors. >> > > I have some Maxtor XT-4380E disks and they have the bad block > table printed on the top of the drive ;) > > -andyf > > > _______________________________________________ > freebsd-fs@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > From owner-freebsd-fs@freebsd.org Fri Aug 3 09:10: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 A1C3310630C2 for ; Fri, 3 Aug 2018 09:10:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3EE85785BC for ; Fri, 3 Aug 2018 09:10:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 00FE610630C0; Fri, 3 Aug 2018 09:10:59 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E3E6910630BF for ; Fri, 3 Aug 2018 09:10:58 +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 84F82785AB for ; Fri, 3 Aug 2018 09:10:58 +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 CCF87AA2C for ; Fri, 3 Aug 2018 09:10:57 +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 w739AvVp018449 for ; Fri, 3 Aug 2018 09:10:57 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w739AvWI018445 for fs@FreeBSD.org; Fri, 3 Aug 2018 09:10:57 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 229986] Terminating virtualbox or ctld + zfs scrub + gstat leads to deadlock Date: Fri, 03 Aug 2018 09:10:57 +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.2-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: avg@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Aug 2018 09:10:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229986 --- Comment #10 from Andriy Gapon --- Martin, by the way, do you have any non-default settings related to scrub performan= ce? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Fri Aug 3 10:28:44 2018 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E8CDC1064846 for ; Fri, 3 Aug 2018 10:28:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 85E267ADB6 for ; Fri, 3 Aug 2018 10:28:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 4802C1064844; Fri, 3 Aug 2018 10:28:43 +0000 (UTC) Delivered-To: fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 369CA1064843 for ; Fri, 3 Aug 2018 10:28: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 CBAD77ADB4 for ; Fri, 3 Aug 2018 10:28: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 05A5AB54A for ; Fri, 3 Aug 2018 10:28: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 w73ASfAc018513 for ; Fri, 3 Aug 2018 10:28:41 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w73ASfkj018512 for fs@FreeBSD.org; Fri, 3 Aug 2018 10:28: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: fs@FreeBSD.org Subject: [Bug 229986] Terminating virtualbox or ctld + zfs scrub + gstat leads to deadlock Date: Fri, 03 Aug 2018 10:28: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: 11.2-RELEASE X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: d8zNeCFG@aon.at X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Aug 2018 10:28:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229986 --- Comment #11 from Martin Birgmeier --- Andriy, Not really. sysctl.conf is basically empty. Maybe these lines are of intere= st: # PostgreSQL # (see http://people.freebsd.org/~seanc/postgresql/postgresql-kern-autotune= .sh) # tuned to 8 GB for shared mem kern.ipc.shmall=3D2097152 kern.ipc.shmmax=3D8589934592 But postgres is idle on this machine, and ipcs -a shows for shared memory Shared Memory: T ID KEY MODE OWNER GROUP CREATOR CGROUP= =20=20=20=20=20=20 NATTCH SEGSZ CPID LPID ATIME DTIME CTIME=20= =20=20 m 65536 5432001 --rw------- postgres postgres postgres postgres= =20=20=20=20 5 48 727 727 8:00:08 12:27:13 8:00:08 m 196609 0 --rwa------ kdm kdm kdm kdm=20= =20=20=20=20=20=20=20=20 2 7225344 2224 2196 8:00:30 no-entry 8:00:30 m 65538 0 --rwa------ kdm kdm kdm kdm=20= =20=20=20=20=20=20=20=20 2 5242880 2250 2222 8:00:30 no-entry 8:00:30 -- Martin --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-fs@freebsd.org Sat Aug 4 22:07: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 C53EE105478C for ; Sat, 4 Aug 2018 22:07:30 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (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 5B21E8A701 for ; Sat, 4 Aug 2018 22:07:30 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fm4hs-000Lfn-6u; Sat, 04 Aug 2018 23:07:28 +0100 Date: Sat, 4 Aug 2018 23:07:28 +0100 From: Gary Palmer To: Dmitry Morozovsky Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS backup Q: send/recv and mountpoint property Message-ID: <20180804220727.GA83288@in-addr.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Aug 2018 22:07:30 -0000 On Sun, Jul 22, 2018 at 09:14:05PM +0300, Dmitry Morozovsky wrote: > Colleagues, > > still stuck in compiling stable procedure. > > Prerequisites: > > - some servers, all on ZFS, with layout such as > machine -> unique pool name, usually 2-letters, say, hm and im > > - zfs layouts like > > hm/R/${fs}, like > hm/R > hm/R/usr > hm/R/usr/local > hm/R/var > hm/R/home > etc, where hm/R has property mountpoint=/ and others just inherit it > > > - on servers, zfs allows for non-root user to make snapshots, hold, etc, like > > Local+Descendent permissions: > group operator hold,send,snapshot > > - zfs send -R [-i pool@prev-snap] pool@now-snap | \ > ssh backupserver 'zfs recv tgpool/B/zfs/srvname' > > Problem: > > 0. on backup (zfs recv) server, I could not > - overwrite mountpoint property (and I'd better avoid it) > - add canmount=off, especially for child filesets, as it's not inherited (which > could be preferred behaviour) > > 1. after backup server reboot, if special manual tweaks did not have place, > filesets from backup images overwrite backup filesets, render it unuseable > > Any hints? > > Or did I missed something trivial? > > Thanks, as usual, in advance! Hi, On my backup server I have two pools, zfsroot and data. I think I set things up, and then exported data so that it's not auto-imported at boot. I then put this in /etc/rc.local zpool import -N -R /backups data It lets the pool import filesystems with paths like / or /home without over-writing the paths on the local system. Regards, Gary