[Bug-ddrescue] Image File Size

[wilborville]

Thanks in Advance for any help in this mystery.

Needless to say, new at all this. Gddrescue is pretty cool but I am still
trying to understand both
Ubuntu Linux and Gddrescue. I am worried about running out of hard disk
space used to output the image file "Jim", 
to drive name "160G" (which is the approximate drive size too), /dev/sdb.

I desired to rescue a segment on a bad USB external 320G drive, between 70G
and 100G in 10G increments.
Actually 11G so there's some overlap? Will use data carving tool like
Photorec to analyze each segment.

I already "rescued" sudo ddrescue -vd -i70G -s11G /dev/sdc2 /media/160G/Jim
/media/160G/logfile

The size of Jim (~ 74G) spooked me. I know why now, -s11G is size of input
to be copied. 
Output file I understand starts around zero. So, yes the output file can be
large. Ooops.

If the next two 11G segments are this large or larger, I'd run out of drive
space. 
I decided that I'd ADD the next two 11G segments to Jim to using the same
logfile. 

Using same logfile...

I have asked to CONTINUE rescuing a segment 11G in size from position 80G to
91G
sudo ddrescue -vd -i80G -s11G /dev/sdc2 /media/160G/Jim /media/160G/logfile

Why -d "direct"? It seems to work longer between "input file disappeared"
messages than without. 
Painfully slow but it keeps chugging away. 

Snapshot now fyi:
About to copy 11 GBytes from /dev/sdc2 to /media/160G/Jim
    Starting positions: infile = 80 GB,  outfile = 80 GB
    Copy block size: 128 hard blocks
Hard block size: 512  bytes
Max_retries: 0    
Direct: yes    Sparse: no    Split: yes    Truncate: no

Press Ctrl-C to interrupt
Initial status (read from logfile)
rescued:   432723 kB,  errsize:  10567 MB,  errors:      16
Current status
rescued:   432723 kB,  errsize:  10567 MB,  current rate:        0 B/s
   ipos:    81062 MB,   errors:      16,    average rate:        0 B/s
   opos:    81062 MB,     time from last successful read:    25.4 m
Splitting failed blocks.

Here's the problem. If I look in the File Browser, double click "160G", in
Ubuntu (latest version), it shows
Jim 75.9G in size and growing. logfile is 26kB. Another 1.5 G from two other
unrelated files, 4 files visible
in totaling 77.2G   Keep this number in mind. Even showing "hidden files"
using this NFS+ (journaling OFF)
drive only shows a few kB more.

But if  Right Click "160G" drive and read Properties, it shows 142.7 GB used
and 9.7GB free!!! 
Same general results if   df /dev/sdb2 or 94% used. 

How can this be?  77.2G or 142.7G? 

Thanks
wilborville (Jim)

P.S. I found in this forum a better way would have been to use this to
start. Correct?
sudo ddrescue -vd -i70G -o0 -s11G /dev/sdc2 /media/160G/Jim
/media/160G/logfile

-- 
View this message in context: 
http://old.nabble.com/Image-File-Size-tp26931720p26931720.html
Sent from the Gnu - ddrescue mailing list archive at Nabble.com.