| Bug #96224 | The MTR case innodb.innodb_corrupt_bit get a randomly coredump | ||
|---|---|---|---|
| Submitted: | 17 Jul 2019 3:12 | Modified: | 21 Oct 2019 12:21 |
| Reporter: | shangshang yu | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
| Version: | 8.0.16 | OS: | CentOS |
| Assigned to: | CPU Architecture: | x86 | |
| Tags: | core dump, mtr | ||
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
[18 Jul 2019 9:31]
Umesh Shastry
[16 Jun 2022 3:01]
chengqing hu
./mtr my1 result
Attachment: my1.result (application/octet-stream, text), 6.90 KiB.
