|
In general if you run the SD with the -p option (also bextract if
I am not mistaken), it will attempt to ignore block errors.
However, if the block contains data that Bacula must use for some
operation, it is very likely that Bacula will blow up at some
later time.
Best regards,
Kern
On 05/03/2018 02:01 PM, Heitor Faria
wrote:
Dear Bacula Users,
I'm working for a company that had all Windows data
ransomware corrupted.
I've got a faulty Backup Storage LVM with more than
135k multiply-claimed nodes according to fsck, resulting in
several restore job errors:
03-May 07:43 bacula-srv-sd JobId 244: Error:
block.c:318 Volume data error at 49:3137286592!
Block checksum mismatch in block=240712 len=64512:
calc=6483f882 blk=ec9fd28e
03-May 07:43 bacula-srv-sd JobId 244: Fatal error:
fd_cmds.c:169 Command error with FD, hanging up.
fsck repair results in fsck freeze or exaggerated
running time (probably several days).
I've already tried setting the BlockPositioning
directive = no, but still could not restore much data.
I tried to pinch some urgent files with bextract,
with the same results.
I don't remember if there is any special option to
deal with bad blocks. Is there?
Regards,
--
Heitor
Medrado de Faria | EB-1 Visa | LPIC-III
| ITIL-F | EMC 05-001
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
