Date: Tue, 8 Aug 2017 00:01:35 -0600 From: Warner Losh <imp@bsdimp.com> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: [autofs] problems with "dirty" UFS2 partitions Message-ID: <CANCZdfpJypp4Jmu2x8-6u1LotYK4nHqJYv8JHWz8Y85eD9P56Q@mail.gmail.com> In-Reply-To: <20170808071758.6a815d59@freyja.zeit4.iv.bundesimmobilien.de> References: <20170808071758.6a815d59@freyja.zeit4.iv.bundesimmobilien.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 7, 2017 at 11:17 PM, O. Hartmann <ohartmann@walstatt.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfpJypp4Jmu2x8-6u1LotYK4nHqJYv8JHWz8Y85eD9P56Q>