From owner-freebsd-current@freebsd.org Fri Jun 21 20:09:57 2019 Return-Path: Delivered-To: freebsd-current@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 9393115BDF4A for ; Fri, 21 Jun 2019 20:09:57 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lj1-f176.google.com (mail-lj1-f176.google.com [209.85.208.176]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9C48B77171 for ; Fri, 21 Jun 2019 20:09:56 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lj1-f176.google.com with SMTP id 16so7004741ljv.10 for ; Fri, 21 Jun 2019 13:09:56 -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:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UJiUiX7KxlydykNG/SghHxrYGDtvaO2jgHqbY3skqF0=; b=kh04tTkMhcsg9F/CEkBDxUzC5yKqEzSOdVDLjUCr8rYN7z/vuQsgc+vCgtthbtiWYk Zn+UIOI9lL25B/GcHjWhIM+xlWh4Rv8PGlISPVF1WDjCS+PVSm3s8rkU1G/rReXLM1ln oWL1Y8dHpj4sF1R7NGEuwt/jXuViSWb4QoQ4cDCp8Hc5tcrhqufSSiC5EZJ5r3ZGxNnu LcnzTK1hHHCETBrdwWXQNaMQZgoqpbXSzXncrVB+Qk3mfOsnKRZNqjEgm1tvJDADz016 1+UqYilLjRaWAI44JiOvAW1AbzrOG8X3q+8O6JK/xASvr8tyWzO5jy5PuCIScmP8AZ6y o2eA== X-Gm-Message-State: APjAAAVlc7IdrriFjoPNhq+Pka2E7QSElX0gFwnXY7eycebwsNbdyKmr 8dr7Yg2cgazjqZKkApQMf7s187toCKz7tFWwU+DY/jWH X-Google-Smtp-Source: APXvYqy30+AiSdj4avk+Jji3Pfn/Ez7ArntaITPrrIB195DzD/0UR7/KVZ43Wr/p0zna7FoncgLhxY5K72QKbutEhCc= X-Received: by 2002:a2e:6e0c:: with SMTP id j12mr50986543ljc.123.1561147789462; Fri, 21 Jun 2019 13:09:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Alan Somers Date: Fri, 21 Jun 2019 14:09:38 -0600 Message-ID: Subject: Re: Reducing UFS corruption from unclean shutdowns? To: Scott Long Cc: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" X-Rspamd-Queue-Id: 9C48B77171 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of asomers@gmail.com designates 209.85.208.176 as permitted sender) smtp.mailfrom=asomers@gmail.com X-Spamd-Result: default: False [-3.18 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.997,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; IP_SCORE(-1.25)[ip: (-0.42), ipnet: 209.85.128.0/17(-3.43), asn: 15169(-2.33), country: US(-0.06)]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; DMARC_NA(0.00)[freebsd.org]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_TRACE(0.00)[0:+]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: alt3.gmail-smtp-in.l.google.com]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[176.208.85.209.list.dnswl.org : 127.0.5.0]; NEURAL_HAM_SHORT(-0.93)[-0.928,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; FORGED_SENDER(0.30)[asomers@freebsd.org,asomers@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[176.208.85.209.rep.mailspike.net : 127.0.0.17]; R_DKIM_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[asomers@freebsd.org,asomers@gmail.com]; SUBJECT_ENDS_QUESTION(1.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jun 2019 20:09:57 -0000 On Fri, Jun 21, 2019 at 1:56 PM Scott Long wrote: > > > > > On Jun 21, 2019, at 1:49 PM, Alan Somers wrote: > > > > I panic my development VM regularly. Each time, I need to fsck the > > file system. Even if I had run sync(8) just before the panic, I > > frequently find corruption. What should I change to make sync(8) > > work, or at least to make corruption rare? It looks like my root file > > system is using soft-updates+journal. Should I disable those? > > > > What corruption do you regularly see? > > Scott fsck reports various types of errors, all repairable, like "INODE CHECK-HASH FAILED", "FREE BLK COUNT(S) WRONG IN SUPERBLK", "SUMMARY INFORMATION BAD", "BLK(S) MISSING IN BIT MAPS", and "UNREF FILE". If I don't run fsck, then I get errors when I try to access files. Like "inode XXX: check-hash failed" and "such and such is marked as an executable file but could not be run by the operating system". -Alan