-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix "/host unmount failure" during reboot #4558
Conversation
retest broadcom please |
retest vsimage please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As comments
Do you have new commit for reviewing? |
Hi Qi, I'm working on the changes. I will commit it soon. |
Here's an observation. In stretch based builds:
In buster based builds:
We do really want the reboot to happen through the platform specific tool. |
Hi Joyas, In S6100 and Z9100, platform reboot is happening using systemd services to ensure graceful unmount. |
Hi Qi, committed the last changes addressing the review comments. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me. Please also check other reviews's comments
Qi/Joyas, Please let us know if there is there any further queries on this for the merge to happen. |
Why the title contains 'DellEMC', I think it is a general fix. |
Yeah Right. I will change it.. |
Looks good to me. |
Fix for the host unmount issue through PR #4558 and #4865 creates the timeout of syslog.socket closure during reboot since the journald socket closure has been included in syslog.socket Removed the journal socket closure. The host unmount is fixed with just stopping the services which gets restarted only after /var/log unmount and not causing the unmount issues.
Fix for the host unmount issue through PR #4558 and #4865 creates the timeout of syslog.socket closure during reboot since the journald socket closure has been included in syslog.socket Removed the journal socket closure. The host unmount is fixed with just stopping the services which gets restarted only after /var/log unmount and not causing the unmount issues.
Fix for the host unmount issue through PR #4558 and #4865 creates the timeout of syslog.socket closure during reboot since the journald socket closure has been included in syslog.socket Removed the journal socket closure. The host unmount is fixed with just stopping the services which gets restarted only after /var/log unmount and not causing the unmount issues.
- Why I did it
During /sbin/reboot, the /host unmount failure happened.
- How I did it
The /var/log is mounted as a separate ext4 filesystem. This ext4 filesystem is associated with a loop device and mounted along with root partition.This loop device association needs to be detached after unmounting /var/log which systemd is not performing.
The script to stop the journal services, unmount /var/log and detele the loop device has been invoked at the closure of syslog.socket.
- How to verify it
I have verified the 100 iterations of reboot and confirmed issue has been fixed in all dell platforms.
Once the device is up, have checked if the /var/log, host partitions has been mounted properly.
Fast-boot, warm-boot and normal reboot has also been verified.
- Description for the changelog
Fixed the /host unmount failure issue.
Attaching the logs of 100 iterations in S6100 device.
- A picture of a cute animal (not mandatory but encouraged)
logs_S6100.txt