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 <[email protected]> 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@idun-02-27 ~]# du -hs /nvme/ > 38M /nvme/ > [root@idun-02-27 ~]# df -h|grep nvme > 10.3.1.2@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 > [email protected] > http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org _______________________________________________ lustre-discuss mailing list [email protected] http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org
