On Tue, 19 Feb 2008, David Chinner wrote:
> I did not use a patched mkfs - just my patch that does correction.
> I think I need to test this on an x86_64 box and see if i can
> reproduce it locally because it's not obviously operator error
> or clearly an 32/64bit problem...
Will you have possibility to test it in near future or should I rather
recreate my FS's with lazy-count=0 to keep the data safe?
Maybe this information can be useful. Kernel and userspace tools were
# gcc -v
Using built-in specs.
Configured with: ../configure --enable-threads=posix --prefix=/usr
--mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64
--enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib64
--with-system-zlib --enable-shared --enable-__cxa_atexit
--without-system-libunwind --with-cpu=generic --host=x86_64-suse-linux
Thread model: posix
gcc version 4.2.1 (SUSE Linux)