On Mon, Nov 11, 2019 at 9:34 AM Belisko Marek 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
kn
On Wed, Nov 20, 2019, 11:58 PM Belisko Marek
wrote:
> On Thu, Nov 21, 2019 at 7:25 AM Chris Murphy
> wrote:
> >
> > On Tue, Nov 12, 2019 at 3:52 AM Belisko Marek
> wrote:
> > >
> > > On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering
> > > wrote:
> > > >
> > > > On Mo, 11.11.19 13:33, Belisko
20.11.2019 17:35, Belisko Marek пишет:
> Hi Andrei,
>
> On Sat, Nov 16, 2019 at 9:31 AM Andrei Borzenkov wrote:
>>
>> 12.11.2019 13:52, Belisko Marek пишет:
>>> On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering
>>> wrote:
On Mo, 11.11.19 13:33, Belisko Marek (marek.beli...@gmail.com)
On Thu, Nov 21, 2019 at 7:25 AM Chris Murphy wrote:
>
> On Tue, Nov 12, 2019 at 3:52 AM Belisko Marek wrote:
> >
> > On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering
> > wrote:
> > >
> > > On Mo, 11.11.19 13:33, Belisko Marek (marek.beli...@gmail.com) wrote:
> > > 65;5802;1c
> > > > Hi,
> > >
On Tue, Nov 12, 2019 at 3:52 AM Belisko Marek wrote:
>
> On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering
> wrote:
> >
> > On Mo, 11.11.19 13:33, Belisko Marek (marek.beli...@gmail.com) wrote:
> > 65;5802;1c
> > > Hi,
> > >
> > > I'm using systemd 234 (build by yocto) and I've setup automount o
Hi Andrei,
On Sat, Nov 16, 2019 at 9:31 AM Andrei Borzenkov wrote:
>
> 12.11.2019 13:52, Belisko Marek пишет:
> > On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering
> > wrote:
> >>
> >> On Mo, 11.11.19 13:33, Belisko Marek (marek.beli...@gmail.com) wrote:
> >> 65;5802;1c
> >>> Hi,
> >>>
> >>> I'
12.11.2019 13:52, Belisko Marek пишет:
> On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering
> wrote:
>>
>> On Mo, 11.11.19 13:33, Belisko Marek (marek.beli...@gmail.com) wrote:
>> 65;5802;1c
>>> Hi,
>>>
>>> I'm using systemd 234 (build by yocto) and I've setup automount of
>>> sdcard in fstab. Thi
On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering
wrote:
>
> On Mo, 11.11.19 13:33, Belisko Marek (marek.beli...@gmail.com) wrote:
> 65;5802;1c
> > Hi,
> >
> > I'm using systemd 234 (build by yocto) and I've setup automount of
> > sdcard in fstab. This works perfectly fine. But I have seen from t
Am Mo., 11. Nov. 2019 um 16:47 Uhr schrieb Lennart Poettering
:
> Well, note that ext4's fsck only does an actual file system check
> every now and then.
Afair this is outdated knowledge. newer e2fsprogs versions no longer
setup ext4 file systems to do regular fscks.
At least on Debian sid, /etc/m
On Mo, 11.11.19 13:33, Belisko Marek (marek.beli...@gmail.com) wrote:
65;5802;1c
> Hi,
>
> I'm using systemd 234 (build by yocto) and I've setup automount of
> sdcard in fstab. This works perfectly fine. But I have seen from time
> to time when system goes to emergency mode because sdcard filesyste
Hello,
FWIK passno > 0 in /etc/fstab configures only order in which the fsck
is performed, not the frequency. To configure the frequency as well,
I'd recommend taking a look at `man systemd-fsck@.service`, especially
the `fsck.mode=force` kernel command line parameter, which should do
exactly what
Am 11.11.19 um 13:33 schrieb Belisko Marek:
> I'm using systemd 234 (build by yocto) and I've setup automount of
> sdcard in fstab. This works perfectly fine. But I have seen from time
> to time when system goes to emergency mode because sdcard filesystem
> (ext4) have an issue and cannot be moun
Hi,
I'm using systemd 234 (build by yocto) and I've setup automount of
sdcard in fstab. This works perfectly fine. But I have seen from time
to time when system goes to emergency mode because sdcard filesystem
(ext4) have an issue and cannot be mounted. I was thinking about
forcing fsck for every
13 matches
Mail list logo