[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2236: Skip files with errors, Long files name, too large. Instead of failing the entire process

[Tahoe-LAFS]

#2236: Skip files with errors, Long files name, too large. Instead of failing the
entire process
-----------------------------------+------------------------------------
     Reporter:  CyberAxe           |      Owner:  daira
         Type:  defect             |     Status:  new
     Priority:  normal             |  Milestone:  eventually
    Component:  code-frontend-cli  |    Version:  1.10.0
   Resolution:                     |   Keywords:  tahoe-backup error cli
Launchpad Bug:                     |
-----------------------------------+------------------------------------
Changes (by daira):

 * keywords:   => tahoe-backup error cli
 * component:  unknown => code-frontend-cli
 * milestone:  undecided => eventually


Old description:

> Skip Errors and cont.
>
> When a long file name, large file, or other error or validation issue
> happens the entire process of backup or restore is ended and you must
> start over. This takes a massive amount of time. If you are backing up or
> restoring GB of data this could cause many hours or days of reprocessing.
> As well to test a solution to the fix you must start the entire process
> over.
> Please log the errors and skipped files but cont the process. An optional
> prompt would be helpful to allow the Large file name to be renamed or
> skipped.
> At the end of the process all skipped or errors should be reported.
>

> (1:51:54 PM) CyberAxe: I really need backup/restore to not fail when it
> runs into a problem with a file but log it and skip. I've been having a
> problem with long file names on restore and it kills the entire process
> at any error instead of skipping the problem file and moving on.
> (1:53:49 PM) zooko: CyberAxe: hm
> (1:53:53 PM) CyberAxe: This should apply to almost any action. A Try
> statement vs instead of crash. With 25GB of data to recover going up to
> 350GB I really don't want to have to monitor the restore/backup for 20+
> hours just incase it fails.
> (1:53:56 PM) zooko: CyberAxe: I saw the issue ticket about the long file
> names.
> (1:54:29 PM) zooko: CyberAxe: okay, I don't believe that there is
> currently an issue ticket about continuing past an error. Would you
> please open one that says what you just said right there?
>
> Skip, Cont

New description:

 Skip Errors and cont.

 When a long file name, large file, or other error or validation issue
 happens the entire process of backup or restore is ended and you must
 start over. This takes a massive amount of time. If you are backing up or
 restoring GB of data this could cause many hours or days of reprocessing.
 As well to test a solution to the fix you must start the entire process
 over.
 Please log the errors and skipped files but cont the process. An optional
 prompt would be helpful to allow the Large file name to be renamed or
 skipped.
 At the end of the process all skipped or errors should be reported.


 (1:51:54 PM) !CyberAxe: I really need backup/restore to not fail when it
 runs into a problem with a file but log it and skip. I've been having a
 problem with long file names on restore and it kills the entire process at
 any error instead of skipping the problem file and moving on.
 (1:53:49 PM) zooko: !CyberAxe: hm
 (1:53:53 PM) !CyberAxe: This should apply to almost any action. A Try
 statement vs instead of crash. With 25GB of data to recover going up to
 350GB I really don't want to have to monitor the restore/backup for 20+
 hours just incase it fails.
 (1:53:56 PM) zooko: !CyberAxe: I saw the issue ticket about the long file
 names.
 (1:54:29 PM) zooko: !CyberAxe: okay, I don't believe that there is
 currently an issue ticket about continuing past an error. Would you please
 open one that says what you just said right there?

 Skip, Cont

--

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2236#comment:2>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage