i think a good idea would also be to compare clean 2.4.0-test5/8 and
the xfs tree - maybe it is not really an xfs issuse and more an
"redhat adds dozens of patches to its kernel" thing? - maybe
the same problem also exists with clean 2.4.0 ... just an
idea - maybe someone can try it out (have myself no 7.0
set up so far to test it)
t
utz lehmann <xfs@xxxxxxxxxx> wrote:
> hello
> redhat 7.0 ist unbootable with my xfs kernel (old one, cvs from 2000-08-17,
> compiled on redhat 6.2) with the same errors.
> the redhat 7.0 installation is on a ext2 partition.
> i have bootet the original redhat 7.0 kernel (2.2.16-22) and the xfs kernel
> (2.4.0-test5-xfs-20000817) with "init=/bin/bash" on lilo prompt. and done
> following:
> mount -orw,remount /
> strace -o ls.strace-`uname -r`
> i attached both strace outputs.
> i think the xfs kernel (all 2.4.0-test5 kernels?) returns the wrong error on
> fstat64.
> original redhat 7.0 kernel:
> [...]
> open("/", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 4
> fstat(4, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
> fcntl64(4, F_SETFD, FD_CLOEXEC) = -1 ENOSYS (Function not
> implemented)
> fcntl(4, F_SETFD, FD_CLOEXEC) = 0
> brk(0x8059000) = 0x8059000
> [...]
> xfs kernel:
> [...]
> open("/", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = 4
> fstat64(4, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
> fcntl64(4, F_SETFD, FD_CLOEXEC) = -1 EFAULT (Bad address)
> close(4) = 0
> write(2, "ls: ", 4) = 4
> write(2, "/", 1) = 1
> write(2, ": Bad address", 13) = 13
> write(2, "\n", 1) = 1
> close(1) = 0
> _exit(1) = ?
> hope that helps.
> utz lehmann
--
thomas.graichen@xxxxxxxxxxxxx
technical director innominate AG
clustering & security networking people
tel: +49.30.308806-13 fax: -77 http://innominate.de
|