Re: [Bug-ddrescue] Option to stop copy at first error

[Narcis Garcia]

--max-errors didn't work as expected with ddrescue 1.17

This is my command:
$ ddrescue --force -n -e +1 /dev/sdb /dev/sdc /var/tmp/ddrescue-map.log

This is the output when running repeatedly:
(why errsize 35563TB on a 1TB disk ???)


GNU ddrescue 1.17
Press Ctrl-C to interrupt
rescued:    34992 MB,  errsize:   90112 B,  current rate:        0 B/s
   ipos:    34992 MB,   errors:       2,    average rate:   77245 kB/s
   opos:    34992 MB,    time since last successful read:       1 s
Copying non-tried blocks...
Too many errors in input file


GNU ddrescue 1.17
Press Ctrl-C to interrupt
Initial status (read from logfile)
rescued:    34992 MB,  errsize:   90112 B,  errors:       2
Current status
rescued:    34999 MB,  errsize:    118 kB,  current rate:        0 B/s
   ipos:    34999 MB,   errors:       4,    average rate:     271 kB/s
   opos:    34999 MB,    time since last successful read:       1 s
Copying non-tried blocks...
Too many errors in input file


GNU ddrescue 1.17
Press Ctrl-C to interrupt
Initial status (read from logfile)
rescued:    34999 MB,  errsize:    118 kB,  errors:       4
Current status
rescued:    35009 MB,  errsize:    221 kB,  current rate:        0 B/s
   ipos:    35009 MB,   errors:       6,    average rate:     357 kB/s
   opos:    35009 MB,    time since last successful read:       1 s
Copying non-tried blocks...
Too many errors in input file


GNU ddrescue 1.17
Press Ctrl-C to interrupt
Initial status (read from logfile)
rescued:    35009 MB,  errsize:    221 kB,  errors:       6
Current status
rescued:    97277 MB,  errsize:    299 kB,  current rate:        0 B/s
   ipos:    97277 MB,   errors:       8,    average rate:   50135 kB/s
   opos:    97277 MB,    time since last successful read:       1 s
Copying non-tried blocks...
Too many errors in input file


GNU ddrescue 1.17
Press Ctrl-C to interrupt
Initial status (read from logfile)
rescued:    97277 MB,  errsize:    299 kB,  errors:       8
Current status
rescued:    97277 MB,  errsize:  35563 TB,  current rate:        0 B/s
   ipos:    35563 TB,   errors:       8,    average rate:        0 B/s
   opos:    35563 TB,    time since last successful read:     1.1 m
Copying non-tried blocks...terminate called after throwing an instance
of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted


GNU ddrescue 1.17
Press Ctrl-C to interrupt
Initial status (read from logfile)
rescued:    97277 MB,  errsize:    299 kB,  errors:       8
Current status
rescued:    97277 MB,  errsize:  35780 TB,  current rate:        0 B/s
   ipos:    35780 TB,   errors:       8,    average rate:        0 B/s
   opos:    35780 TB,    time since last successful read:       1 m
Copying non-tried blocks...terminate called after throwing an instance
of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted


GNU ddrescue 1.17
Press Ctrl-C to interrupt
Initial status (read from logfile)
rescued:    97277 MB,  errsize:    299 kB,  errors:       8
Current status
rescued:    97277 MB,  errsize:  35789 TB,  current rate:        0 B/s
   ipos:    35789 TB,   errors:       8,    average rate:        0 B/s
   opos:    35789 TB,    time since last successful read:       1 m
Copying non-tried blocks...terminate called after throwing an instance
of 'std::bad_alloc'
  what():  std::bad_alloc
Aborted


GNU ddrescue 1.17
Press Ctrl-C to interrupt
Initial status (read from logfile)
rescued:    97277 MB,  errsize:    299 kB,  errors:       8
Current status
rescued:    97277 MB,  errsize:   2355 TB,  current rate:        0 B/s
   ipos:     2355 TB,   errors:       8,    average rate:        0 B/s
   opos:     2355 TB,    time since last successful read:       5 s
Copying non-tried blocks...^C
Interrupted by user
^C



On 03/02/16 12:50, Paul Daniels wrote:
> 
> There's the -X or --max-errors options that should fit your needs
> perhaps ? (ie, --max-errors=+1 )
> 
> On 03/02/16 19:15, Narcis Garcia wrote:
>> I've read the letter entitled "Dealing with a disk that stops
>> responding" from Olaf Buddenhagen, and I have same situation with a
>> S.ATA disk: rest of blocks are annotated as
>>
>> My feature request is to add an option to stop ddrescue action when a
>> new read error is found, having the opportunity of shutting down
>> computer and continue copy in a new session.
>>
>> $ ddrescue -n -N /dev/sda /dev/sdb map.log
>>
>> In the meanwhile, may be some alternative to cut mapfile properly?
>>
>>
>> _______________________________________________
>> Bug-ddrescue mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/bug-ddrescue
>>
>