On Mar 19, 2020, at 12:56, Lana Deere
mailto:lana.de...@gmail.com>> wrote:
The MDT shows 6% of storage in use and 9% of inodes in use. The OST, however,
shows 46% of storage and 100% of inodes in use (12 free). (There is only one
OST on this particular file system.) I suppose if a lot of
you may need to delete more files, and wait for a while for MDS gets
updated.
Best,
Feng
On Thu, Mar 19, 2020 at 2:56 PM Lana Deere wrote:
> The MDT shows 6% of storage in use and 9% of inodes in use. The OST,
> however, shows 46% of storage and 100% of inodes in use (12 free). (There
> is
The MDT shows 6% of storage in use and 9% of inodes in use. The OST,
however, shows 46% of storage and 100% of inodes in use (12 free). (There
is only one OST on this particular file system.) I suppose if a lot of
files are deleted, the system will recover, but then I'm not sure why I
couldn't
Hi Lana,
Lustre dispatches the data across several servers, MDTs and OSTs. It is likely
that one of this OST is full.
To see the usage per sub-component, you should check:
lfs df -h
lfs df -ih
See if this reports one OSTs or MDT is full.
Aurélien
De : lustre-discuss au nom de Lana
Deere
I have a Lustre 2.12 setup running on CentOS 7. It has been working fine
for some months but last night one of my users tried to untar a large file,
which (among other things) created a single directory containing several
million subdirectories. At that point the untar failed, reporting "no
