On Sun, 2009-09-27 at 11:41 -0400, Brian J. Murrell wrote:
On Sun, 2009-09-27 at 14:58 +0200, Nick Jennings wrote:
I can look into all of these possibilities soon, and try to get more
information the next time it happens, but as I understand it from
reading the bug, this is already a
On Sat, 2009-09-26 at 14:20 -0400, Oleg Drokin wrote:
On Sep 26, 2009, at 9:37 AM, Brian J. Murrell wrote:
Unfortunately that was the only info I could get. The client had no
information in the logs about what happened.
They usually don't when they panic.
Right.
RHEL configured to
On Sun, 2009-09-27 at 14:58 +0200, Nick Jennings wrote:
I can look into all of these possibilities soon, and try to get more
information the next time it happens, but as I understand it from
reading the bug, this is already a known issue, and hasn't been fixed
yet (slated for 2.0 release as
Hello!
On Sep 26, 2009, at 1:57 AM, Nick Jennings wrote:
About an hour ago the client completely hung. Hosting co. says it was
a kernel panic. I got not useful feedback in /var/log/messages from
the
client or the MDS. However from the OST I got several complaints.
(below).
Does anyone
On Sat, 2009-09-26 at 14:53 +0200, Nick Jennings wrote:
Heya Nick,
Unfortunately that was the only info I could get. The client had no
information in the logs about what happened.
They usually don't when they panic.
The MDS only had the
following entry near the time:
Sep 25 22:28:43
Hello!
On Sep 26, 2009, at 9:37 AM, Brian J. Murrell wrote:
Unfortunately that was the only info I could get. The client had no
information in the logs about what happened.
They usually don't when they panic.
Right.
RHEL configured to have panic on oops too, if you disable that (in /
Hello All,
I'm running lustre v1.6.7.2 - I've got one of each (mds, oss, client).
The client serves apache off the lustre volume.
About an hour ago the client completely hung. Hosting co. says it was
a kernel panic. I got not useful feedback in /var/log/messages from the
client or the MDS.
