Displaying 3 results from an estimated 3 matches for "375g".
Did you mean:
375
2015 Nov 30
1
Re: "Failed to start domain..."
...1|f\30<2
\347\276\37T:>|\241\2403\256\203GN\316=\233N\221\313\32\3630{\255\374O\360\263\374\353l\324\206\272o['I\205+\30\351\304LG\374\202\216\260\340H\342eL\214\377\3131(@:C\202\300\354x\235D\256\355\204G\261\rT5\247lK\364\342\7\232\231\210\25o\23\275\260\325\337\17E\255\300\211\254\277k\375g\347\347\5\273\324\255\324\220A\311\305\365{,J\351DE\245\337\272JBr\243\361\r\2226\330S\354\212$b\1J\37&C\200\225U\351\335",
8192) = 176
25533 close(4) = 0
25533 close(5) = 0
25533 clock_gettime(0x7 /* CLOCK_??? */, {17970, 938396231}) = 0
25533 clock_gettime(0x7 /* CLOCK_??? */, {17970...
2015 Nov 25
2
"Failed to start domain..."
Sadly, I'm back with another issue. I can do a "system list --all" just
fine; however, if I attempt to start the machines, I get back:
maas@Bill-MAAS-cc:~$ strace -s 1024 -f -o /tmp/asdfasdf.log virsh -c
vbox+ssh://gbadmin@10.20.0.1/system start PXE-client-07
error: Failed to start domain PXE-client-07
error: An error occurred, but the cause is unknown
Log files on both client
2011 May 13
27
Extremely slow zpool scrub performance
Running a zpool scrub on our production pool is showing a scrub rate
of about 400K/s. (When this pool was first set up we saw rates in the
MB/s range during a scrub).
Both zpool iostat and an iostat -Xn show lots of idle disk times, no
above average service times, no abnormally high busy percentages.
Load on the box is .59.
8 x 3GHz, 32GB ram, 96 spindles arranged into raidz zdevs on OI 147.