bug-ddrescue
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-ddrescue] Not really a bug about timestamp, but rather a suggestion


From: Rikard Bosnjakovic
Subject: [Bug-ddrescue] Not really a bug about timestamp, but rather a suggestion
Date: Mon, 09 Nov 2015 23:47:17 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32

I recently upgraded from ddrescue 1.16 to 1.20 and noticed that there are two timestamps (start / current) in the logfile. This is good info.

However, I have a suggestion for this. As for now, the start time seems to be changed everytime ddrescue is invoked for the particular logfile. This has shown to be a bit pointless for some of the drives I've run ddrescue on, which I have to kill ddrescue and reset the drive to be able to continue (somehow the kernel just dropped it and reset was the only way out). But resetting the drive and program also resets the start time, which is a bit weird.

My suggestion is this: only write the start time once, when the logfile is created. Concurrent runs only updates the current time, as it does now. Perhaps adding another field: "Number of runs", or similar?

This is an except for a very damaged drive I worked with last week, and had to reset the drive for atleast 40 times before finally being able to work on the rescued image:

# Start time:   2015-11-02 09:11:28
# Current time: 2015-11-02 09:12:00

That info is surely hiding what actually happened :-)


Just my two cents.

BR,
Rikard



reply via email to

[Prev in Thread] Current Thread [Next in Thread]