Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.1.6
-
None
Description
MariaDB [test]> show binary logs;
|
+------------------+-----------+
|
| Log_name | File_size |
|
+------------------+-----------+
|
| mysql-bin.000001 | 312 |
|
+------------------+-----------+
|
1 row in set (0.00 sec)
|
|
MariaDB [test]> reset master to 2147483647;
|
Query OK, 0 rows affected (0.36 sec)
|
|
MariaDB [test]> show binary logs;
|
+----------------------+-----------+
|
| Log_name | File_size |
|
+----------------------+-----------+
|
| mysql-bin.2147483647 | 316 |
|
+----------------------+-----------+
|
1 row in set (0.00 sec)
|
|
# So far, so good...
|
MariaDB [test]> reset master to 2147483648;
|
ERROR 1098 (HY000): Can't generate a unique log-filename mysql-bin.(1-999)
|
|
MariaDB [test]> show binary logs;
|
Empty set (0.00 sec)
|
|
MariaDB [test]> reset master to 1;
|
ERROR 1373 (HY000): Target log not found in binlog index
|
MariaDB [test]> reset master;
|
ERROR 1373 (HY000): Target log not found in binlog index
|
MariaDB [test]> create table t1 (i int);
|
ERROR 3 (HY000): Error writing file 'UNOPENED' (Errcode: 9 "Bad file descriptor")
|
Attachments
Issue Links
- relates to
-
MDEV-34486 Server crashes when binlog_space_limit is set to 1 after setting the binary log larger than the max limit
- Open
-
MDEV-8469 Add RESET MASTER TO x to allow specification of binlog file nr
- Closed