On Feb 21, 2007 08:30 -0800, David Brown wrote: > >While testing 1.5.97 on kernel 2.6.18, I had the following Oops on a > >client. > > > >Unable to handle kernel paging request at ffff88000b17fff8 RIP: > > [<ffffffff8843951a>] :osc:osc_brw_prep_request+0x3e3/0x9e2
Can you please decode this to a line number? If you do "gdp .../osc.ko" and "list *(osc_brw_prep_request+0x3e3)" it should give you a line number. > >Note: the client was running on a Xen dom0, with fairly small memory, so > >lustre is not necessarily at fault. > >Further details on request. > > Yeah I found running lustre in xen is kinda difficult when trying to > partition out the memory, I use at least 512M for all lustre involved > components of my xen/lustre systems. Strange. I've run 1.4 with client + MDS + 5 OSTs in a single 96MB UML. The memory allocated by lustre generally scales as a function of RAM in the system, so that it can at least function in lower-memory environments. That said, I haven't run 1.6 in this environment. Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc. _______________________________________________ Lustre-discuss mailing list [email protected] https://mail.clusterfs.com/mailman/listinfo/lustre-discuss
