2009/9/10 George Mamalakis <mama...@eng.auth.gr>: [about aac0: COMMAND 0xffffff80003d9440 TIMEOUT AFTER 40 SECONDS] >> It looks like the controller was too busy rebuilding to take any new >> requests. It is possible you have filled the controller's write cache and >> that is why the lag happened at this point. You can easily test this theory. >> > This is the exact reason why I am asking this question. If this behavior is > normal, then there is no problem with me. But I couldn't be sure whether it > was a driver's problem or a controller's problem. >
I see it from time to time on a number of boxes. You can often ignore this. It might be due to (and a symptom of) high disk workload. Btw, there was a recent change to increase command timeout to 120s. > Thank you for your answer again, and (now that you mentioned it:) ) in case > anyone knows whether we'll be able to see partitions > 2T in the future (or > now?!), please say how :). > Look at gpart(8). -- wbr, pluknet _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
