From: Michael Hennig <M_Hennig@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: ext4 file system corruption with v4.19.3 / v4.19.4
Date: Mon, 3 Dec 2018 22:47:40 +0100 [thread overview]
Message-ID: <019a09df-df3d-3350-a779-e51886c2691b@gmx.net> (raw)
I'm suffering from ext4 corruption too.
(Ubuntu 18.10, 4.19.6-041906-generic, 64 bit)
22:00:01 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484759: comm rm: bad extra_isize 58853 (inode size 256)
22:00:01 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484759: comm rm: bad extra_isize 58853 (inode size 256)
22:00:01 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484754: comm rm: bad extra_isize 58853 (inode size 256)
22:00:01 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484755: comm rm: bad extra_isize 58853 (inode size 256)
22:00:01 kernel: EXT4-fs error (device sda4): ext4_iget:4851: inode
#42484768: comm rm: checksum invalid
22:00:01 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484767: comm rm: bad extra_isize 58853 (inode size 256)
22:00:01 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484763: comm rm: bad extra_isize 58853 (inode size 256)
22:00:01 kernel: EXT4-fs error (device sda4): ext4_iget:4851: inode
#42484766: comm rm: checksum invalid
22:00:01 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484761: comm rm: bad extra_isize 58853 (inode size 256)
22:00:01 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484764: comm rm: bad extra_isize 58853 (inode size 256)
22:00:01 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484765: comm rm: bad extra_isize 58853 (inode size 256)
21:00:48 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484759: comm rm: bad extra_isize 58853 (inode size 256)
21:00:48 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484754: comm rm: bad extra_isize 58853 (inode size 256)
21:00:48 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484755: comm rm: bad extra_isize 58853 (inode size 256)
21:00:48 kernel: EXT4-fs error (device sda4): ext4_iget:4851: inode
#42484768: comm rm: checksum invalid
21:00:48 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484767: comm rm: bad extra_isize 58853 (inode size 256)
21:00:48 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484763: comm rm: bad extra_isize 58853 (inode size 256)
21:00:48 kernel: EXT4-fs error (device sda4): ext4_iget:4851: inode
#42484766: comm rm: checksum invalid
21:00:48 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484761: comm rm: bad extra_isize 58853 (inode size 256)
21:00:48 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484764: comm rm: bad extra_isize 58853 (inode size 256)
21:00:48 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484765: comm rm: bad extra_isize 58853 (inode size 256)
21:00:32 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484762: comm rsync: bad extra_isize 58853 (inode size 256)
21:00:32 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484761: comm rsync: bad extra_isize 58853 (inode size 256)
21:00:32 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484760: comm rsync: bad extra_isize 54976 (inode size 256)
21:00:32 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484759: comm rsync: bad extra_isize 58853 (inode size 256)
21:00:32 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484758: comm rsync: bad extra_isize 58853 (inode size 256)
21:00:32 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484757: comm rsync: bad extra_isize 58853 (inode size 256)
21:00:32 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484756: comm rsync: bad extra_isize 63008 (inode size 256)
21:00:32 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484755: comm rsync: bad extra_isize 58853 (inode size 256)
21:00:31 kernel: EXT4-fs error (device sda4): ext4_iget:4831: inode
#42484754: comm rsync: bad extra_isize 58853 (inode size 256)
21:00:31 kernel: EXT4-fs error (device sda4): ext4_iget:4851: inode
#42484753: comm rsync: checksum invalid
Checked some of the defective inodes only to find timeshift back-upped
files through rsync:
debugfs 1.44.4 (18-Aug-2018)
debugfs: ncheck 42484759
Inode Pathname
42484759
/timeshift/snapshots/2018-11-28_20-00-02/localhost/var/lib/dpkg/info/libxcb1:i386.symbols
42484759
/timeshift/snapshots/2018-11-30_18-00-01/localhost/var/lib/dpkg/info/libxcb1:i386.symbols
42484759
/timeshift/snapshots/2018-12-02_21-00-01/localhost/var/lib/dpkg/info/libxcb1:i386.symbols
42484759
/timeshift/snapshots/2018-12-01_21-00-01/localhost/var/lib/dpkg/info/libxcb1:i386.symbols
debugfs: ncheck 42484754
Inode Pathname
debugfs: ncheck 42484755
Inode Pathname
42484755
/timeshift/snapshots/2018-11-28_20-00-02/localhost/var/lib/dpkg/info/libxcb1:amd64.triggers
42484755
/timeshift/snapshots/2018-11-30_18-00-01/localhost/var/lib/dpkg/info/libxcb1:amd64.triggers
42484755
/timeshift/snapshots/2018-12-02_21-00-01/localhost/var/lib/dpkg/info/libxcb1:amd64.triggers
42484755
/timeshift/snapshots/2018-12-01_21-00-01/localhost/var/lib/dpkg/info/libxcb1:amd64.triggers
debugfs: ncheck 42484768
Inode Pathname
42484768
/timeshift/snapshots/2018-11-28_20-00-02/localhost/var/lib/dpkg/info/libxft2:amd64.list
42484768
/timeshift/snapshots/2018-11-30_18-00-01/localhost/var/lib/dpkg/info/libxft2:amd64.list
42484768
/timeshift/snapshots/2018-12-02_21-00-01/localhost/var/lib/dpkg/info/libxft2:amd64.list
42484768
/timeshift/snapshots/2018-12-01_21-00-01/localhost/var/lib/dpkg/info/libxft2:amd64.list
debugfs: ncheck 42484767
Inode Pathname
42484767
/timeshift/snapshots/2018-11-28_20-00-02/localhost/var/lib/dpkg/info/libxft-dev:amd64.md5sums
42484767
/timeshift/snapshots/2018-11-30_18-00-01/localhost/var/lib/dpkg/info/libxft-dev:amd64.md5sums
42484767
/timeshift/snapshots/2018-12-02_21-00-01/localhost/var/lib/dpkg/info/libxft-dev:amd64.md5sums
42484767
/timeshift/snapshots/2018-12-01_21-00-01/localhost/var/lib/dpkg/info/libxft-dev:amd64.md5sums
debugfs: ncheck 42484763
Inode Pathname
42484763
/timeshift/snapshots/2018-11-28_20-00-02/localhost/var/lib/dpkg/info/libxdo3:amd64.shlibs
42484763
/timeshift/snapshots/2018-11-30_18-00-01/localhost/var/lib/dpkg/info/libxdo3:amd64.shlibs
42484763
/timeshift/snapshots/2018-12-02_21-00-01/localhost/var/lib/dpkg/info/libxdo3:amd64.shlibs
42484763
/timeshift/snapshots/2018-12-01_21-00-01/localhost/var/lib/dpkg/info/libxdo3:amd64.shlibs
debugfs: ncheck 42484753
Inode Pathname
42484753
/timeshift/snapshots/2018-11-28_20-00-02/localhost/var/lib/dpkg/info/libxcb1:amd64.shlibs
42484753
/timeshift/snapshots/2018-11-30_18-00-01/localhost/var/lib/dpkg/info/libxcb1:amd64.shlibs
42484753
/timeshift/snapshots/2018-12-02_21-00-01/localhost/var/lib/dpkg/info/libxcb1:amd64.shlibs
42484753
/timeshift/snapshots/2018-12-01_21-00-01/localhost/var/lib/dpkg/info/libxcb1:amd64.shlibs
Maybe timeshifts rsync is related to this?
Kind regards
Michael Hennig
next reply other threads:[~2018-12-03 21:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 21:47 Michael Hennig [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-04 7:33 Gunter Königsmann
2018-12-01 15:47 Huang Yan
[not found] <065643a0-f9aa-a361-715a-03ca978d9228@roeck-us.net>
2018-11-27 14:32 ` Guenter Roeck
2018-11-27 14:48 ` Marek Habersack
2018-11-27 17:31 ` Guenter Roeck
2018-11-27 18:55 ` Rainer Fiebig
2018-11-27 21:22 ` Guenter Roeck
2018-11-28 1:57 ` Vito Caputo
2018-11-28 9:56 ` Rainer Fiebig
2018-11-27 15:50 ` Rainer Fiebig
2018-11-28 0:16 ` Andrey Jr. Melnikov
2018-11-28 4:15 ` Theodore Y. Ts'o
2018-11-28 8:02 ` Marek Habersack
2018-11-28 10:02 ` Andrey Jr. Melnikov
2018-11-28 15:56 ` Rainer Fiebig
2018-11-28 16:10 ` Theodore Y. Ts'o
2018-11-28 16:18 ` Marek Habersack
2018-11-28 17:01 ` Rainer Fiebig
2018-11-28 21:13 ` Andrey Melnikov
2018-11-28 22:09 ` Rainer Fiebig
2018-12-02 20:19 ` Andrey Melnikov
2018-12-02 22:13 ` Rainer Fiebig
2018-12-05 12:58 ` Andrey Melnikov
2018-12-11 0:11 ` Pavel Machek
2018-12-13 10:38 ` Andrey Jr. Melnikov
2018-11-28 13:28 ` Andrey Melnikov
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=019a09df-df3d-3350-a779-e51886c2691b@gmx.net \
--to=m_hennig@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®