[Xen-devel] Weekly Samba & Mysql stress testing

[Rick Gonzalez <rcgneo@xxxxxxxxxx>]

December 12, 2005

* Xen BUILD:
changeset:   8241:0255f48b757f
tag:         tip
user:        cl349@xxxxxxxxxxxxxxxxxxxx
date:        Sun Dec  4 13:12:00 2005 +0100
summary:     Temporarily remove NetBSD and FreeBSD sparse trees to avoid
user confusion.

* Testing Hardware:

   HW ID   Model   Procs.   Mem.    ARCH     Distro
   -----   -----   ------   ----   ------    ------
   A       x335    2        2GB    x86_32  SLES9-GA-SP2
   B       HS20    2        2GB    x86_64  SLES9-GA-SP2
   C       HS20    2        1GB    x86_64  SLES9-GA-SP2

* Xen Setups(NOTE: for HW ID look above):
                                        Dom0
   DomUs(same config)
   Setup
   ID    HW ID   CPUs    Mem    DomUs  CPUs  Mem  PAE
   ---   -----   -----   ----   -----  ----  ---  ---
   1       A       1     256MB   2      1   512MB NO
   2       B       1     256MB   2      1   512MB NO
   3       C       1     256MB   2      1   256MB NO
   4       A       1     256MB   2      1   512MB YES

* Test Status(NOTE: for Setup ID look above):

   - All stress testing is done DomU(client) to DomU(server).

   Setup ID    Workload   Test Tool   24hr   96hr   Errors(Y/N)
   --------   ---------   ---------   ----   ----   -----------
   1           MySql       DOTS        P      P         N
   2           MySql       DOTS        P      P         N
   3           Samba       fsstress    F      F         Y
-----------------------------------------------------------------

        Legend: P=pass, F=fail, Y=yes, N=no

* Issues / Comments:

Setup ID #3:

- I'm doing quick runs on Samba & fsstress to debug problem. Here is 
what I'm getting after the benchmark is done:
 smb_lookup: find d3a9XXXXXXXXXXXXXX/d3f1 failed, error=-36

NOTE: this message is coming from smbfs and not from Samba.

- This message is generated on the Client system(wherever you are
running fsstress from). I ran domU to domU, and dom0 to domU and on 
distro kernel and I get the error on all setups.
- I will open a bug after I analyze the problem further.


* Results:

- Please let me know if you would like to see the results.






_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel