Hi.  I haven't forgotten about your bug report.  The problem has been
I can't find any explanation for how e2fsck could have returned an
exit status of 1 given the output shown below.

> bigon@fornost:~$ sudo LC_ALL=C e2scrub /var/lib/sbuild/
>   Logical volume "sbuildbuild.e2scrub" created.
> e2fsck 1.45.0 (6-Mar-2019)
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> /dev/fornost/sbuildbuild.e2scrub: 13/983040 files (0.0% non-contiguous),
> 68098/3932160 blocks

So... if you could do the following, I would greatly appreciate it.

1)  Confirm that this is still reproducing for you with e2fsprogs 1.45.0.

2) I've just released e2fsprogs 1.45.1 to Debian unstable.  If you
could try installing e2fsprogs, and see if you can still reproduce the
problem with e2fsprogs 1.45.1.

3) If you can, please create an /etc/e2fsck.conf containing the
following:

[options]
        max_count_problems = 2
        log_dir = /tmp
        problem_log_filename = e2fsck-problems-%N.%h.INFO.%D-%T
        log_filename = e2fsck-%N.%h.INFO.%D-%T
        log_dir_wait = true

4) The rerun the e2scrub command and send me the output of
/tmp/e2fsck-problems-*INFO* and /tmp/e2fsck-*INFO* files that will be
created as a result of running e2fsck.

Many thanks, and my apologies for not getting back to you sooner.

                                              - Ted
     

Reply via email to