| |||||||||||||
Yet another opportunity for opportunistic suspendYet another opportunity for opportunistic suspendPosted Oct 27, 2011 16:10 UTC (Thu) by Wol (guest, #4433)In reply to: Yet another opportunity for opportunistic suspend by pabs Parent article: Yet another opportunity for opportunistic suspend
Equally, they would avoid trashed files ...
I had a load of audacity projects on my Linpus Aspire and did an mv to move them to my desktop.
With hindsight leaving the Aspire on the desk to finish copying was a major mistake - it kept suspending, breaking network links, and I ended up having to repeatedly wake it. What's worse, it didn't move stuff properly, and having started working on those projects on the desktop, I discovered a load of files had been trashed, leaving holes in the audio. Seeing as I'd done an mv, not a cp, recovery was not possible ... :-(
Suspending at the wrong time will trash your data ...
Cheers,
(Log in to post comments)
Yet another opportunity for opportunistic suspend Posted Oct 27, 2011 17:12 UTC (Thu) by intgr (subscriber, #39733) [Link]
> I had a load of audacity projects on my Linpus Aspire and did an mv to move them to my desktop.
This is a problem with opportunistic suspend. This is a bug in the protocol/file system you used to access the remote machine. A proper one would return the network error back to mv as an I/O error, and mv would abort without deleting the source file.
|
|||||||||||||