Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
MariaDB
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
nexedi
MariaDB
Commits
d1d61d9a
Commit
d1d61d9a
authored
Jun 02, 2004
by
unknown
Browse files
Options
Browse Files
Download
Plain Diff
Merge tulin@bk-internal.mysql.com:/home/bk/mysql-4.1
into mc05.(none):/space2/tomas/mysql-4.1-ndb-test
parents
0ab38c8c
4de5ecdc
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
45 additions
and
4 deletions
+45
-4
innobase/fil/fil0fil.c
innobase/fil/fil0fil.c
+45
-4
No files found.
innobase/fil/fil0fil.c
View file @
d1d61d9a
...
...
@@ -2572,13 +2572,32 @@ fil_load_single_table_tablespace(
fprintf
(
stderr
,
"InnoDB: Error: could not open single-table tablespace file
\n
"
"InnoDB: %s!
\n
"
,
filepath
);
"InnoDB: %s!
\n
"
"InnoDB: We do no continue crash recovery, because the table will become
\n
"
"InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
\n
"
"InnoDB: To fix the problem and start mysqld:
\n
"
"InnoDB: 1) If there is a permission problem in the file and mysqld cannot
\n
"
"InnoDB: open the file, you should modify the permissions.
\n
"
"InnoDB: 2) If the table is not needed, or you can restore it from a backup,
\n
"
"InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
\n
"
"InnoDB: crash recovery and ignore that table.
\n
"
"InnoDB: 3) If the file system or the disk is broken, and you cannot remove
\n
"
"InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
\n
"
"InnoDB: and force InnoDB to continue crash recovery here.
\n
"
,
filepath
);
ut_free
(
filepath
);
if
(
srv_force_recovery
>
0
)
{
fprintf
(
stderr
,
"InnoDB: innodb_force_recovery was set to %lu. Continuing crash recovery
\n
"
"InnoDB: even though we cannot access the .ibd file of this table.
\n
"
,
srv_force_recovery
);
return
;
}
exit
(
1
);
}
success
=
os_file_get_size
(
file
,
&
size_low
,
&
size_high
);
if
(
!
success
)
{
...
...
@@ -2587,14 +2606,36 @@ fil_load_single_table_tablespace(
fprintf
(
stderr
,
"InnoDB: Error: could not measure the size of single-table tablespace file
\n
"
"InnoDB: %s!
\n
"
,
filepath
);
"InnoDB: %s!
\n
"
"InnoDB: We do no continue crash recovery, because the table will become
\n
"
"InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
\n
"
"InnoDB: To fix the problem and start mysqld:
\n
"
"InnoDB: 1) If there is a permission problem in the file and mysqld cannot
\n
"
"InnoDB: access the file, you should modify the permissions.
\n
"
"InnoDB: 2) If the table is not needed, or you can restore it from a backup,
\n
"
"InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
\n
"
"InnoDB: crash recovery and ignore that table.
\n
"
"InnoDB: 3) If the file system or the disk is broken, and you cannot remove
\n
"
"InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
\n
"
"InnoDB: and force InnoDB to continue crash recovery here.
\n
"
,
filepath
);
os_file_close
(
file
);
ut_free
(
filepath
);
if
(
srv_force_recovery
>
0
)
{
fprintf
(
stderr
,
"InnoDB: innodb_force_recovery was set to %lu. Continuing crash recovery
\n
"
"InnoDB: even though we cannot access the .ibd file of this table.
\n
"
,
srv_force_recovery
);
return
;
}
exit
(
1
);
}
/* TODO: What to do in other cases where we cannot access an .ibd
file during a crash recovery? */
/* Every .ibd file is created >= 4 pages in size. Smaller files
cannot be ok. */
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment