Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=2499152
By: nobody
Szaka,
1) Network traffic does not seem to affect this.
2) I did
smbmount with lfs option
ntfsclone -o /mnt/l/test.img /dev/hda1
I see a 25 second delay at 0.65% complete. Then I see another delay at 7.40%
complete, and after 30 seconds it fails. During these two delays, the hard drive
light at the remote (destination) PC is continuously on (a detail I hadn't noticed
before!).
3) The same thing happens when the output file is on either of two different
shares on the remote PC, which happen to be on two different physical drives.
So, although I have not defragged the remote PC, the fact that I get delays
at the same place on two different drives leads me to believe it's not related
to fragmentation on the remote.
4) Same test as test (2), plus on the remote PC, I also perform a copy of a
large (2GB) file from one drive to the other. This produces a lot of interferring
I/O requests on the remote PC.
In this case, I get a 30 second delay and failure at the 0.65% completion
point.
5) If I delete the pagefile.sys on the local PC, and then repeat, I get a delay
at 0.86% complete, 30 seconds delay and then failure. So while again I have
not defragged the local PC, the problem does seem to be related to file layout
on the local PC.
My guess interpretation of this is that when ntfsclone performs a "go to position"
operation that is a large skip, the ntfs driver on the remote PC must physically
write zeros to all those skipped blocks. If this operation takes longer than
30 seconds, something (probalby in smbfs) times out.
It's not clear to me that this can be easily fixed. You probably don't want
to increase the time-out limit, because 30 seconds is alreay a very long timeout
for normal operations. Perhaps ntfsclone could make its jumps in smaller chunks,
waiting for ackowledgement.
Hope this helps,
Trey
______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/unmonitor.php?forum_id=44085
|