Re: [PATCH 1/3] make static counters in new_inode and iunique be 32 bits

2007-01-26 Thread Kirill Korotaev
Acked-By: Kirill Korotaev <[EMAIL PROTECTED]> hit it today as well :/ > When a 32-bit program that was not compiled with large file offsets does a > stat and gets a st_ino value back that won't fit in the 32 bit field, glibc > (correctly) generates an EOVERFLOW error. We can't do anything about f

[PATCH 1/3] make static counters in new_inode and iunique be 32 bits

2007-01-16 Thread Jeff Layton
When a 32-bit program that was not compiled with large file offsets does a stat and gets a st_ino value back that won't fit in the 32 bit field, glibc (correctly) generates an EOVERFLOW error. We can't do anything about fs's with larger permanent inode numbers, but when we generate them on the fly,

Re: [PATCH 1/3] make static counters in new_inode and iunique be 32 bits

2007-01-10 Thread Christoph Hellwig
On Mon, Jan 08, 2007 at 03:47:07PM -0500, Jeff Layton wrote: > When a 32-bit program that was not compiled with large file offsets does a > stat and gets a st_ino value back that won't fit in the 32 bit field, glibc > (correctly) generates an EOVERFLOW error. We can't do anything about fs's > with

[PATCH 1/3] make static counters in new_inode and iunique be 32 bits

2007-01-08 Thread Jeff Layton
When a 32-bit program that was not compiled with large file offsets does a stat and gets a st_ino value back that won't fit in the 32 bit field, glibc (correctly) generates an EOVERFLOW error. We can't do anything about fs's with larger permanent inode numbers, but when we generate them on the fly,

[PATCH 1/3] make static counters in new_inode and iunique be 32 bits

2006-12-29 Thread Jeff Layton
When a 32-bit program that was not compiled with large file offsets does a stat and gets a st_ino value back that won't fit in the 32 bit field, glibc (correctly) generates an EOVERFLOW error. We can't do anything about fs's with larger permanent inode numbers, but when we generate them on the fly,