From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-fsdevel-owner@vger.kernel.org>
Received: from imap.thunk.org ([74.207.234.97]:40202 "EHLO imap.thunk.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1727979AbeK2C7G (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
        Wed, 28 Nov 2018 21:59:06 -0500
Date: Wed, 28 Nov 2018 10:56:57 -0500
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Willy Wolff <willy.mh.wolff.ml@gmail.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
        linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: oops when ext4 fs is full
Message-ID: <20181128155657.GG31885@thunk.org>
References: <20181128085038.iaklny2yuygrixhs@inc028000049.lancs.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20181128085038.iaklny2yuygrixhs@inc028000049.lancs.ac.uk>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Wed, Nov 28, 2018 at 08:50:39AM +0000, Willy Wolff wrote:
> 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.

Was this true after you rebooted?

Can you get a log of running e2fsck -n on the file system?

    	      	     	     	       - Ted