From: "Degremont, Aurelien via lustre-devel" <lustre-devel@lists.lustre.org>
To: "lustre-devel@lists.lustre.org" <lustre-devel@lists.lustre.org>
Subject: [lustre-devel] Recommendation for hsm_restore for directories
Date: Thu, 25 Nov 2021 10:18:15 +0000 [thread overview]
Message-ID: <81C95C19-8B9F-47F3-B827-AEA3B9D6E91C@amazon.com> (raw)
Hello all
I'm doing some early work toward implementing a directory/namespace support for Lustre/HSM. The idea would be to support something similar to hsm_restore/hsm_release but for directories.
My first thought was for the MDT to not grant LDLM lock for this directory and hold it, while the directory is getting restored by copytool, in a similar fashion than what is done for files. But the hard part here, is to have a way for copytool to access the directory while its access is actually prevented by the above locking.
Restoring a file is using this smart trick of restoring it in a different temporary file and using layout swap at the end to move data to the actual real file. It looks difficult to do the same thing here.
Do you have any recommendation on the right way to frame this directory access for copytools?
Aurélien
_______________________________________________
lustre-devel mailing list
lustre-devel@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
next reply other threads:[~2021-11-25 10:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 10:18 Degremont, Aurelien via lustre-devel [this message]
2021-11-25 14:32 ` [lustre-devel] 回复: Recommendation for hsm_restore for directories Qian Yingjin via lustre-devel
2021-11-25 15:32 ` Degremont, Aurelien via lustre-devel
-- strict thread matches above, loose matches on Subject: below --
2021-11-24 17:33 [lustre-devel] " Degremont, Aurelien via lustre-devel
2021-12-08 21:09 ` Andreas Dilger via lustre-devel
2021-12-15 15:33 ` Degremont, Aurelien via lustre-devel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81C95C19-8B9F-47F3-B827-AEA3B9D6E91C@amazon.com \
--to=lustre-devel@lists.lustre.org \
--cc=degremoa@amazon.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).