| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | anjali_524(at)yahoo(dot)co(dot)in, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6372: Error while creating database with fsync parameter as on incase of CIFS |
| Date: | 2012-01-02 20:14:32 |
| Message-ID: | 1149.1325535272@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Mon, Jan 2, 2012 at 17:27, <anjali_524(at)yahoo(dot)co(dot)in> wrote:
>> PST ERROR: could not fsync file "base/16409": Invalid argument Dec 30
>> 03:00:26 devok64-8 postgres_cifs_kaz_1[15812]: [2-2] [local] 15812
>> 2011-12-30 03:00:26.511 PST STATEMENT: CREATE DATABASE "KazDB
The specific error seems to be coming from copydir.c's attempt to fsync
a directory. We are already ignoring EBADF there, and could presumably
fix at least this symptom if we ignored EINVAL.
> PostgreSQL does not support data directory over CIFS.
I'm wondering what's your basis for asserting we don't support CIFS in
general? It's probably not terribly bulletproof, but any worse than NFS?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2012-01-02 20:18:27 | Re: BUG #6372: Error while creating database with fsync parameter as on incase of CIFS |
| Previous Message | Noah Misch | 2012-01-02 19:46:35 | Re: Re: BUG #6264: Superuser does not have inherent Replication permission |