We are running Lustre 2.1.6 on Scientific Linux 6.4, kernel
2.6.32-358.11.1.el6.x86_64. This was an upgrade from Lustre 1.8.4 on SL5.
We have had a few situations lately where a client stops talking to some
subset of the OST (about 58 of these total on 8 OSS, nearly 500TB in
total). I have a
That is an interesting mix. Nothing shows up at all on the clients,
even on those 3 that route to a second NIC. On the OSS, it is quite the
mix of up/down on the 3 routers, with no obvious pattern.
Most of our traffic is on the 10.10 network, with the 3 machines shown
below routing to a smal
There are very few clients right now on the tcp2 network. AFAIK, they
are happy. No one is complaining, but they may not be using the Lustre
storage right now, either.
bob
On 9/5/2013 4:22 PM, Kris Howard wrote:
If you lctl ping 10.10.X.XX@tcp from both sides it should bring the
route up.
The following message is a translated version of the email we distributed
announcing the upcoming APAC LUG events. We encourage you to circulate the
notice below to any of your Japanese colleagues or contacts. The previous
English email is also attached for reference.
イベント日程案内
中国 北京
２０１３年１
