Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL)
Description
This came up while I was preparing to test MDEV-14795 with something like the following:
mkdir /dev/shm/data
|
./mariadbd --datadir /dev/shm/data --innodb-data-file-path=ibdata1:56G --bootstrap < /dev/null
|
The startup message would wrongly claim the following:
10.9 35de8326fb6ca2751c83ee7465c33347b9efeb93 |
2023-07-05 13:39:58 0 [Note] InnoDB: Setting file './ibdata1' size to 0.000GiB. Physically writing the file full; Please wait ...
|
2023-07-05 13:40:19 0 [Note] InnoDB: File './ibdata1' size is now 0.000GiB.
|
This happens because of 32-bit arithmetics in SysTablespace::set_size(). All other messages that use the MDEV-27158 ib::bytes_iec seem to be correct.
Attachments
Issue Links
- is duplicated by
-
MDEV-31627 innodb large file size are have overflowed "size to 0.000B" message in logs
-
- Closed
-
- relates to
-
MDEV-27158 Humanize the number of bytes in InnoDB messages
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
issue.field.resolutiondate | 2023-07-05 11:52:19.0 | 2023-07-05 11:52:19.618 |
Fix Version/s | 10.9.8 [ 29015 ] | |
Fix Version/s | 10.10.6 [ 29017 ] | |
Fix Version/s | 10.11.5 [ 29019 ] | |
Fix Version/s | 11.0.3 [ 28920 ] | |
Fix Version/s | 11.1.2 [ 28921 ] | |
Fix Version/s | 11.2.1 [ 29034 ] | |
Fix Version/s | 10.9 [ 26905 ] | |
Fix Version/s | 10.10 [ 27530 ] | |
Fix Version/s | 10.11 [ 27614 ] | |
Fix Version/s | 11.0 [ 28320 ] | |
Fix Version/s | 11.1 [ 28549 ] | |
Fix Version/s | 11.2 [ 28603 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Link |
This issue is duplicated by |