|From:||Antonio Diaz Diaz|
|Subject:||Re: [Bug-ddrescue] Suggestion for ddrescue in _seriously hosed filesystem_ environment|
|Date:||Thu, 30 Apr 2015 19:16:29 +0200|
|User-agent:||Mozilla/5.0 (X11; U; Linux i586; en-US; rv:188.8.131.52) Gecko/20070601 SeaMonkey/1.1.2|
Nathan Neulinger wrote:
I managed to finally get it to read without crashing by adding the -d direct option, so my suggestion may not strictly be necessary.
I hope so. See below.
It just seemed to me that the 'I'm trying block X' information is lost if the process is uncleanly terminated _while_ trying that block, and seems like there should be something that is recording reads in progress with a fsync of that temporary log while it's running.
The main problem with your suggestion is that on the good parts of the file the logfile can be written and synced hundreds of times per second, instead of once every 30 seconds. If someone activates the option by mistake, it can easily melt the drive where the logfile is written.
If '-d' had not worked, cloning the HDDs individually could have been the best solution.
Best regards, Antonio.
|[Prev in Thread]||Current Thread||[Next in Thread]|