All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arthur Marsh <arthur.marsh@internode.on.net>
To: linux-kernel@vger.kernel.org
Subject: ext3/ext4 filesystem corruption under post 5.1.0 kernels
Date: Sat, 11 May 2019 21:03:44 +0930	[thread overview]
Message-ID: <48BA4A6E-5E2A-478E-A96E-A31FA959964C@internode.on.net> (raw)

I have yet to bisect, but have had trouble with recent, post 5.1.0 kernels built from Linus' git head on both i386 (Pentium 4 pc) and amd64 (Athlon II X4 640).

The easiest way to trigger the problem is:

git gc

on the kernel source tree, although the problem can occur without doing a git gc.

The filesystem with the kernel source tree is the root file system, ext3, mounted as:

/dev/sdb7 on / type ext3 (rw,relatime,errors=remount-ro)

After the "Compressing objects" stage, the following appears in dmesg:

[  848.968550] EXT4-fs error (device sdb7): ext4_get_branch:171: inode #8: block 30343695: comm jbd2/sdb7-8: invalid block
[  849.077426] Aborting journal on device sdb7-8.
[  849.100963] EXT4-fs (sdb7): Remounting filesystem read-only
[  849.100976] jbd2_journal_bmap: journal block not found at offset 989 on sdb7-8

fsck -yv 

then reports:

# fsck -yv
fsck from util-linux 2.33.1
e2fsck 1.45.0 (6-Mar-2019)
/dev/sdb7: recovering journal
/dev/sdb7 contains a file system with errors, check forced.
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
Free blocks count wrong (4619656, counted=4619444).
Fix? yes

Free inodes count wrong (15884075, counted=15884058).
Fix? yes


/dev/sdb7: ***** FILE SYSTEM WAS MODIFIED *****

Other times, I have gotten:

"Inodes that were part of a corrupted orphan linked list found."
"Block bitmap differences:"
"Free blocks sound wrong for group"

No problems have been observed with the 5.1.0 release kernel.

Any suggestions for narrowing down the issue welcome.

Arthur.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

             reply	other threads:[~2019-05-11 11:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-11 11:33 Arthur Marsh [this message]
2019-05-11 12:43 ` ext3/ext4 filesystem corruption under post 5.1.0 kernels Richard Weinberger
2019-05-11 22:06   ` Theodore Ts'o
2019-05-13  7:45     ` Arthur Marsh
2019-05-13 10:31     ` Arthur Marsh
2019-05-14  1:59       ` Arthur Marsh
2019-05-14 10:42         ` Ondrej Zary
2019-05-15  2:59         ` Arthur Marsh
2019-05-15  4:57           ` Theodore Ts'o
2019-05-15 12:12             ` Arthur Marsh
2019-05-16  2:56               ` Theodore Ts'o
2019-05-17 16:44             ` Geert Uytterhoeven
2019-07-01 12:43               ` Geert Uytterhoeven
2019-07-01 13:56                 ` Theodore Ts'o
2019-07-01 14:08                   ` Geert Uytterhoeven
2019-05-17  9:23     ` Geert Uytterhoeven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48BA4A6E-5E2A-478E-A96E-A31FA959964C@internode.on.net \
    --to=arthur.marsh@internode.on.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.