busybox: revert dd fsync change which makes no sense #1862
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change (introduced in 1.27.0) makes no sense - if anyone wanted to perform a single sync they would do that with
dd && sync
without changing the entire behaviour ofconv=fsync
.Following this change in
busybox
, the upgrade progress indicators are useless asdd bs=1M conv=fsync
no longer performs a sync every 1MB - there are now long delays where there is no progress, and then the progress jumps to 50% and finally 100% as the entire transfer is synced at the end (rather than at regular intervals during the transfer prior tobusybox
1.27.0).I've opened a bug: https://bugs.busybox.net/show_bug.cgi?id=10191
Apologies for not catching this sooner, I had assumed my SD card was on the fritz...!