Sync: Difference between revisions

From Leo's Notes
This page was last edited on 10 February 2020, at 22:50.
mNo edit summary
mNo edit summary
Line 6: Line 6:
}}
}}


If something is wonky with your disk or network share, {{code|sync}} may hang. If a reboot is issued, the reboot will also hang when attempting to call {{code|sync}}. In such circumstances, it might be desirable to do a force reboot ({{code|reboot -f}}) or by rebooting using [[Sysrq#Rebooting|Sysrq]] both of which foregoes syncing.
If something is wonky with your disk or network share, {{code|sync}} may hang. If a reboot is issued, the reboot will also hang when attempting to call {{code|sync}}. In such circumstances, it might be desirable to do a force reboot ({{code|reboot -f -f}}) or by rebooting using [[Sysrq#Rebooting|Sysrq]] both of which foregoes syncing.




{{Navbox Linux}}[[Category:Linux]]
{{Navbox Linux}}[[Category:Linux]]

Revision as of 22:50, 10 February 2020

The sync system call writes dirty buffers to the file system or disk.

The progress of sync can be viewed indirectly by:

# grep -e Dirty: -e Writeback: /proc/meminfo

If something is wonky with your disk or network share, sync may hang. If a reboot is issued, the reboot will also hang when attempting to call sync. In such circumstances, it might be desirable to do a force reboot (reboot -f -f) or by rebooting using Sysrq both of which foregoes syncing.