[lustre-discuss] question regarding du vs df on lustre

Andreas Dilger adilger at whamcloud.com
Mon Apr 11 09:01:42 PDT 2022

Lustre is returning the file unlink from the MDS immediately, but deleting
the objects from the OSTs asynchronously in the background. 

How many files are being deleted in this case?  If you are running tests
like IO500, where there are many millions of small files plus some huge
files, then it may be that huge object deletion is behind small objects?

That said, it probably shouldn't take hours to finish if the OST storage is
NVMe based. 

Cheers, Andreas

> On Apr 4, 2022, at 05:05, Einar Næss Jensen <einar.nass.jensen at ntnu.no> wrote:
> Hello lustre people.
> We are experimenting with lustre on nvme, and observe the following issue:
> After running benchmarks and deleting benchmark files, we see that df and du reports different sizes:
> [root at idun-02-27 ~]#  du -hs /nvme/
> 38M     /nvme/
> [root at idun-02-27 ~]# df -h|grep nvme
> at o2ib:/nvme                   5.5T  3.9T  1.3T  76% /nvme
> It takes several hours before du and df agrees.
> What is causing this?
> How can we get updated records for df immediately when deleting files?
> Best REegards
> Einar
> _______________________________________________
> lustre-discuss mailing list
> lustre-discuss at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org

More information about the lustre-discuss mailing list