On Wed, Nov 28, 2018 at 08:50:39AM +0000, Willy Wolff wrote: > Hi, > I got a Oops when the hard drive was COMPLETELY full using a ext4 fs. > After it, any command on the directory where the last write should have occurred freezes, while any other directory behave just fine. > > If this email is not relevant for you, please point me what to do. > > Best Regards, > Willy > > > $ cat /proc/version > Linux version 4.18.7-dirty (willy@inc028000049) (gcc version 6.3.0 20170516 (Debian 6.3.0-18)) #32 SMP PREEMPT Thu Sep 27 19:31:11 BST 2018 > > The kernel is dirty but the modifications are not related to the fs subsystem. The system is running on a Hardkernel Odroid-xu3 but running with the mainline linux at 8ea7eadbef2f7103d5871016f03fc38b3adeaddb > Also, the fs is on a SD-card. I did a fs check after the oops, no errors are reported. Disassembly of __d_instantiate in your build would obviously be useful... _Presumably_ it's one of the spin_lock() inlined there, but it would be useful to know which one...
