pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Phillip Smith <phillip.smith@weatherbeeta.com.au>
Cc: pgsql-admin@postgresql.org
Subject: Re: Backup to Tape Incomplete
Date: Wed, 27 Feb 2008 01:08:38 -0500
Message-ID: <14600.1204092518@sss.pgh.pa.us> (raw)
In-Reply-To: <dcc563d10802262123q1f6770afu4a466ec88ff29b1f@mail.gmail.com>
References: <dcc563d10802261946w5c064c66g689be5ad0563476f@mail.gmail.com>
	<020401c878f8$1194b500$9b0014ac@wbaus090>
	<dcc563d10802262123q1f6770afu4a466ec88ff29b1f@mail.gmail.com>

"Scott Marlowe" <scott.marlowe@gmail.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



view thread (15+ messages)  latest in thread

Message-ID: <14600.1204092518@sss.pgh.pa.us>
Permalink:  ../14600.1204092518@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/14600.1204092518@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, scott.marlowe@gmail.com, phillip.smith@weatherbeeta.com.au
  Subject: Re: Backup to Tape Incomplete
  In-Reply-To: <14600.1204092518@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox