Dear Dr. Arman,
I have checked inodes availability on all OST's and MDT's and they are all less
than 2%. I believe like you said stripe count could be an issue. Our default stripe count
is 1 and the applications that are running out of space are probably writing to an OST
that have reached 100% on its space usage. But I assumed this being the most common case,
this is something Lustre would handle it on its own? What puzzles me is why would a copy
command fail at times, because during a copy I am sure file system would checked on
available space on an OST and then obtained an Object index to write to where there was
enough space.
Do I get this right? Or Am I missing something? Should I change my default stripe count on
the file system to higher than 1?
Thank you for your prompt response!!
Amit
-----Original Message-----
From: Arman Khalatyan [mailto:arm2arm@gmail.com]
Sent: Monday, June 01, 2015 10:58 AM
To: Kumar, Amit
Cc: hpdd-discuss(a)lists.01.org
Subject: Re: [HPDD-discuss] Strange Issue, No space left, where there actually
over 500TB
hi,
we had similar trouble when one of the bricks was running out of inodes.
it depends how you stripe your data.
If you use for writing the full bricks it will trow out of space error.
***********************************************************
Dr. Arman Khalatyan eScience -SuperComputing
Leibniz-Institut für Astrophysik Potsdam (AIP) An der Sternwarte 16, 14482
Potsdam, Germany
***********************************************************