Puredisk DR backup's failing

Article:TECH157753  |  Created: 2011-04-09  |  Updated: 2012-07-28  |  Article URL http://www.symantec.com/docs/TECH157753
Article Type
Technical Solution

Product(s)

Issue



Puredisk DR backup will fail with the error below when the freed up disk pages are not released causing postages increasingly consuming the disk space as the freed up mappings cannot be reused.

<2011-03-30 13:31:18 WST>ERROR:  cache lookup failed for index 69196652
 


Error



pg_dump: Error message from server: ERROR:  cache lookup failed for index 69196647
pg_dump: The command was: SELECT t.tableoid, t.oid, t.relname as indexname, pg_catalog.pg_get_indexdef(i.indexrelid) as indexdef, t.relnatts as indnkeys, i.indkey, i.indisclustered, c.contype, c.conname, c.tableoid as contableoid, c.oid as conoid, (SELECT spcname FROM pg_catalog.pg_tablespace s WHERE s.oid = t.reltablespace) as tablespace, array_to_string(t.reloptions, ', ') as options FROM pg_catalog.pg_index i JOIN pg_catalog.pg_class t ON (t.oid = i.indexrelid) LEFT JOIN pg_catalog.pg_depend d ON (d.classid = t.tableoid AND d.objid = t.oid AND d.deptype = 'i') LEFT JOIN pg_catalog.pg_constraint c ON (d.refclassid = c.tableoid AND d.refobjid = c.oid) WHERE i.indrelid = '36712463'::pg_catalog.oid ORDER BY indexname
 

postgresql log:

<2011-03-30 13:31:18 WST>ERROR:  cache lookup failed for index 69196652
<2011-03-30 13:31:18 WST>STATEMENT:  SELECT t.tableoid, t.oid, t.relname as indexname, pg_catalog.pg_get_indexdef(i.indexrelid) as indexdef, t.relnatts as indnkeys, i.indkey, i
.indisclustered, c.contype, c.conname, c.tableoid as contableoid, c.oid as conoid, (SELECT spcname FROM pg_catalog.pg_tablespace s WHERE s.oid = t.reltablespace) as tablespace,
 array_to_string(t.reloptions, ', ') as options FROM pg_catalog.pg_index i JOIN pg_catalog.pg_class t ON (t.oid = i.indexrelid) LEFT JOIN pg_catalog.pg_depend d ON (d.classid =
 t.tableoid AND d.objid = t.oid AND d.deptype = 'i') LEFT JOIN pg_catalog.pg_constraint c ON (d.refclassid = c.tableoid AND d.refobjid = c.oid) WHERE i.indrelid = '36712463'::p
g_catalog.oid ORDER BY indexname
 

 


Cause



Resource used exceeding the limit of max_fsm_pages


Solution



* Execute #/opt/pddb/bin/psql -U pddb mb -c "vacuum analyze verbose" > /root/vacuum_mb_1.log 2>&1

* The last line in the log will indicate the appropriate value for the parameters that control the FSM (Free space map). E.g.:

   NFO:  free space map contains 2994056 pages in 542 relations
   DETAIL:  A total of 3000000 page slots are in use (including overhead).
   7804112 page slots are required to track all free space.
   Current limits are:  3000000 page slots, 1000 relations, using 17683 kB.
   NOTICE:  number of page slots needed (7804112) exceeds max_fsm_pages (3000000)
  HINT:  Consider increasing the configuration parameter "max_fsm_pages" to a value over 7804112.

NOTE: In some occasion, running the psql statement of "vacuum analyze verbose" will not work and appears to be hanging (with no result even after 24 hours). In this case, simply get the <Storage path>/logs/pddb/postgresql.log* and it's very likely we can find similar message like above indicating max_fsm_pages limit exceeded.

<2012-03-04 11:55:38 EST>NOTICE:  number of page slots needed (8586992) exceeds max_fsm_pages (2000000)
<2012-03-04 11:55:38 EST>HINT:  Consider increasing the configuration parameter "max_fsm_pages" to a value over 8586992.
<2012-03-04 11:55:38 EST>LOG:  number of page slots needed (8586992) exceeds max_fsm_pages (2000000)


 * /etc/init.d/puredisk stop 

 * Adjust 'max_fsm_pages' parameter in /Storage/databases/pddb/data/postgresql.conf file

 * /etc/init.d/puredisk start pddb

 *  /etc/init.d/puredisk start

 




Article URL http://www.symantec.com/docs/TECH157753


Terms of use for this information are found in Legal Notices