On Thu, 15 Feb 2007, Nathaniel Rutman wrote:

Are there any test suite that should be run to "certify" the patchless
client for other (distribution specific) kernels? So that they can be
added to the wiki too?

We run a full suite of tests against each of these kernels -- but I have no objection to adding a "user reported" section that lists which kernels have been tried, and problems/successes associated. If you're building from source, the acceptance-small.sh suite under lustre/tests gives pretty good coverage, although that's intended to test servers also.

Hmm. I can't find acceptance-small.sh in the 1.5.97 tarball at least...

At the minimum, sanity.sh should be able to be run on a client.
Start your patchless client, then just
/lustre/tests# sh sanity.sh

Actually, env MOUNT=/path/to/your/filesystem sh sanity.sh, otherwise it will create a bunch of files in /mnt/lustre, and all lustre-specific tests will fail ;)

By the way, I don't think that sanity.sh has been sanitized to support patchless clients... I'm getting a lot of:
./sanity.sh: line 117: [: patchless: integer expression expected
which seems to make it skip all tests that checks for a lustre kernel version. I suspect that the correct approach is to apply all tests to patchless clients, not skip them.

Also, there are a number of funny dependencies... For example, I can't figure out where it should get socketserver and socketclient from.

On a side note, usleep seems to have been depreceated in modern distros. Use something like sleep 0.0005 instead.

/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se     |    [EMAIL PROTECTED]
---------------------------------------------------------------------------
 I never met a chocolate I didn't like. - Deanna
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

_______________________________________________
Lustre-discuss mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-discuss

Reply via email to