Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 3E9DE2E006D for ; Wed, 27 Feb 2008 01:23:07 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 27248-06 for ; Wed, 27 Feb 2008 01:23:04 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by postgresql.org (Postfix) with ESMTP id 476EF2E0075 for ; Wed, 27 Feb 2008 01:23:04 -0400 (AST) Received: by wa-out-1112.google.com with SMTP id m38so2893364waf.5 for ; Tue, 26 Feb 2008 21:23:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=EVbxKjhiNEwz8eLSXPUXfWo2BDQeTg2q80gyiS0zlwY=; b=pCQGzh2YoICWn/XwmPcGJlBFP6vhb5sylw1z9mqj5xT1Y0qV9siIqWVrBKcENV9T43lNvfUqrxQZ2QZLIU5/NdRQp5Z9YRE6ADuh+8GWYgO/ySKgGDoIXtpd/z+f/uKKzUVShPpvhqCSQAVwALqTmjIKOwnYypuT1VxDYFkIWTY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lkE6hgOI6CPJ90eT76AOIFeBuFPxiTACOt8h06zCdpg5tgxmzX9jy+7T0d72o3UOHvL3W1bFlPJt0yHz0zlHkY6/NNWJe9DARRhiIDbCEaIvln2Pfd0o9smfog8Gf8rDtYed5pGagv36tX7RtV0b3rvC7KsYPesfM3VjtDYIM10= Received: by 10.114.209.1 with SMTP id h1mr6741028wag.130.1204089783457; Tue, 26 Feb 2008 21:23:03 -0800 (PST) Received: by 10.114.133.6 with HTTP; Tue, 26 Feb 2008 21:23:03 -0800 (PST) Message-ID: Date: Tue, 26 Feb 2008 23:23:03 -0600 From: "Scott Marlowe" To: "Phillip Smith" Subject: Re: Backup to Tape Incomplete Cc: pgsql-admin@postgresql.org In-Reply-To: <020401c878f8$1194b500$9b0014ac@wbaus090> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <020401c878f8$1194b500$9b0014ac@wbaus090> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/361 X-Sequence-Number: 28435 On Tue, Feb 26, 2008 at 10:20 PM, Phillip Smith wrote: > > > > Do we think this is a Postgres problem, a Linux problem or a problem > > > specific to my hardware setup? Was I wrong to think that I should be > > > able to stream directly from pg_dump to /dev/st0? I would have > > > thought it *should* work, but maybe I was wrong in the first place > > > with that? > > > > If you can dd the file onto your tape drive, then it's some weird > interaction between > > pg_dump and your system I'd think. Could the be some maximum size that > you can buffer > > through pipes / redirects on your machine? > > > > I'd test to see if cat pgdumpfile.sql > /dev/st0 works or not. If it > fails at the > > same approximate size, then it's something to do with redirection. If > > tar works but > > redirects fail, then the problem isn't with postgresql. i.e. do something > similar to > > what you're doing with pgsql and see which things fail and which ones > don't. > > It appears to be me :( > > [postgres@stirling ~]$ cat /tmp/dbname080225.sql > /dev/st0 > cat: write error: Invalid argument > > It ran for a good 30 minutes, then died with that. I wonder what it's meaning by invalid arg? Is something in the .sql file somehow coming across as an argument? Can you cat the sql file to /dev/null successfully?