Bug#926130: e2fsck returns 1 which makes e2scrub fails

2021-02-14 Thread Theodore Ts'o
tag 926130 +moreinfo
thanks

On Sat, May 25, 2019 at 06:54:57PM -0400, Theodore Ts'o wrote:
> On Tue, May 14, 2019 at 09:42:58AM +0200, Laurent Bigonville wrote:
> > 
> > I've attached the requested logs. I don't see anything weird here.
> 
> Yeah, I'm not seeing anything in the logs either.  :-(
> 
> Would you be willing to send me a compressed e2image file?  The
> commands to generate are:
> 
>   e2image -Q /dev/fornost/docker docker.qcow2
>   xz docker.qcow2
> 
> .. and then send me the docker.qcow2.xz file.  It will include only
> the metadata blocks of the file system.  See the e2image man page for
> more details.  This *will* include filenames in the directory blocks,
> so if that makes you uncomfortable, you can use the -S option --- but
> if it's all the same to you, it would be more convenient if you could
> send it to me w/o using -S option.  The file will hopefully be small
> enough that you can just e-mail it to me, or put it someplace where I
> can download it (perhaps encrypted using GPG).

Hi, it's been a while.  Are you seeing e2scrub problems, especially
with newer versions of e2fsprogs?  If you are, would you be willing to
send me a compressed e2image file?

Thanks!

- Ted



Bug#926130: e2fsck returns 1 which makes e2scrub fails

2019-05-25 Thread Theodore Ts'o
On Tue, May 14, 2019 at 09:42:58AM +0200, Laurent Bigonville wrote:
> 
> I've attached the requested logs. I don't see anything weird here.

Yeah, I'm not seeing anything in the logs either.  :-(

Would you be willing to send me a compressed e2image file?  The
commands to generate are:

e2image -Q /dev/fornost/docker docker.qcow2
xz docker.qcow2

.. and then send me the docker.qcow2.xz file.  It will include only
the metadata blocks of the file system.  See the e2image man page for
more details.  This *will* include filenames in the directory blocks,
so if that makes you uncomfortable, you can use the -S option --- but
if it's all the same to you, it would be more convenient if you could
send it to me w/o using -S option.  The file will hopefully be small
enough that you can just e-mail it to me, or put it someplace where I
can download it (perhaps encrypted using GPG).

Thanks!!

- Ted



Bug#926130: e2fsck returns 1 which makes e2scrub fails

2019-05-13 Thread Theodore Ts'o
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
 



Bug#926130: e2fsck returns 1 which makes e2scrub fails

2019-04-01 Thread Laurent Bigonville

Le 31/03/19 à 23:10, Theodore Ts'o a écrit :

On Sun, Mar 31, 2019 at 09:37:56PM +0200, Laurent Bigonville wrote:

Package: e2fsprogs
Version: 1.45.0-1
Severity: important

Hi,

For one of my LV, e2scrub consistantly fails.

Debugging this it seems that e2fsck returns 1 but it's not showing any
messages about reparing something.

According to the manpage, 1 means:
1- File system errors corrected

Can you send me (or attach to the bug) the output of running "e2scrub
"?

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
/var/lib/sbuild/: Scrub FAILED due to corruption!  Unmount and run 
e2fsck -y.

tune2fs 1.45.0 (6-Mar-2019)
Setting filesystem error flag to force fsck.
  Logical volume "sbuildbuild.e2scrub" successfully removed


Bug#926130: e2fsck returns 1 which makes e2scrub fails

2019-03-31 Thread Theodore Ts'o
On Sun, Mar 31, 2019 at 09:37:56PM +0200, Laurent Bigonville wrote:
> Package: e2fsprogs
> Version: 1.45.0-1
> Severity: important
> 
> Hi,
> 
> For one of my LV, e2scrub consistantly fails.
> 
> Debugging this it seems that e2fsck returns 1 but it's not showing any
> messages about reparing something.
> 
> According to the manpage, 1 means:
> 1- File system errors corrected

Can you send me (or attach to the bug) the output of running "e2scrub
"?

Thanks,

- Ted



Bug#926130: e2fsck returns 1 which makes e2scrub fails

2019-03-31 Thread Laurent Bigonville
Package: e2fsprogs
Version: 1.45.0-1
Severity: important

Hi,

For one of my LV, e2scrub consistantly fails.

Debugging this it seems that e2fsck returns 1 but it's not showing any
messages about reparing something.

According to the manpage, 1 means:
1- File system errors corrected

If I'm umounting the FS and then run e2scrub, it returns 0

Any idea how to debug this further?

Regards,
Laurent Bigonville

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages e2fsprogs depends on:
ii  libblkid12.33.1-0.1
ii  libc62.28-8
ii  libcom-err2  1.45.0-1
ii  libext2fs2   1.45.0-1
ii  libss2   1.45.0-1
ii  libuuid1 2.33.1-0.1

Versions of packages e2fsprogs recommends:
ii  e2fsprogs-l10n  1.45.0-1
ii  lvm22.03.02-2

Versions of packages e2fsprogs suggests:
pn  e2fsck-static  
ii  fuse2fs1.45.0-1
pn  gpart  
ii  parted 3.2-24

-- no debconf information