Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-16456

InnoDB error "returned OS error 71" complains about wrong path

Details

    Description

      This simple 2-liner makes InnoDB produce the notorious "returned OS error 71" in the command line.

      --source include/have_innodb.inc
      		 
      CREATE TABLE t1 (a INT) ENGINE=InnoDB;
      		 
      --error ER_ERROR_ON_RENAME
      		 
      RENAME TABLE t1 TO non_existing_db.t1;
      		 
       
      		 
      # Cleanup
      		 
      DROP TABLE t1;

      The SQL error is of course expected, and the appearance of the accompanying InnoDB error might be considerated legitimate; the problem is what it says:

      10.0 c4499a0391

      		 
      2018-06-11 01:06:49 7fb9f297a700  InnoDB: Operating system error number 2 in a file operation.
      		 
      InnoDB: The error means the system cannot find the path specified.
      		 
      180611  1:06:49 [ERROR] InnoDB: File ./test/t1.ibd: 'rename' returned OS error 71.

      In the error message, it mentions the valid existing path ./test/t1.ibd, but doesn't mention the problematic non-existing path, and it reads like ./test/t1.ibd does not exist. It's very confusing when it comes to investigation, especially when it's a problem on the user side, when we don't have all the information, don't know which statement was issued and what caused the error.

      Attachments

        Activity

          marko Marko Mäkelä added a comment -

          The problem is that InnoDB is only reporting one file name with the error message:

          	ret = rename(oldpath, newpath);
          		 
           
          		 
          	if (ret != 0) {
          		 
          		os_file_handle_error_no_exit(oldpath, "rename", FALSE);
          		 
           
          		 
          		return(FALSE);
          		 
          	}

          Fixing this requires rewriting all the error reporting code, or maybe as a lesser evil, duplicating the logic of os_file_handle_error_no_exit() for rename, reporting both file names.

          marko Marko Mäkelä added a comment - The problem is that InnoDB is only reporting one file name with the error message: ret = rename (oldpath, newpath);   if (ret != 0) { os_file_handle_error_no_exit(oldpath, "rename" , FALSE);   return (FALSE); } Fixing this requires rewriting all the error reporting code, or maybe as a lesser evil, duplicating the logic of os_file_handle_error_no_exit() for rename, reporting both file names.

          People

            marko Marko Mäkelä
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.