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?
