Hello Theodore,
Theodore Tso schrieb am Fri 29. Sep, 17:15 (-0400):
If the filesystem is empty (or at least no no hashtree directories),
then when the kernel creates new directories and expands to the point
where they become indexed, they will be indexed with the PPC variant
of the hash
On Sep 28, 2006 21:08 -0400, Theodore Tso wrote:
On Wed, Sep 27, 2006 at 02:22:51PM +0200, Jörg Sommer wrote:
Package: e2fsprogs
Version: 1.39-1
Severity: important
you set the compiler option -fsigned-char, but on PowerPC the default is
unsigned char. This makes the kernel uses
On Fri, Sep 29, 2006 at 11:15:47AM -0600, Andreas Dilger wrote:
Hmm, except isn't the problem ALREADY that PPC is broken with 8-bit
chars and htree? That's what started this problem in the first place.
Running e2fsck allowed the kernel htree code to find the file, when
it could not otherwise
On Wed, Sep 27, 2006 at 02:22:51PM +0200, Jörg Sommer wrote:
Package: e2fsprogs
Version: 1.39-1
Severity: important
you set the compiler option -fsigned-char, but on PowerPC the default is
unsigned char. This makes the kernel uses unsigned and e2fsck uses signed
chars.
In the case of an
Package: e2fsprogs
Version: 1.39-1
Severity: important
Hi,
you set the compiler option -fsigned-char, but on PowerPC the default is
unsigned char. This makes the kernel uses unsigned and e2fsck uses signed
chars.
In the case of an 8 bit character, str2hashbuf() in lib/ext2fs/dirhash.c
produces
5 matches
Mail list logo
