search for: 275s

...5KZ\357\277\275IW_\357\277\275/Y\357\277\275|\357\277\275%\357\277\275W\357\277\275^/\357\277\275/\357\277\275\027\357\277\275\v\372\213\274\266\277 \020D\357\277\275\002\357\277\275Q\357\277\275B\357\277\275<\357\277\275\rH\357\277\275<'E\357\277\275\022\357\277\275X\357\277\275$\357\277\275S\357\277\275\bE\020YN\357\277\275"..., size=8815) at squat-trie.c:934 trie = <value optimized out> data = 0x964a5a8 "" char_lengths = 0x9648338 "\001\003\001\001\001\001\003\001\001\001\001\001\001\001\001\001\001\003\001\001\001\001\003\001\001\001\...

...operations manual (version 1.9) does not say a lot about options for balancing the work load among OSSs/OSTs. Shouldn''t lustre be doing a better job (by default) of distributing the workload? Charlie Taylor UF HPC Center FWIW, the servers are dual-processor, dual-core Opterons (275s) with 4GB RAM each. They are running CentOS 5 w/ a 2.6.18-8.1.14.el5Lustre (patched lustre, smp kernel) and the deadline I/O scheduler. If it matters, our OSTs are atop LVM2 volumes (for management). The back-end storage is all Fibre-channel RAID (Xyratex). We have tuned the ser...

My setup is as follows: Motherboard: Tyan S2895 CPU: Two Opteron 275s Memory: 4 GB Disk: Three 250 GB SATA drives attached to a 3Ware 9500S-4LP RAID card Video: Nvidia GeForce 7800 The only hardware that I have added to the motherboard is the 3Ware card and the Nvidia card. The disks are configured as a RAID 5 array, and the machine boots from this array. I installe...

...one I try to install a suse11 pv guest on redhat5.2 virtualization platform. But the startup process hung with messages: xen-vbd: registered block device major 202 xvda:<6>netfront: Initialising virtual ethernet driver. XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...<6>Uniform Multi-Platform E-IDE driver SCSI subsystem initialized st: Vers...

...bb ea ff ff ff 0f 84 03 01 00 00 49 [ 173.234105] RIP [<ffffffff81141dd7>] internal_create_group+0x28/0x15a [ 173.234120] RSP <ffff88003fe05d30> [ 173.234129] ---[ end trace e52b5afb691890a0 ]--- [ 178.140021] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s... If I wait until the timeout expires the installer goes on but the partitioner only recognizes two of my three configured disks and therefore I cannot install as desired. Now today I finally tried to install it as HVM but I get exactly the same stacktrace and issue. Any hints what to do or wha...

...el/PLANTILLA_D1,xvda1,w'', ''phy:/dev/disk/by-label/PLANTILLA_SW,xvda2,w''] the VM do not boot. Below are the console messages: ... [ 0.241307] Initialising Xen virtual ethernet driver. [ 5.340090] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...udevd[59]: timeout: killing ''/sbin/modprobe -b xen:vbd'' [69] udevd[59]: ''/sbin/modprobe -b xen:vbd'' [69] terminated by signal 9 (Killed) udevd[61]: timeout: killing ''/sbin/modprobe -b xen:vbd'' [...

...ried to migrate UBUNTU_10.04.iso from pc 1(front > node) to pc 2(cluster node) [...] > PCI: setting up Xen PCI frontend stub [...] > PCI: System does not support PCI > PCI: System does not support PCI [...] > XENBUS: Waiting for devices to initialise: > 295s...290s...285s...280s...275s...270s...265s...260s...255s... Haven''t a clue. Xenbus never initializes, the devices are not enumerated, so device driver loading, and the rest of the boot sequence never occurs. I assume this domu booted fine on the first node, so look for differences between the hardware on the two n...

...rtc_cmos: rtc core: registered rtc_cmos as rtc0 [ 0.976298] No iBFT detected. [ 0.976641] TCP cubic registered [ 0.976647] NET: Registered protocol family 17 [ 0.976739] registered taskstats version 1 [ 6.077230] XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s....

...ating block device nodes. Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading jbd.ko module Loading ext3.ko module Loading xenblk.ko module XENBUS: Waiting for devices to initialise: 295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s....

This morning I''ve had both my infiniband and tcp lustre clients hiccup. They are evicted from the server presumably as a result of their high load and consequent timeouts. My question is- why don''t the clients re-connect. The infiniband and tcp clients both give the following message when I type "df" - Cannot send after transport endpoint shutdown (-108). I''ve

...= {part = 0xa0440b0, hdr = 0x0, data = 0xc9b9e90 "\031\357\277\275\067S\357\277\275^\fP\357\277\275B\357\277\275Q\357\277\275]\020\357\277\275=Z\357\277\275NL]}\357\277\275\023\357\277\275!U\357\277\275WV\357\277\275$\357\277\275I\357\277\275\020Z$\357\277\275J\357\277\275A\357\277\275S6\357\277\275T\357\277\275\031#\357\277\275@\357\277\275\006\357\277\275\070\357\277\275W6`\357\277\275A\357\277\275\r6\357\277\275S\034\357\277\275\017\357\277\275\v\357\277\275\n\357\277\275\024\357\277\275\017\357\277\275^\357\277\275{\357\277\275\n\357\277\275-\357\277\275\322\256PV\021\357\277\...

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and