linux-ext4 - Re: big allocation status

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] [day] [month] [year] [list]

Message-ID: <4E085A87.7050101@tao.ma>
Date:	Mon, 27 Jun 2011 18:25:11 +0800
From:	Tao Ma <tm@....ma>
To:	Ted Ts'o <tytso@....edu>
CC:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: big allocation status

Hi Ted,
	We began our test this week. And we found an error in dmesg:

[10484.043482] EXT4-fs (sda10): delayed block allocation failed for
inode 2289279 at logical offset 0 with max blocks 2 with error -28
[10484.043484] EXT4-fs (sda10): This should not happen!! Data will be lost
[10484.043484]
[10484.043486] Total free blocks count 0
[10484.043487] Free/Dirty block details
[10484.043488] free_blocks=0
[10484.043489] dirty_blocks=1495584
[10484.043489] Block reservation details
[10484.043490] i_reserved_data_blocks=2
[10484.043491] i_reserved_meta_blocks=1

yes, df shows that the file system is used 100% now, so I am not sure
whether this is a bug or not.

btw, this is a postmark test.

Regards,
Tao


On 06/07/2011 07:04 AM, Ted Ts'o wrote:
> On Fri, Jun 03, 2011 at 11:38:05PM -0400, Ted Ts'o wrote:
>> On Fri, Jun 03, 2011 at 09:57:23AM +0800, Tao Ma wrote:
>>> Hi Ted,
>>>
>>> Do you have any new branch or patch set that can be used for testing
>>> about big allocation? The latest patch set in the mailist is what you
>>> have sent at the beginning of May. Do you have an updated one? We will
>>> try to test it soon and it would grateful if we are on the same page.
>>
>> There is a patch set available at:
>>
>> git://repo.or.cz/ext4-patch-queue.git
>>
>> The bigalloc patches are after the stable-boundary, and will apply
>> against 3.0-rc1.
> 
> I've updated the bigalloc patch set to fix a number of bugs that I and
> a colleague of mine at Google have found.
> 
> This patch set known have problems with i_blocks getting out of sync
> if delalloc is enabled (particularly with sparse files and truncates),
> and as mentioned before, doesn't work correctly with the punch ioctl.
> These are bugs that we plan to fix before anything gets pushed into
> upstream, of course.
> 
> 	      					- 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

--
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