On 7/5/24 3:22 AM, Tim via users wrote:
So I typed sync, and that stayed doing something until the
flashdrive stopped blinking, then the cursor returned immediately. So,
I'm tempted to think that the caching delay was part of the OS rather
than the drive.
Your reaction is likely to be right. There is cache in the OS. And it is
causing sync to block for a while.
Samuel Sieb:
>> The writing is finished when dd exits, but the drive might keep
flashing
>> briefly after that. Or maybe the drive has some internal caching that
>> it doesn't advertise (that would be very bad).
I have gone through man pages of `dd` and find executing `sync` right
after the writing finished may not be enabled by default. That requires
passing `oflag=sync` or passing nocache to `conv=`, but non of the above
is done in the command you provided. I guess probably dd did leave
kernel cache behind and exit.
Running `sync` and just wait for lights to not blink any more is always
very wise. And it also indicates that your installation medium is
probably OK.
--
Tide Ka
Disclaimer: https://about.ctide.dev/DISCLAIMER
https://about.ctide.dev/
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
