| Bug #98530 | crash when inplace encryption resumes makes tablespace unusable | ||
|---|---|---|---|
| Submitted: | 10 Feb 2020 9:27 | Modified: | 17 Sep 2020 16:25 |
| Reporter: | Satya Bodapati (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S2 (Serious) |
| Version: | 8.0, 8.0.19 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix> - On windows use WinZip or a similar utility to split the large file
[10 Feb 2020 9:28]
Satya Bodapati
[10 Feb 2020 9:28]
Satya Bodapati
mtr testcase
Attachment: tablespace_encrypt_2_crash.test (application/octet-stream, text), 3.48 KiB.
[10 Feb 2020 9:29]
Satya Bodapati
debug crash point change
Attachment: 98530_code_change.diff (text/x-patch), 539 bytes.
