https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-5655 Lustre <p>steps :<br/> 1. Mounted lustre<br/> 2. enabled hsm</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> # lctl set_param mdt.lustre-MDT0000.hsm_control=enabled </pre> </div></div> <p>3. Started copy tool daemon (only one copy tool agent can run on a client )</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> #lhsmtool_posix --daemon --hsm-root /tmp/HSM --archive=1 /mnt/lustre/ </pre> </div></div> <p>4. Only way to stop agent is to send TERM signal to agent as per lustre manual. So I killed it (as I wanted to run modified copy tool agent)</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> # ps -ef | grep lhs root 4017 1 0 16:54 ? 00:00:00 lhsmtool_posix --daemon --hsm-root /tmp/HSM --archive=1 /mnt/lustre/ root 4045 2110 0 16:55 pts/1 00:00:00 grep lhs </pre> </div></div> <p>5. Now I tried to start new copy tool agent</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> #lhsmtool_posix --daemon --hsm-root /tmp/HSM --archive=1 /mnt/lustre/ </pre> </div></div> <p> But got below message from kernel </p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> Sep 11 16:55:34 localhost kernel: Lustre: HSM agent b150c068-22f2-83cd-21b0-2b4e76a3082a already registered. </pre> </div></div> centos 6.5 LU-5655

lhsmtool_posix (copy tool agent) does not provide facility to un register

Improvement Critical Resolved Cannot Reproduce Bruno Faccini Vinayak Hariharmath HSM Wed, 24 Sep 2014 12:24:25 +0000 Wed, 25 Feb 2015 09:52:44 +0000 Wed, 25 Feb 2015 09:52:44 +0000 Lustre 2.5.0 Lustre 2.6.0 Lustre 2.7.0 0 9 <p>I feel once the daemon is killed , it should get unregistered. </p> <p>Is this a new problem in 2.6.0 or does the same problem exist in 2.5?</p> <p>I'm not able to reproduce this on 2.5.3. Whenever I kill the daemon, it stops running and the is no longer registered. </p> <p>It's not clear in the description that the <tt>ps</tt> in step 4 was run before or after you killed the copytool. If it is after, then clearly the daemon is still running for some reason and so it is still registered. </p> <p>ps in step 4 was run before I killed copy tool after that I killed it. Later I tried to start copy tool again but I got below message. Using b2_6 branch.</p> <p>Oct 14 17:53:59 localhost kernel: Lustre: HSM agent 0f4d5578-4a43-df67-a8b1-ce31a2c2cd3a already registered</p> <p>I'm seeing this on b2_6 as well, so this appears to be new in 2.6.0.</p> <p>Bruno,<br/> Can you please have a look at this one?<br/> Thank you!</p> <p>Ok. I just wonder if copytool death and unregister could not take longer than before in b2_6 and then if this ticket could be related to <a href="https://jira.whamcloud.com/browse/LU-5622" title="copytool_cleanup function should check/wait for copytool death" class="issue-link" data-issue-key="LU-5622"><del>LU-5622</del></a> ? But then, I also wonder why this does not currently affect auto-tests sanity-hsm results ?</p> <p>BTW I am unable to reproduce it with master/b2_6 builds.<br/> Robert, can you help me and detail the exact versions ad configuration you used to be able to reproduce ?</p> <p>I just tried again on a recent master build and wasn't able to reproduce it, either. I don't recall exact version of 2.6 I had been using, but the configuration would have been a single node setup using llmount.sh plus an additional mountpoint for the copytool. </p> <p>Vinayak, are you still able to reproduce the problem at your site?<br/> If yes can you help and provide more infos, because I am unable to reproduce for the moment?<br/> It would be nice if before running again your test/reproducer you can enable the full Lustre debug-log mask on both the CLient/Agent and MDS nodes, and then to provide them, can you do this ?</p> <p>Sure. I will verify it on my side and update the bug. Sorry I was stuck with other work and could not able update it. </p> <p>Vinayak, Any update ? Did you spend some time for more testing about this issue ? Could it be, as I suspected above, that the copytool unregister could take longer ?</p> <p>Hi </p> <p>Yes I have spent bit time on it to verify.<br/> The issue is not observed on master but still dmesg gives</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>Lustre: HSM agent 277f9613-7a7d-1caa-5849-0b5ffe11fdbb already registered </pre> </div></div> <p>but there is no problem with copy tool which works fine (Earlier with the above error message, copy tool was failing to start after killing it). I guess it only a grammar correction. Dmesg logs attached. </p> <p>Hello Vinayak,<br/> Do you agree if close this ticket as "Cannot reproduce" ?</p> <p>Hi Bruno,</p> <p>We can close this as "Cannot reproduce", but there is one more ticket <a href="https://jira.whamcloud.com/browse/LU-5216" title="HSM: restore doesn&#39;t restart for new copytool" class="issue-link" data-issue-key="LU-5216">LU-5216</a> looks bit similar to this issue. I am trying to reproduce it and draw some relation with this.</p> <p>Thanks</p> <p>According to the description in <a href="https://jira.whamcloud.com/browse/LU-5216" title="HSM: restore doesn&#39;t restart for new copytool" class="issue-link" data-issue-key="LU-5216">LU-5216</a>, then we may easily think that if both tickets are related, this one would only be a consequence of <a href="https://jira.whamcloud.com/browse/LU-5216" title="HSM: restore doesn&#39;t restart for new copytool" class="issue-link" data-issue-key="LU-5216">LU-5216</a> due to some orphan copytool thread still present or related data structure deferred/missing cleanup.<br/> So closing this one.</p> Development Epic client Project Rank 1|hzwwzj: Rank (Obsolete) 15853