-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
br restore encrypted backup failed "Bad table magic number #32423
Comments
The error log of this bug is similar to previously fixed bug: #30225 |
|
It failed again during the daily CI today, refer to https://tcms.pingcap.net/dashboard/executions/plan/633883 |
Can we download the SST file |
@YuJuncen please get it from http://172.16.5.66:9000/tmp/fubin/17884e0d-7863-4f36-8119-f45ab83385ca_308_5_78_default.sst?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=IGJERMI9YK8YO1SPZD3B%2F20220221%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220221T013211Z&X-Amz-Expires=604799&X-Amz-Security-Token=eyJhbGciOiJIUzUxMiIsInR5cCI6IkpXVCJ9.eyJhY2Nlc3NLZXkiOiJJR0pFUk1JOVlLOFlPMVNQWkQzQiIsImV4cCI6MTY0NTQxMDcwNywicG9saWN5IjoiY29uc29sZUFkbWluIn0.ehj94OZNZpFvmXJsQ2MCJfCKSEs8mEvW7jH2jX305K_EhozPWaz5T-kCOEoKF1jzgqHYTYVtgDFMb_iF2Kxr2A&X-Amz-SignedHeaders=host&versionId=null&X-Amz-Signature=511ba8fe2ac03e40b6253b6c512926cb192fc8f708af9d10d9e3b011ec14db67 / # /br restore db "-s" "s3://tmp/br-backup-basica744c193-d3d1-4f4a-8f31-dc07172963a1?access-key=minioadmin&secret-access-key=minioadmin&endpoint=http%3a%2f%2fminio.pingcap.net%3a9000&force-path-style=true" "-u" "http:// |
3 of 5 recent daily CI since 2022/02/17 failed for this case (please refer to https://tcms.pingcap.net/dashboard/executions/plan?query=brie-acceptance%40main&page=1&pageSize=20) , please triage it with high priority, thanks. |
I've checked those files, and found out that:
{
"sha256": "0a409a13ff6d3b4d494b176e09563cf7827e137598db58a6c08097100db43ed8",
"start_key": "7480000000000002ee5f72fa00000000567b49",
"end_key": "7480000000000002ee5f72fc0000000052935d",
"name": "1_4444_469_698ec964e67db64231a7ef85ed6f26c4a7ae18101004ff243765a5e9445af12d_1645037214310_default.sst",
"end_version": 431236630631415800,
"crc64xor": 2619387936646232000,
"total_kvs": 139709,
"total_bytes": 44761977,
"cf": "default",
"size": 17236528,
"cipher_iv": "Ynuhu60Tafw0q9q5otBa7g=="
}
I guess the file should already be incorrect when we backing up. 🤔 |
close it, the issue is fixed in master. |
…rror for downloadSST (pingcap#32847) (pingcap#33197) close pingcap#32423
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
Run br backup and restore, specifying encryption parameters as below
2. What did you expect to see? (Required)
Restore can be successful.
3. What did you see instead (Required)
restore failed, error: "Engine Engine("Corruption: Bad table magic number: expected 9863518390377041911, found 7952868509031340309 in /var/lib/tikv/data/import/.temp/b10f671b-0aa3-4914-938b-6f2c021605d0_20460_5_3231_default.sst"
4. What is your TiDB version? (Required)
/ # /br -V
Release Version: v5.5.0-nightly
Git Commit Hash: 9659b93
Git Branch: heads/refs/tags/v5.5.0-nightly
Go Version: go1.16.4
UTC Build Time: 2022-02-16 06:07:49
Race Enabled: false
The text was updated successfully, but these errors were encountered: