Обсуждение: could not link file "pg_xlog/xlogtemp.72606"
Hi there, We recently copied over our 8.3 database cluster files from a local disk to a network attached storage drive. Everything seemed to work okay for a while until we got this error: ERROR: could not link file "pg_xlog/00000001000000AA00000030" to "pg_xlog/00000001000000AA00000096" (initialization oflog file 170, segment 150): Operation not supported pg_xlog/00000001000000AA00000096 does not exist in the original file tree, so I'm wondering if there's some special linkthat PG is trying to create that is not permitted in the NAS drive? This is for Postgresql 8.3 + PostGIS 1.5 Would appreciate any pointers. This is a test environment, so nothing is lost, but we'd like to use the NAS for storageas the local disk doesn't have enough space. Claire.
On Fri, Feb 15, 2013 at 6:25 PM, Claire McLister <mclister@zeesource.net> wrote: > Hi there, > > We recently copied over our 8.3 database cluster files from a local disk to > a network attached storage drive. > > Everything seemed to work okay for a while until we got this error: > > ERROR: could not link file "pg_xlog/00000001000000AA00000030" to > "pg_xlog/00000001000000AA00000096" (initialization of log file 170, segment > 150): Operation not supported > > pg_xlog/00000001000000AA00000096 does not exist in the original file tree, > so I'm wondering if there's some special link that PG is trying to create > that is not permitted in the NAS drive? That's a regular (hard) link. Whether it's supported or not would depend on your NAS, but it certainly looks like it's not supported by yours - or you need different mount options. For example, if your NAS runs something Windows-based, it's likely not supporting links at all. Note that putting the data directory on a NAS is in general not a good idea - it's very easy to get corruption that way, unless you are very careful. > This is for Postgresql 8.3 + PostGIS 1.5 Also, do note that PostgreSQL 8.3 is no longer supported - see http://www.postgresql.org/support/versioning/. You should look into upgrading ASAP. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
Thanks. I checked and hard links are not supported by the NAS. Will look into getting another disk. Yes, should upgrade out of 8.3. Thanks again. Claire ---- On Mon, 18 Feb 2013 08:21:19 -0800 Magnus Hagander <magnus@hagander.net> wrote ---- On Fri, Feb 15, 2013 at 6:25 PM, Claire McLister <mclister@zeesource.net> wrote: > Hi there, > > We recently copied over our 8.3 database cluster files from a local disk to > a network attached storage drive. > > Everything seemed to work okay for a while until we got this error: > > ERROR: could not link file "pg_xlog/00000001000000AA00000030" to > "pg_xlog/00000001000000AA00000096" (initialization of log file 170, segment > 150): Operation not supported > > pg_xlog/00000001000000AA00000096 does not exist in the original file tree, > so I'm wondering if there's some special link that PG is trying to create > that is not permitted in the NAS drive? That's a regular (hard) link. Whether it's supported or not would depend on your NAS, but it certainly looks like it's not supported by yours - or you need different mount options. For example, if your NAS runs something Windows-based, it's likely not supporting links at all. Note that putting the data directory on a NAS is in general not a good idea - it's very easy to get corruption that way, unless you are very careful. > This is for Postgresql 8.3 + PostGIS 1.5 Also, do note that PostgreSQL 8.3 is no longer supported - see http://www.postgresql.org/support/versioning/. You should look into upgrading ASAP. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general