> Steve,
>
> The disk under the hood is IBM raid array (sharks?). We're seeing them
> through a qlogic driver to the SAN.
>
> If you've got any tuning params. or patches for me to try, let me know.
> We like the performance of xfs (what we were able to measure), but need to
> pick a filesystem soon. This will be the filesystem behind our 512 host
> linux cluster at NCSA.
>
> I downloaded the development tree from your cvs server, but was not able
> to "make bzImage" on linux 2.4.4:
>
>
> gcc -I/usr/include -ldb1 aicasm_gram.c aicasm_scan.c aicasm.c
> aicasm_symbol.c -o aicasm aicasm_symbol.c:39: db1/db.h: No such file or
> directory
> make[5]: *** [aicasm] Error 1
>
> So we're still on linux 2.4.2. I down-graded the system for testing xfs
> because your web site made it look like 2.4.2 was the development
> platform. If you've got a working 2.4.4 version I'd like to try it out
> (that's what the rest of the cluster is running).
>
> -Galen
>
I would really encourage you to get the 2.4.4 xfs kernel up and running,
I am much happier with the code base we have there now, and we cannot yet
replicate the problem with the development tree. Hmm, maybe fiber is the
difference, the qlogic driver has a patchy history in linux.
Steve
|