From: Al Viro <viro@zeniv.linux.org.uk>
To: Willy Wolff <willy.mh.wolff.ml@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: oops when ext4 fs is full
Date: Wed, 28 Nov 2018 14:41:39 +0000 [thread overview]
Message-ID: <20181128144139.GG2217@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20181128085038.iaklny2yuygrixhs@inc028000049.lancs.ac.uk>
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...
next prev parent reply other threads:[~2018-11-29 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 8:50 oops when ext4 fs is full Willy Wolff
2018-11-28 14:41 ` Al Viro [this message]
2018-11-28 15:56 ` Theodore Y. 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=20181128144139.GG2217@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy.mh.wolff.ml@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.