Skip to content
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

[sonic_install] sync filesystem after file copy is done #189

Merged
merged 2 commits into from
Jan 18, 2018

Conversation

yxieca
Copy link
Contributor

@yxieca yxieca commented Jan 18, 2018

- What I did
sync file system after all copies and installations are done.

- How to verify it
With platform specific reboot tool power cycling devices, it is highly repeatable that some file would be missing after sonic_install.

The fix is verified under the same circumstances.

The issue turns out not related to this sync. But putting the sync at the end of the execution list by itself is a good practice anyways.

@pavel-shirshov
Copy link
Contributor

About sync. The sync command doesn't guarantee that you got your disk in sync state when the command returns. You need to wait until all disk are synced. Usually 'sleep 3' works in 90% of time.
But you can also read information about the sync operation progress here:
https://unix.stackexchange.com/questions/48235/can-i-watch-the-progress-of-a-sync-operation

@yxieca
Copy link
Contributor Author

yxieca commented Jan 18, 2018

Thanks for pointing that out. Pavel! I added a 3 second delay after sync.

Regards,
Ying

@yxieca yxieca merged commit c6bcfa6 into sonic-net:master Jan 18, 2018
@yxieca yxieca deleted the installer branch January 18, 2018 23:52
vdahiya12 pushed a commit to vdahiya12/sonic-utilities that referenced this pull request Jul 23, 2021
Description
Refactor the pcied and add the unit test

Motivation and Context
Added unit test to increase the pmon unit test coverage.

How Has This Been Tested?
Build with unit test enabled and run manually on a dut to verify the pcied.
stepanblyschak pushed a commit to stepanblyschak/sonic-utilities that referenced this pull request Apr 28, 2022
35fec8528bbf3fad9451554de16922f8c59dda4 (HEAD -> 201911, origin/201911) [201911]: security update kernel to 4.9.246 (sonic-net#188)
d992e63eee24a6a598e58c8b2b468e5440ae56f0 [ci]: add azure pipeline for 201911 (sonic-net#189)

Signed-off-by: Abhishek Dosi <[email protected]>
mihirpat1 pushed a commit to mihirpat1/sonic-utilities that referenced this pull request Sep 15, 2023
…t#189)

Description
Added constants to component_base for each potential return code of auto_firmware_update() so that vendor specific component implementations may reference these to provide the correct return codes to the firmware auto update utility.

Motivation and Context
This provides a central location from which standardized return codes may be imported, preventing the need for potential inconsistency in vendor implementations or the use of magic numbers in vendor implementations for return code.

How Has This Been Tested?
Non-functional change, builds successfully and can be successfully imported from at runtime.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants