quentin
/
seafile_recovery
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Improve README

This commit is contained in:
Quentin 2021-04-28 15:06:20 +02:00
parent 0b4b735e46
commit 81bf5405e7
Signed by: quentin
GPG Key ID: A98E9B769E4FF428
1 changed files with 62 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

64
README.md
View File

@ -1,13 +1,38 @@
# seafile_recovery
**Quick description:** `seafile_recovery` is a low-level tool that parses Seafile's on-disk file storage.
Compared to other tools, it works without the associated sqlite or MySQL database.
**Some use cases:** I developped this tool because I lost my database and wanted to get back my files.
It can also help you to diagnose problems with Seafile's on-disk file storage and maybe repair them.
Finally, it can help you better understand how Seafile is working internally and gather some statistics about your Seafile's repositories health.
**Features and limitation:** The tool can parse all commits of a repository, currently the `head` subcommand selects the "last" one according to the commit graph and an heuristic based on time. Each commit contains a `RootId`. All files and folders have an Id in Seafile, the `RootId` is simply the Id of the root folder of the repository at the time of the commit. You can inspect these Ids with `ls`. You can copy a file or a folder hierarchy on your disk with `cp`. Finally the `s3` subcommand directly transfer the file or folder hierarchy to a S3-compatible storage. Currently, the tool does not work with encrypted repositories. Advanced Seafile features are not tested. Finally, the tool has not been extensively tested and may crash when encountering some unusual edge cases.
**Disclaimer:** This tool is community made and thus not affiliated to Seafile Ltd., Seafile Gmbh. or any company.
The development of this tool has been done for my own needs, I can not be held responsible for any issue or damage it can cause.
Use it carefully or none at all if you are not sure of what you are doing, data are often more precious than we imagine.
Always shutdown your Seafile daemons before using it (both Seafile and Seahub).
Create a backup before running any command and double check all your operations.
## Installation
```
go get git.deuxfleurs.fr/quentin/seafile_recovery
~/go/bin/seafile_recovery --help
```
## Usage
```
Seafile Recovery.
Usage:
seafile_recovery [--storage=<sto>] head <repoid>
seafile_recovery [--storage=<sto>] ls <repoid> (--dir=<dirid> | --file=<fileid>)
seafile_recovery [--storage=<sto>] cp <repoid> (--dir=<dirid> | --file=<fileid>)
seafile_recovery [--storage=<sto>] s3 <repoid> (--dir=<dirid> | --file=<pathid>) <s3url>
seafile_recovery [--storage=<sto>] cp <repoid> (--dir=<dirid> | --file=<fileid>) <dest>
seafile_recovery [--storage=<sto>] s3 <repoid> (--dir=<dirid> | --file=<pathid>) <dest>
seafile_recovery s3del <dest>
seafile_recovery (-h | --help)
Options:
@ -17,6 +42,41 @@ Options:
--file=<fileid> Seafile File ID, can be obtained through ls
```
## Seafile on-disk storage
```
storage/commits/(repoid) storage/fs/(repoid) storage/blocks/(repoid)
(plain text json) (json + zlib) (chunk of raw data)
Dir (1) ┌──────────┐
HEAD ┌──────────┐ root_id ┌──────────┐ ┌─────►│5b/4c09c..│
(sink)│4f/2fcf9..├───────────────────►│98/ff6e3..│ │ └──────────┘
└─┬─────┬──┘ └─┬──────┬─┘ │
parent │ │ 2nd parent │ │DirEnt │ (2) ┌──────────┐
▼ ▼ │ │ ├─────►│eb/a557a..│
┌──────────┐ ┌──────────┐ Dir ▼ ▼ File │ └──────────┘
│21/22f45..├──┤a5/c7325..├───? ┌──────────┐ ┌──────────┐ │
└────────┬─┘ └─┬────────┘ │9f/31be6..│ │3b/2e671..├──┤ (3) ┌──────────┐
parent │ │ parent └─────┬──┬─┘ └──────────┘ └─────►│42/1aac0..│
▼ ▼ │ │DirEnt └──────────┘
┌──────────┐ │ └──────┐
│5b/2f24f..├──────────? File ▼ ▼ File (1) ┌──────────┐
└────┬─────┘ ┌──────────┐ ┌──────────┐ ┌──────►│0b/5c780..│
│ parent │4a/54b55..│ │ba/557ae..├─┘ └──────────┘
▼ └───────┬──┘ └──────────┘
┌──────────┐ │ (1) ┌──────────┐
Initial│69/ca6b5..├──────────? └─────────────────────────►│67/515ea..│
└────┬─────┘ (? = not shown) └──────────┘
│
X no parent
```
## Tutorial
----
## Dev notes
Should look how Seafile handles ID collision, it might be one here in a repo with `44592` commits: