On 12:05, Mingming Cao wrote:
BTW: Are ext3 filesystem sizes greater than 8T now officially
supported?
I think so, but I don't know how much 16TB testing developers and
distros are doing - perhaps the linux-ext4 denizens can tell us?
-
IBM has done some testing (dbench, fsstress,
Begin forwarded message:
Date: Thu, 8 Mar 2007 18:35:54 +0100
From: Jan De Luyck [EMAIL PROTECTED]
To: linux-kernel@vger.kernel.org
Subject: EXT3-fs warning (device sdd2): dx_probe: Unrecognised inode hash code
232
Hello,
Running 2.6.19.1 on AMD64.
While copying some files on an ext3
On Mar 09, 2007 07:40 -0800, Andrew Morton wrote:
EXT3-fs warning (device sdd2): dx_probe: Unrecognised inode hash code 232
Assertion failure in dx_probe() at fs/ext3/namei.c:384:
dx_get_limit(entries)
== dx_root_limit(dir, root-info.info_length)
Looks like corrupted on-disk or in-memory
In recent discussions on #linuxfs with Coly Li (I hope I have the email
correct), we have ressurected the idea of improving the stat and unlink
performance of ext3 htree directories. Coly seems interested in working
on fixing this problem, so I thought I'd start an email thread in the
list to get
