To: lfedden@contextworld.com
cc: pgsql-admin@postgresql.org
Subject: Re: OID and filesystem issues 
In-reply-to: <4F91850CA8.07DC00FATFSFQGQL@contextworld.com> 
References: <4F91850CA8.07DC00FATFSFQGQL@contextworld.com>
Comments: In-reply-to lfedden@contextworld.com
	message dated "Tue, 15 Apr 2008 16:25:22 +0100"
Date: Tue, 15 Apr 2008 11:51:20 -0400
Message-ID: <15276.1208274680@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

lfedden@contextworld.com writes:
> Even when logged in as root, a 'ls -l' command returns:

> mm2:/var/lib/pgsql82/data/base/16673 # ls -lash | more
> /bin/ls: 19357877: Permission denied
> /bin/ls: 19569529: Permission denied

You get that as root?  I think you've got filesystem problems that are
beyond the ken of us mere database weenies.  Better ask some kernel
hackers.

(If you're on a SELinux-enabled system it might have to do with SELinux
permissions, although I thought that those typically weren't enforced
against interactive shells.  It might be useful to look in the kernel
log and see if anything comes out when you do this.)

> So can we assume it is safe to remove these none accessible files and also the couple of orphaned OID files from pg_class we can still access?

If it won't let you chown it, it likely won't let you rm it, either...

			regards, tom lane