Re: Kernel 2.4->2.6 upgrade results in PANIC: could not locate a
От | Achilleus Mantzios |
---|---|
Тема | Re: Kernel 2.4->2.6 upgrade results in PANIC: could not locate a |
Дата | |
Msg-id | Pine.LNX.4.44.0604141425400.28770-100000@matrix.gatewaynet.com обсуждение исходный текст |
Ответ на | Kernel 2.4->2.6 upgrade results in PANIC: could not locate a valid checkpoint record (Achilleus Mantzios <achill@matrix.gatewaynet.com>) |
Ответы |
Thoughts on a Isolation/Security problem.
|
Список | pgsql-admin |
Problem solved. The sysadmins yesterday forgot to mention to me that they didnt mount correctly all the file systems (including the one of pg_xlog). Sorry for the noise :-) O Achilleus Mantzios έγραψε στις Apr 14, 2006 : > > Hi, we have happily been running postgresql 7.4.x (currently 7.4.12) on a > debian linux with kernel 2.4.x for some years without any issues. > Yesterday after switching to 2.6.16 we experienced the following problem > upon pgsql startup: > > LOG: could not open file "/var/lib/pgsql/data/pg_xlog/0000006900000091" > (log file 1 05, segment 145): No such file or directory > LOG: invalid primary checkpoint record > LOG: could not open file "/var/lib/pgsql/data/pg_xlog/0000006900000091" > (log file 1 05, segment 145): No such file or directory > LOG: invalid secondary checkpoint record > PANIC: could not locate a valid checkpoint record > LOG: startup process (PID 414) was terminated by signal 6 > LOG: aborting startup due to startup process failure > > After reverting back to kernel 2.4, postgresql started up hapilly again. > > Any ideas? > -- -Achilleus
В списке pgsql-admin по дате отправления: