From owner-freebsd-current@freebsd.org Tue Aug 8 05:18:14 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 0C977DC2534 for ; Tue, 8 Aug 2017 05:18:14 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6D1C96F8F5 for ; Tue, 8 Aug 2017 05:18:12 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MfzEP-1e1izG4AgX-00NOji for ; Tue, 08 Aug 2017 07:18:04 +0200 Date: Tue, 8 Aug 2017 07:17:58 +0200 From: "O. Hartmann" To: freebsd-current Subject: [autofs] problems with "dirty" UFS2 partitions Message-ID: <20170808071758.6a815d59@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:vAjLuyH3jR9MZD6nkbEV9E0n4R5sLhoqf7kdCkoGdlG1BpIMBYh kmoaXw/opKC4sNAPFdwXFyzQTqSWQMWJ/9Lz3O3tdrcUNmBES7kbdWSW/wwzeXWZytANd1m 5WNBbMX94qZJWoZ+9fBBV1hPvsfryT4uOlAlzrnXcIPjy5XU20fiUhpWkU8aeciP27z8geB C3lA31pWVDjXUF10UWJkQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:vrn+rFIi1IA=:N4twjWmmSZ0j4yfPiEEDEG ORECWqOfi/ozzFC9iNOnb8R87OIY/OKnTZ7hiJorPpPfbTWnfLZw4SMUNz3Zf6zx1OpNBq2YE lXmdazW44wAkS4xaY8/OgurvBHZgki4a8heGXCJDqWsXao9qOh3EjAt+Psc4ehytdzT95AQPp Ltyq3VK/vr+lp6ZW6ErWbEXAqwDWU8G0HKqU7mbNl9f/9QZwTWYQPGvmBpoTGKst4bHTYGJ1r 1ns7viU5QtWTIpXo8V4/hlDRqkOy3YZ0PRnqhF++uph0LMxr6M69XnwkGzO5FcdbrxFKG8Ulu Zd3RJN3xpODU6qTI9udCxdfdhb26vzA9kI51cdWyiUR+WqQzlYqB79wloO9xooPN+ccAXH2ad cZP9Wa4AX/pYdiZqzyXXsJIT+GxPsZbHAL+77pQQ9Kzmoy5xMGvEREIuYgIZTptXnUg0FQ7DT FKB9H0sULc5iY6ndqcTLuIxrUYuu7tIVRNvg8P3vPzag4saRr6XDEUNQ6YsVfq9VLuoepOYql rjfC1U2ZLt3ZvB/m7iiqBcqEaEyVcKI952MpN6EngguYgsN9tSx5BvDT1njTYfvsfny1gEC6O OJGuwAQcit7Z8seW/hmYrA6CII4HSmxiq591ZSyiYVEfITfimwhgAG0gsHIfNfYfE5wKE7Hso f8NSQ1q4QFUcnwKTSF6As6bvcPcOYLgsUYfz8+4aUwSTXXS1JHKjLvjcwB2JNrw8bJ1FC6NGB 421heae3nYKmOGjssN73IhHb++QzV35zSqa7SfvJyGDSEwXWWGzEWdp+SfNvEThWpPrcsekhX hQRM7P2sNPO2OdGQvunGkGROiYX1MevJrCOOqLLKCnEeDKRhHs= 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 05:18:14 -0000 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. Thanks in advance, Oliver