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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 3 Dec 2008 12:23:09 -0500
From:	Theodore Tso <>
To:	"Aneesh Kumar K.V" <>
Cc:	Jonathan Bastien-Filiatrault <>,
	Andres Freund <>,
	Andreas Dilger <>,
	LKML <>,
Subject: Re: EXT4 ENOSPC Bug

On Wed, Dec 03, 2008 at 09:04:41PM +0530, Aneesh Kumar K.V wrote:
> Can you make sure you have the below patch in the kernel.
> c001077f4003fa75793bb62979baa6241dd8eb19
> commit c001077f4003fa75793bb62979baa6241dd8eb19
> Author: Eric Sandeen <>
> Date:   Tue Aug 19 22:19:50 2008 -0400
> ext4: Fix bug where we return ENOSPC even though we have plenty of inodes

Mmmm, good point, thanks.  I had been assuming this was caused by some
failure in the delayed allocation code with block accounting, but we
also had a bug fix that was causing a problem with inode allocation.

That doesn't explain a report of an ENOSPC error with metadata only
changes were failing (i.e., touching a file that already exists),
although I don't think we've gotten a lot of information about that
scenario and it feels a little unconfirmed to me still...

So, yes, this patch may solve the issue for you.

							- Ted

View attachment "0001-ext4-Fix-bug-where-we-return-ENOSPC-even-though-we.patch" of type "text/x-diff" (1602 bytes)

Powered by blists - more mailing lists