linux-kernel - Re: EXT4 ENOSPC Bug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090216150156.GD22619@mini-me.lan>
Date:	Mon, 16 Feb 2009 10:01:56 -0500
From:	Theodore Tso <tytso@....edu>
To:	Andres Freund <andres@...razel.de>
Cc:	adilger@....com, LKML <linux-kernel@...r.kernel.org>,
	linux-ext4@...r.kernel.org,
	Jonathan Bastien-Filiatrault <joe@....org>,
	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
Subject: Re: EXT4 ENOSPC Bug

On Mon, Feb 16, 2009 at 12:37:19PM +0100, Andres Freund wrote:
> Hi All,
>
> "Luckily", to prove that I am not completly mad I recently found this  
> problem again. On a more recent kernel:
> 2.6.29-rc3-andres-00498-g68e80d5
> (upstream 2.6.29 + Theodore's ext4 debug patches)
>
> Again I got:
> open("/home/andres/tt", O_WRONLY|O_CREAT|O_NOCTTY|O_NONBLOCK, 0666) = -1  
> ENOSPC (No space left on device)

So /home/andres/tt does not exist, correct?  Does this happen for any
attempt to create a new zero-length file using the "touch" command?
(Even in other directories)   Can you append to a file using "cat
/etc/mailcap >> some_existing_file"?

If it is "yes" to the first two questions, and "no" the third, it
looks like this might be an inode allocation failure as opposed to a
block allocation failure.

Once this triggers, does it reliably continue to fail if you reboot?
Or does it go away when you reboot?

					- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/