Sorry for not replying immediately, but I was on holiday.
As regards the InitRelink error, you were correct. It was to do with the
link() command not executing on a samba share over windows (hard link).
Was solved by using a linux nfs.
As for reliability zero I concur but we do not have any choice. The
database space is finished on the machine and we can't increase it without
formatting. So we had an extra 50GB partition on another machine available
temporarily. Problem is that vacuum still failed with an out of disk space
message. Anyone knows on how much a table needs to be vacuumed correctly ?
(A 20GB table with 4GB indexes did not vacuum in 50GB of free space).
Regards
Robert
Tom Lane
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
pa.us> cc: [EMAIL PROTECTED]
Subject: Re: [ADMIN] Strange error
message
19/08/2001
17:09
[EMAIL PROTECTED] writes:
> FATAL 2: InitRelink(logfile 347 seg 167) failed: Operation not permitted
Looks like a permissions problem in the pg_xlog directory. Is that
directory owned and writable by the postgres user?
> The setup is as follows, the pg_xlog is situated on another PC (win
> 2000) mounted using samba.
Gack. I'd rate this as a "zero reliability" setup. I take it your data
is not very important to you? If it is, find a way to avoid using NFS.
Especially NFS to a Windoze server.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
