| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | "Phillip Smith" <phillip(dot)smith(at)weatherbeeta(dot)com(dot)au>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Backup to Tape Incomplete |
| Date: | 2008-02-27 06:08:38 |
| Message-ID: | 14600.1204092518@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> writes:
> I wonder what it's meaning by invalid arg?
On my Fedora machine, "man write" explains EINVAL thusly:
EINVAL fd is attached to an object which is unsuitable for writing; or
the file was opened with the O_DIRECT flag, and either the
address specified in buf, the value specified in count, or the
current file offset is not suitably aligned.
I'm not sure that writing to a tape is quite like O_DIRECT, but the
mention of an un-aligned count seems pretty relevant. If you grant
the assumption that the underlying problem is that the tape drive
has to be written to in multiples of its blocksize, then this supports
the idea that a violation of that rule would be reported as EINVAL.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Darren Reed | 2008-02-27 06:39:12 | Re: How to reindex when unable to open relation? |
| Previous Message | Phillip Smith | 2008-02-27 05:35:50 | Re: Backup to Tape Incomplete |