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-5173 Lustre <p>When try to shutdown or reboot the system freze on the umount on the filesystem.</p> <p>regards</p> redhat 5.7<br/> lustre-1.8.9-2.6.18_348.3.1.el5_g7880158 LU-5173

During the shutdown\reboot process the system hangs on filesytems umount.

Task Minor Resolved Not a Bug Cliff White Supporto Lustre Jnet2000 Wed, 11 Jun 2014 15:28:09 +0000 Thu, 26 Jun 2014 16:53:23 +0000 Thu, 26 Jun 2014 16:53:22 +0000 0 5 <p>Please provide us with some more detail on this incident. Are you referred to the umount of the clients, or the servers? Please attach system logs /var/log/messages for the affected machines for the time period when you are rebooting the system. Please provide us with some details of exactly how you are doing the shutdown. </p> <p>log client</p> <p>The problem is at the clients. I have attached the log of the client.</p> <p>regards</p> <p>Please provide more details of what problem you actually observed. Please provide a timestamp so I can reference the logs. <br/> When, exactly did this issue occur? What error messages concerned you?</p> <p>messages of umount</p> <p>hi, i hava attached the new log file</p> <p>regards</p> <p>You are furnishing quite a bit of data, but no information. <br/> Please:</p> <ul class="alternate" type="square"> <li>The exact time the incident occured.</li> <li>The exact error messages that concern you.</li> </ul> <p>Thank you.</p> <p>Sorry, but we don't have many more infos. The system hangs with umounting filestsems message. The attached putty.log contains all the console messages.</p> <p>Do you know what time the system hung? Do you know what day the system hung?<br/> I see no such hang in the console messages you have furnished. I do see that lustremount had to do a force umount, which is not an issue.</p> <p>2014-06-11T09:58:30.544811+02:00 osiride-lp-002 lustre_mclient: Ambiente macchina osiride-lp-002.utenze.bankit.it ERROR Lustre umount - force umount between 30 sec</p> <p>Was 09:58:30 on 2014-06-11 when you had an issue?</p> <p>These messages are from the forced umount and are harmless</p> <p>2014-06-11T11:15:04.956170+02:00 osiride-lp-002 kernel: LustreError: 9669:0:(ldlm_request.c:1039:ldlm_cli_cancel_req()) Got rc -108 from cancel RPC: canceling anyway<br/> 2014-06-11T11:15:04.956192+02:00 osiride-lp-002 kernel: LustreError: 9669:0:(ldlm_request.c:1597:ldlm_cli_cancel_list()) ldlm_cli_cancel_list: -108<br/> 2014-06-11T11:15:04.961406+02:00 osiride-lp-002 kernel: LustreError: 9669:0:(ldlm_request.c:1039:ldlm_cli_cancel_req()) Got rc -108 from cancel RPC: canceling anyway<br/> 2014-06-11T11:15:04.961417+02:00 osiride-lp-002 kernel: LustreError: 9669:0:(ldlm_request.c:1597:ldlm_cli_cancel_list()) ldlm_cli_cancel_list: -108<br/> 2014-06-11T11:15:04.972380+02:00 osiride-lp-002 kernel: Lustre: client home-client(ffff810fe05c4400) umount complete</p> <p>Were you having issues on 2014-06-11 at 11:15:04? </p> <p> If this issue re-appears, please attempt to determine a timestamp, collect system logs from all servers for the period 4 hours prior to the timestamp and collect relevant log entries from any impacted clients. </p> <p>I talked with the partner. The partner will look deep in the unmount script and in the position in the run level. Please hold on until the partner come back with more details.</p> <p>Dear Gabriele, the problem is not related to the runlevel, but is located in the /etc/init.d/lustremount script that doesn’t respect the rigth skeleton for the init files. According to redhat sample script, after a successuful start the file /var/lock/subsys/&lt;servicename&gt; must be created; the same file must be removed after a stop.</p> <p>See /usr/share/doc/initscripts-&lt;version&gt;/sysvinitfiles</p> <p>I fixed the script and now the shutdown/reboot works fine.<br/> Ciao ! See you at the next event ! <br/> Demetrio </p> <p>thank you Demetrio.<br/> Cliff, could you please close this ticket?</p> <p>Thanks Demetrio/Gabriele.</p> Development Rank 1|hzwo5j: Rank (Obsolete) 14360