Hi Antonio, To help avoid any misunderstandings and reduce the chance of disaster,
any critical requirements for the operation of the program ; 1) could be mentioned, referred to, or covered at the front/top of the manual. 2) could be mentioned within the program. (e.g. generate logfile by default, using name of image with suffix name.log, check that input source is not mounted as rw, ask user if the disk has been reporting IO errors before actually doing any extraction operation, if destination is a drive or partition then warn the user before doing any extraction operation.) These include (from manual http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html ) IMPORTANT! Always use a logfile unless you know you won't need it. Without a logfile, ddrescue can't resume a rescue, only reinitiate it. IMPORTANT! Never try to rescue a r/w mounted partition. The resulting copy may be useless. IMPORTANT! If you use a device or a partition as destination, any data stored there will be overwritten. IMPORTANT! If you interrupt the rescue and then reboot, any partially copied partitions should be hidden before allowing them to be touched by any operating system that tries to mount and "fix" the partitions it sees. IMPORTANT! Never try to repair a file system on a drive with I/O errors; you will probably lose even more data. ie "file system on a drive" do not repair it "ON" the drive. - but can it be extracted/copied/imaged/ddrescued to a file then repair the file? Yours Al _______________________________________________ Bug-ddrescue mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-ddrescue
