I have a Lustre (1.6.7) system that looks OKish (as far as I can see) from the
mds and most of the clients. From one client however (the users' login machine)
it looks broken. Some files are missing, some seem broken, and the df command
hangs.
Rebooting the client doesn't change anything. Is
Could you elaborate about how broken the files are?
From your description and the error message you provide, I suspect that one(or
some) of the OSTs went down. What does `lctl dl` show?
在 2010-11-18，下午8:18， Herbert Fruchtl 写道：
I have a Lustre (1.6.7) system that looks OKish (as far as I can
Hi,
在 2010-11-17，上午9:17， Nihir Parikh 写道：
Now my problem is to run some network tests from S2 à S3 and S3 à S2 to
measure the bandwidth but somehow both S2 and S3 complain that network is
unreachable. What am I doing wrong?
Your configuration seems OK to me. Can S2 and S3 ping each
Hello,
在 2010-11-18，下午10:03， Herbert Fruchtl 写道：
I was wrong about only one client having problems. It seems to
be all of them, except the mds server (see below), so it is a
problem of the filesystem (not the client) after all.
Could you elaborate about how broken the files are?
When I
Wang Yibin wrote:
Hello,
在 2010-11-18，下午10:03， Herbert Fruchtl 写道：
I was wrong about only one client having problems. It seems to
be all of them, except the mds server (see below), so it is a
problem of the filesystem (not the client) after all.
It looks like you may have corruption on the
Sorry, I had meant to cc this to the list.
Herbert
---BeginMessage---
Hi Kevin,
That didn't change anything. Umounting the of the OSTs hung (yes, with an LBUG),
and I did a hard reboot. It came up again, and the status is as before: on the
MDT server, I can see all files (well, I assume
Hello!
On Nov 18, 2010, at 7:18 AM, Herbert Fruchtl wrote:
Rebooting the client doesn't change anything. Is it broken, or is there some
persistent information that I need to flush? When I do an ls on a partially
broken directory, I get the following two lines in /var/log/messages:
Nov 18
Thanks Wang,
Hi,
�� 2010-11-17��5:18�� Thomas Johansson д
Hi all,
I accidentally added an ost using an fsname belonging to another fs than
what was intended.
I am not sure I understand - Do you have multiple filesystems sharing the
same MGS?
Yes 5 filesystems on 4 OSS:s and 2
Hello!
So are there any other compplaints on the OSS node when you mount that OST?
Did you try to run e2fsck on the ost disk itself (while unmounted)? I assume
one of the possible problems is just on0disk fs corruptions
(and it might show unhealthy due to that right after mount too).
Bye,
