I tried remounting the /home lustre file system to /mnt in read-only mode
and when I try to ls the directory it locks up but I can escape it, how
ever when I do a df command i get the completely wrong size (should be
around 192TB):
10.140.93.42@o2ib:/home6.0P 4.8P 1.3P 80% /mnt
zfs scrub
>
>
>2. Tools to check a lustre (Sid Young)
>4. Re: Tools to check a lustre (Dennis Nelson)
>
>
> My key issue is why /home locks solid when you try to use it but /lustre
is OK . The backend is ZFS used to manage the disks presented from the HP
D8000 JBOD
I'm at a loss after 6 months of
Have you tried lfs check servers on the login node?
Sent from my iPhone
On Oct 11, 2021, at 2:58 AM, Sid Young via lustre-discuss
wrote:
I'm having trouble diagnosing where the problem lies in my Lustre
installation, clients are 2.12.6 and I have a /home and /lustre filesystems
using
Hello
This message is appearing during MDT recovery, likely after a MDS restart. MDT
tries to reconnect first all existing client when it stopped.
It seems all these clients have been also rebooted. To avoid this message, try
to stop your clients before the servers.
If not possible, you can
I'm having trouble diagnosing where the problem lies in my Lustre
installation, clients are 2.12.6 and I have a /home and /lustre
filesystems using Lustre.
/home has 4 OSTs and /lustre is made up of 6 OSTs. lfs df shows all OSTs as
ACTIVE.
The /lustre file system appears fine, I can *ls *into
