From owner-freebsd-current@freebsd.org Tue Aug 8 06:01:37 2017 Return-Path: Delivered-To: freebsd-current@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 5BDB4DC4191 for ; Tue, 8 Aug 2017 06:01:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (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 22CD470C5A for ; Tue, 8 Aug 2017 06:01:37 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x231.google.com with SMTP id 76so13507400ith.0 for ; Mon, 07 Aug 2017 23:01:37 -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=oi+RnUBSFaf8CBTIfLw6NxwgMFiq4p8fibsGVW4oCBI=; b=Gjpba4XClQtfTKXsspQtQS+jEfHAPWF9ct+wUi87J7jQ4ztpP6JCx3XzVw+F2R4rxK XTz+HFCXOpC4yrzAxfiCujHicqC2+TTL9H3bCo0A/b2cfVnMR6ZgnloksWFRQQy4eMh0 HvvNIgyBJXsWgkLrRcmc+zTs+PfUPYqwmvJlrFWoG7oXFSRKKsxH9kmYhBOkCMu2uSu3 9STXP+KuJqcEUgJiumzAn88/InYOj4KcUnsy8THAOJ4Or94qx7rSiaPaUu2Vr2ynErxa Y/xkK93fU0HITaZzSy+/VhzR/EdiLnHKZnJ8MtfEVO3beXDr4IaS1cck9YLpTLRuFNxM HIOQ== 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=oi+RnUBSFaf8CBTIfLw6NxwgMFiq4p8fibsGVW4oCBI=; b=PemvNE0wsOYTtBMbrSJp/6JliLuV0u/YR2SopM0j3TcnPGF+VDcnduan9ZZxr+VU1m VurX5Cfs9DMQXnKWas710h55OzotlurZOnDBhVIQPj5Q9NFxDO58ej8TBgRTocBQf1v9 uRP0z+Od1/tsWIB4JP19AXQp5v+FRSwU/n92Od4VDtHNZl1B1+4mraIb2k6LB/0IvT23 gZWq+Wb5SZQxg0fVrFeI1qnOrtDTV3Ca5zJ7C6bdcJ6INt4VKAjWlHcV2v7QRtWaeSs+ tpBiGKPjoHZlUY4Ku8ZKBXhogC5tBgfsLrDNKqmqPFc0w/HKvHK2gAfCm7c8cjHoFtmQ dREA== X-Gm-Message-State: AHYfb5gQXjjBFdKPcEoGywMbrjJuHO7OgyOEk5XUqMU5dzRnruPyzXCb Ma5a5XUusO0irdC9pKAE8y5LiZZZb76m X-Received: by 10.36.54.13 with SMTP id l13mr3065217itl.0.1502172096457; Mon, 07 Aug 2017 23:01:36 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.10.71 with HTTP; Mon, 7 Aug 2017 23:01:35 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:95b6:4226:f295:bf25] In-Reply-To: <20170808071758.6a815d59@freyja.zeit4.iv.bundesimmobilien.de> References: <20170808071758.6a815d59@freyja.zeit4.iv.bundesimmobilien.de> From: Warner Losh Date: Tue, 8 Aug 2017 00:01:35 -0600 X-Google-Sender-Auth: SDGihhLmxRJaClk8dtPq9dAWIV0 Message-ID: Subject: Re: [autofs] problems with "dirty" UFS2 partitions To: "O. Hartmann" Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 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: Tue, 08 Aug 2017 06:01:37 -0000 On Mon, Aug 7, 2017 at 11:17 PM, O. Hartmann wrote: > Hello, > > we're running a NanoBSD based appliance which resides on a small SoC and > utilises a mSATA SSD for logging, database storage and mail folder. The > operating system is recent CURRENT as it is still under development. > > The problem ist, that from time to time, without knowing or seeing the > reason, > the automounted partitions become "dirty (UFS2 partitions, no ZFS dur to > memory and performance limitations). Journaling is enbaled. > > When the partitions on the SSD become "dirty", logging or accessing them > isn't > possible anymore and for some reason I do not see any log entries reporting > this (maybe due to the fact all logs are going also to that disk since the > logs > would pollute the serial console/console and the console is used for > maintenance purposes/ssh terminal). > > Is it possible to - automated! - check the filesystem on bootup? As on > ordinary > FreeBSD systems with fstab-based filesystems, this happens due to the > rc-init-infrastructure but autofs filesystems seem to be somehow standing > aside > from this procedure. > Can't you just list them in /etc/fstab with the noauto option, but with a non-zero number listed in the 'pass' number column? I know nanobsd doesn't generate things this way, but maybe it should.... Warner