INTL 3:770/1 3:770/3
REPLYADDR bnl@nowhere.com
REPLYTO 3:770/3.0 UUCP
MSGID: abfcb205
REPLY: 543279e4
PID: SoupGate-Win32 v1.05
On 2024-08-02 16:12, The Natural Philosopher wrote:
> On 02/08/2024 15:03, Björn Lundin wrote:
>> On 2024-08-02 14:51, The Natural Philosopher wrote:
>>
>>> Never mind sync.
>>>
>>> It's important to wait anyway on an SSD/nvm until it has finished its
>>> internal business.
>>>
>>> For any copy process.
>>
>>
>> dd'ing 500 Gb to an ssd disk, I've seen sync taking 30 s or more
>> and sync is of course started AFTER dd is done
>>
>> So - how do you know it is done its internal business?
>> Not all drives have blinking LEDs
>>
>> sync makes it easy to know
>>
>>
> Even sync may not be enough.
> SSDS/NVM have their own internal caching.
>
Then the question remains - how do you know when its done?
from man sync you get
"sync - Synchronize cached writes to persistent storage"
In other words, doing sync at least clear the cache,
which must be better than nothing? or?
Or are you saying that ripping the power to a newly sync()ed disk may
mess it up?
as in
dd ....
sync
rip out usb cord for a 2.5" ssd sata in a usb case or something similar ?
--
/Björn
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 1/19 16/0 19/37 80/1 90/1 105/81 106/201 123/130 129/305
SEEN-BY: 142/104 153/757 7715 203/0 218/700 840 220/70 221/1 6 242
SEEN-BY: 221/360 226/17 30 100 227/114 229/110 111 114 200 206 300
SEEN-BY: 229/317 400 426 428 470 550 616 664 700 230/0 240/5832 266/512
SEEN-BY: 267/800 280/5003 282/1038 291/111 292/854 301/1 310/31 320/119
SEEN-BY: 320/219 319 2119 322/757 762 325/304 335/364 341/66 342/200
SEEN-BY: 396/45 423/81 460/58 633/280 712/848 770/1 3 100 330 340
SEEN-BY: 772/210 220 230 5020/400 5053/58 5058/104 5075/35
PATH: 770/3 1 218/840 221/6 1 320/219 229/426
|
