[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bug-201685-13602-kHnHQHX4Yu@https.bugzilla.kernel.org/>
Date: Tue, 04 Dec 2018 01:41:05 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 201685] ext4 file system corruption
https://bugzilla.kernel.org/show_bug.cgi?id=201685
--- Comment #213 from Guenter Roeck (linux@...ck-us.net) ---
#210: I rather refrain from it. Messing up one of my systems is bad enough.
Note that the problem is still spurious; it may happen a mionute into the test
(or even during boot), or after an hour.
I am now at a point where I still see the problem with almost all patches since
4.18.20 reverted; the only patch not reverted is the STAT_WRITE patch, because
it is difficult to revert due to context changes. I'll revert that manually for
the next round of tests. Here is the most recent log:
[ 2228.782567] EXT4-fs error (device sda1): ext4_iget:4795: inode #6317073:
comm borg: bad extra_isize 30840 (inode size 256)
[ 2228.805645] Aborting journal on device sda1-8.
[ 2228.814576] EXT4-fs (sda1): Remounting filesystem read-only
[ 2228.815816] EXT4-fs error (device sda1): ext4_iget:4795: inode #6317074:
comm borg: bad extra_isize 30840 (inode size 256)
[ 2228.817360] EXT4-fs error (device sda1): ext4_journal_check_start:61:
Detected aborted journal
[ 2228.817367] EXT4-fs (sda1): ext4_writepages: jbd2_start: 4086 pages, ino
5310565; err -30
[ 2228.819221] EXT4-fs error (device sda1): ext4_journal_check_start:61:
Detected aborted journal
[ 2228.819227] EXT4-fs (sda1): ext4_writepages: jbd2_start: 9223372036854775745
pages, ino 5328193; err -30
... and so on.
--
You are receiving this mail because:
You are watching the assignee of the bug.
Powered by blists - more mailing lists