pub enum ErrorKind {
TransientFileNotAvailable,
PermanentFileNotAvailable,
PermanentDirectoryNotAvailable,
PermanentDirectoryNotEmpty,
PermissionDenied,
ConnectionClosed,
LocalError,
PageTypeUnknown,
InsufficientStorageSpaceError,
ExceededStorageAllocationError,
FileNameNotAllowedError,
CommandNotImplemented,
}Expand description
The ErrorKind variants that can be produced by the StorageBackend implementations.
Variants§
TransientFileNotAvailable
Error that will cause an FTP reply code of 450 to be returned to the FTP client. The storage back-end implementation should return this if a error occurred that my be retried for example in the case where a file is busy.
PermanentFileNotAvailable
Error that will cause an FTP reply code of 550 to be returned to the FTP client. The storage back-end implementation should return this if a error occurred where it doesn’t make sense for it to be retried. For example in the case where a file is busy.
PermanentDirectoryNotAvailable
Error that will cause an FTP reply code of 550 to be returned to the FTP client. The storage back-end implementation should return this if a error occurred where it doesn’t make sense for it to be retried. For example in the case where the directory doesn’t exist
PermanentDirectoryNotEmpty
Error that will cause an FTP reply code of 550 to be returned to the FTP client. The storage back-end implementation should return this if a error occurred where it doesn’t make sense for it to be retried. For example in the case where file access is denied.
PermissionDenied
Error that will cause an FTP reply code of 550 to be returned to the FTP client. The storage back-end implementation should return this if a error occurred where it doesn’t make sense for it to be retried. For example in the case where file access is denied.
ConnectionClosed
Error that will cause an FTP reply code of 426 to be returned to the FTP client. It means the transfer was aborted, possibly by the client or because of a network issue
LocalError
Error that will cause an FTP reply code of 451 to be returned to the FTP client. It means the requested action was aborted due to a local error (internal storage back-end error) in processing.
PageTypeUnknown
551 Requested action aborted. Page type unknown.
InsufficientStorageSpaceError
452 Requested action not taken. Insufficient storage space in system.
ExceededStorageAllocationError
552 Requested file action aborted. Exceeded storage allocation (for current directory or dataset).
FileNameNotAllowedError
Error that will cause an FTP reply code of 553 to be returned to the FTP client. Its means the requested action was not taken due to an illegal file name.
CommandNotImplemented
Error that will cause an FTP reply code of 502. The indicates to the client that the command is not implemented for the storage back-end. For instance the GCS back-end don’t implement RMD (remove directory) but returns this error instead from its StorageBackend::rmd implementation.