[MDEV-14810] mariabackup.xb_page_compress failed in buildbot with status: 1, errno: 11 Created: 2017-12-29  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Backup, Tests
Affects Version/s: 10.2
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Marko Mäkelä
Resolution: Cannot Reproduce Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-fedora25-amd64/builds/1518/steps/mtr/logs/stdio

mariabackup.xb_page_compress             w3 [ fail ]
        Test ended at 2017-12-27 21:36:29
 
CURRENT_TEST: mariabackup.xb_page_compress
mysqltest: At line 30: exec of '/usr/bin/mariabackup --defaults-file=/dev/shm/var/3/my.cnf  --backup "--tables=test.*1" --target-dir=/dev/shm/var/3/tmp/backup 2>&1' failed, error: 256, status: 1, errno: 11
Output from before failure:
171227 21:36:29 Connecting to MySQL server host: localhost, user: root, password: set, port: 16060, socket: /dev/shm/var/tmp/3/mysqld.1.sock
Using server version 10.2.12-MariaDB-log
/usr/bin/mariabackup based on MariaDB server 10.2.12-MariaDB Linux (x86_64) 
mariabackup: uses posix_fadvise().
mariabackup: cd to /dev/shm/var/3/mysqld.1/data/
mariabackup: open files limit requested 1024, set to 1024
mariabackup: using the following InnoDB configuration:
mariabackup:   innodb_data_home_dir = .
mariabackup:   innodb_data_file_path = ibdata1:12M:autoextend
mariabackup:   innodb_log_group_home_dir = ./
2017-12-27 21:36:29 140718904666304 [Note] InnoDB: Number of pools: 1
171227 21:36:29 >> log scanned up to (17592186504114)
2017-12-27 21:36:29 140718904666304 [Note] InnoDB: Log sequence number at the start 36266 and the end 459698 do not match
2017-12-27 21:36:29 140718904666304 [ERROR] InnoDB: Checksum mismatch in datafile: ./ibdata1, Space ID:0, Flags: 0. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
2017-12-27 21:36:29 140718904666304 [Note] InnoDB: Restoring page [page id: space=0, page number=0] of datafile './ibdata1' from the doublewrite buffer. Writing 16384 bytes into file './ibdata1'
2017-12-27 21:36:29 140718904666304 [Warning] InnoDB: Retry attempts for writing partial data failed.
2017-12-27 21:36:29 140718904666304 [ERROR] InnoDB: Write to file ./ibdata1failed at offset 0, 16384 bytes should have been written, only 0 were written. Operating system error number 9. Check that your OS and file system support files of this size. Check also that the disk is not full or a disk quota exceeded.
2017-12-27 21:36:29 140718904666304 [ERROR] InnoDB: Error number 9 means 'Bad file descriptor'
2017-12-27 21:36:29 140718904666304 [Note] InnoDB: Some operating system error numbers are described at http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
mariabackup: Could not open or create data files.
mariabackup: If you tried to add new data files, and it failed here,
mariabackup: you should now edit innodb_data_file_path in my.cnf back
mariabackup: to what it was, and remove the new ibdata files InnoDB created
mariabackup: in this failed attempt. InnoDB only wrote those files full of
mariabackup: zeros, but did not yet use them in any way. But be careful: do not
mariabackup: remove old data files which contain your precious data!
mariabackup: error: xb_load_tablespaces() failed witherror code 39
mariabackup: Stopping log copying thread.
.
 
 
 
The result from queries just before the failure was:
< snip >
INSERT INTO t1 VALUES(CURRENT_NUM,'TESTING..');
SET CURRENT_NUM = CURRENT_NUM + 1;
END WHILE;
END//
COMMIT;
SET AUTOCOMMIT=0;
CALL innodb_insert_proc(5000);
COMMIT;
SELECT (VARIABLE_VALUE >= 0) AS HAVE_COMPRESSED_PAGES
FROM INFORMATION_SCHEMA.GLOBAL_STATUS
WHERE VARIABLE_NAME = 'INNODB_NUM_PAGES_PAGE_COMPRESSED';
HAVE_COMPRESSED_PAGES
1
# xtrabackup backup
 
More results from queries before failure can be found in /dev/shm/var/3/log/xb_page_compress.log



 Comments   
Comment by Marko Mäkelä [ 2023-11-29 ]

In the cross-reference, I did not find any failure of this test that would include error 9 or Bad file descriptor. The latest failure (of any kind) of this test in a 10.x branch was:

10.3 0ddbec40fbba8ce818489c82a1b679a0b33aa50e

mariabackup.xb_page_compress             w1 [ fail ]
        Test ended at 2023-01-19 14:53:28
 
CURRENT_TEST: mariabackup.xb_page_compress
mysqltest: At line 41: query 'SELECT COUNT(*) FROM t1' failed: 1030: Got error 1877 "Unknown error 1877" from storage engine InnoDB
 
The result from queries just before the failure was:
< snip >
INSERT INTO t1 VALUES(CURRENT_NUM,'TESTING..');
SET CURRENT_NUM = CURRENT_NUM + 1;
END WHILE;
END//
COMMIT;
SET AUTOCOMMIT=0;
CALL innodb_insert_proc(5000);
COMMIT;
SELECT (VARIABLE_VALUE >= 0) AS HAVE_COMPRESSED_PAGES
FROM INFORMATION_SCHEMA.GLOBAL_STATUS
WHERE VARIABLE_NAME = 'INNODB_NUM_PAGES_PAGE_COMPRESSED';
HAVE_COMPRESSED_PAGES
1
# xtrabackup backup
# xtrabackup prepare
ALTER TABLE t1 DISCARD TABLESPACE;
ALTER TABLE t1 IMPORT TABLESPACE;
SELECT COUNT(*) FROM t1;
 
More results from queries before failure can be found in /buildbot/amd64-ubuntu-1804-valgrind/build/mysql-test/var/1/log/xb_page_compress.log
 
Warnings from just before the error:
Warning 1877 InnoDB: Table `test`.`t1` is corrupted.
 
 - skipping '/buildbot/amd64-ubuntu-1804-valgrind/build/mysql-test/var/1/log/mariabackup.xb_page_compress/'

There was one failure on 11.0, but I think that it is related to the Linux kernel bug MDEV-30728.

Generated at Thu Feb 08 08:16:27 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.