linux-ext4 - Re: Bigalloc ENOSPC woes

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: <20120130223111.GA20940@thunk.org>
Date:	Mon, 30 Jan 2012 17:31:11 -0500
From:	Ted Ts'o <tytso@....edu>
To:	Eric Sandeen <sandeen@...hat.com>
Cc:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: Bigalloc ENOSPC woes

On Mon, Jan 30, 2012 at 03:19:05PM -0600, Eric Sandeen wrote:
> I got nervous when I tried this on an -O bigalloc -C 65536 fs:
> 
> # echo foo > blah; du -hc blah; sync; du -hc blah
> 4.0K blah
> 4.0K total
> 64K blah
> 64K total
> 
> Seems that du should never report less than the cluster size, should it?

Yes, that seems like a bug.

> And that made me wonder about ENOSPC handling - are we tracing
> delalloc allocations correctly?
> 
> From running xfstest 204 on a similarly-created fs, it really seems
> that we are not....
> 
> Ted, are you aware of those issues in bigalloc?

No, this is news to me.  I'll have to take a closer look at this;
thanks for bring this up.

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