| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | james(dot)e(dot)hughes(at)boeing(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #8238: duplicate of bug #6372 on panffs |
| Date: | 2013-06-22 22:26:46 |
| Message-ID: | 27236.1371940006@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
james(dot)e(dot)hughes(at)boeing(dot)com writes:
> Upon creating a database on a panfs (Panasas proprietary fs) directory I
> get:
> createdb: database creation failed: ERROR: could not fsync file
> "base/16387": Invalid argument
> This is a duplicate of bug #6372 and is fixed by applying the patch for
> copydir.c listed in the thread. So we confirm this problem also exists on
> another fs in addition to CIFS.
Thanks for the report. Looking back at the previous thread, it seems we
chose not to change the code (to ignore EINVAL for fsync-on-a-directory)
on the grounds that CIFS couldn't be considered a supported filesystem
anyway. Do you find that panfs works all right for Postgres other than
this issue?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2013-06-23 16:53:59 | Re: BUG #7493: Postmaster messages unreadable in a Windows console |
| Previous Message | Sandeep Thakkar | 2013-06-22 01:53:03 | Re: Re: [BUGS] Sorry to bother you. Please tell me exactly how the compiler was built ODBC |