From: Peter Geis <pgwipeout@gmail.com>
To: linux-ext4@vger.kernel.org
Subject: Ext4 corruption on linux-next since 5.2 merge window
Date: Wed, 22 May 2019 19:40:26 -0400 [thread overview]
Message-ID: <f79a1b38-898d-8bfa-37d6-a74ee97411e5@gmail.com> (raw)
Good Evening,
Since the 5.2 merge window, I've been encountering EXT4 corruption
periodically.
The board is the rk3328-roc-cc.
The device is a USB 3.0 Samsung SSD.
$ lsusb
Bus 005 Device 002: ID 04e8:61f5 Samsung Electronics Co., Ltd Portable
SSD T5
$ lsusb --tree
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
|__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
Currently running:
uname -a
Linux firefly 5.2.0-rc1-next-20190521test-14384-gea7592a68ff9 #64 SMP
PREEMPT Tue May 21 14:40:53 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux
The error received is:
[12546.303907] EXT4-fs error (device sda1): ext4_find_extent:909: inode
#8: comm jbd2/sda1-8: pblk 60850175 bad header/extent: invalid extent
entries - magic f30a, entries 8, max 340(340), depth 0(0)
This immediately knocks the filesystem to RO.
It is easily reproducible during kernel compilation.
I'm at a loss as to where to begin, considering the number of changes in
various subsystems.
Is there some way I can enable more ext4 debugging?
next reply other threads:[~2019-05-22 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 23:40 Peter Geis [this message]
2019-05-24 4:37 ` Ext4 corruption on linux-next since 5.2 merge window Theodore Ts'o
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=f79a1b38-898d-8bfa-37d6-a74ee97411e5@gmail.com \
--to=pgwipeout@gmail.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).