Has anyone successfully used encfs with postgresq recently? I'm not sure if this is specifically a postgresql problem, but I'm trying to get postgresql to run on an encrypted file system that is a copy of my live data directory tree (after a shutdown, of course) and am getting the following errors in the log:
LOG: database system was shut down at 2011-06-21 23:21:08 CDT LOG: checkpoint record is at 9/D6A7078 LOG: redo record is at 9/D6A7078; undo record is at 0/0; shutdown TRUE LOG: next transaction ID: 0/6712; next OID: 137017002 LOG: next MultiXactId: 1; next MultiXactOffset: 0 PANIC: could not open file "pg_xlog/00000001000000090000000D" (log file 9, segment 13): Invalid argument LOG: startup process (PID 21248) was terminated by signal 6 LOG: aborting startup due to startup process failure The database version here is 8.2.11, running on a Linux Fedora Core 14 server. The encrypted file system was created and mounted as the postgres user. I can read the "pg_xlog/00000001000000090000000D" file as the postgres user and the log entries were written in a directory that is part of the encrypted file system, so it appears that encfs is working as it should. Since as far as I can tell the postgres user has full access on that directory once mounted, my best guess is that postgresql is trying to access the pg_xlog file as some user other than postgres, Mounting the file system in --public mode doesn't have any impact. FWIW, the reason I'm doing this is I'm trying to create a copy of a client database I can take with me to a conference this summer but I'd prefer it to be encrypted in the event the portable drive it is on is lost or stolen. So far this appears to be the best option available. I'm testing it to see if performance is going to be a major concern. -- Mike Nolan no...@tssi.com
