[Top][All Lists]

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

Re: [Bug-ddrescue] Slowing down of ddrescue over time

From: bidib
Subject: Re: [Bug-ddrescue] Slowing down of ddrescue over time
Date: Wed, 26 Oct 2011 07:24:05 -0700 (PDT)

First of all, thanks a lot to Antonio for this wonderful tool. I would be
glad to show my gratitude : do you have an amazon wishlist or so ? Your work
has helped me a lot for my personal use, and now helps me feeding my family

I am experiencing the same problem here.
Recovery slows down rapidly by a factor of 10x or so, it can't be caused
only by the physical structure of the disk (throughput faster at the
beginning of the disk), which can't exceed 50%.

> Some users have already reported this when writing to an ntfs partition. 
> It seems to be a problem with the ntfs-3g driver or format. See for 
> example the following message:
> "NTFS-3g eating 100%. Solved by switching to ext3"
> https://lists.gnu.org/archive/html/bug-ddrescue/2009-06/msg00004.html

source : 120 gb HFS (mac) partition on a 120gb IDE hdd
target : fresh new 200 gb EXT4 partition on a 200gb IDE hdd
the log is stored on a NTFS partition, on a third IDE hdd. 

the system is a shuttle barebone, booted with hiren's bootdisk mini linux
(slackware). BTW this bootdisk is a jewel.

I hesitated on writing the log elsewhere : 
- on the target ext4 partition (is it possible on the same partition ?
should i create another one ?)
- on the virtual ramdrive my bootdisk created, but i was afraid it would not
be large enough and would be lost if the recovery crashed or the computer

that's why i put it on an NTFS partition i had in that wind0ws desktop.

I am currently recovering a 120 gb partition, it has only completed 50 gb in
30 hours. I am hesitating on stopping the process, moving the logfile (where
??) and resuming it. Afraid of losing everything !
View this message in context: 
Sent from the Gnu - ddrescue mailing list archive at Nabble.com.

reply via email to

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