On Mon, Nov 11, 2019 at 9:34 AM Belisko Marek <marek.belisko@xxxxxxxxx> wrote: > Am I still > missing something? Thanks. Yes, what you are trying to do is the wrong thing(tm) to do, please figure out why there is filesystem corruption in the first place, while ext4 of course has bugs like any software around, it is not known for being fragile. I'd bet money on the SD card being crappy. _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: perform fsck on everyt boot
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: perform fsck on everyt boot
- From: Cristian Rodríguez <crrodriguez@xxxxxxxxxxxx>
- Date: Fri, 6 Dec 2019 22:04:34 -0300
- In-reply-to: <CAAfyv349zu+Lu-UixeZ74rG9SUhH1JNA-xN=tTwB9YEu0W60-g@mail.gmail.com>
- References: <CAAfyv349zu+Lu-UixeZ74rG9SUhH1JNA-xN=tTwB9YEu0W60-g@mail.gmail.com>
- References:
- perform fsck on everyt boot
- From: Belisko Marek
- perform fsck on everyt boot
- Prev by Date: Re: Why does initrd-parse-etc.service re-start initrd-fs.target?
- Next by Date: Re: Why does initrd-parse-etc.service re-start initrd-fs.target?
- Previous by thread: Re: perform fsck on everyt boot
- Next by thread: need help with undestanding a udev warning
- Index(es):
 |