Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 00A7A2E0050 for ; Tue, 26 Feb 2008 23:27:58 -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 18196-05 for ; Tue, 26 Feb 2008 23:27:56 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from server.firetrust.net (mailserver.firetrust.com [209.213.221.13]) by postgresql.org (Postfix) with ESMTP id 805072E004F for ; Tue, 26 Feb 2008 23:27:56 -0400 (AST) Received: from localhost.localdomain (root@[192.168.1.247]) (authenticated bits=0) by server.firetrust.net (8.14.2/8.14.2) with ESMTP id m1R3RpN0015820 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 27 Feb 2008 16:27:53 +1300 Date: Wed, 27 Feb 2008 16:27:50 +1300 From: Steve Holdoway To: pgsql-admin@postgresql.org Subject: Re: Backup to Tape Incomplete Message-Id: <20080227162750.5638b0e8.steve.holdoway@firetrust.com> In-Reply-To: <01e601c878eb$40e498f0$9b0014ac@wbaus090> References: <47C4B83E.4060408@serioustechnology.com> <01e601c878eb$40e498f0$9b0014ac@wbaus090> Organization: Firetrust Ltd X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.7; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Wed__27_Feb_2008_16_27_50_+1300_Pi=LWzUZPkC4HmYV" X-MailWasher-Server-Scanned: Checked by MailWasher server v2.2.3 (www.Firetrust.com) X-MailWasher-Server-Status: Clean X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/354 X-Sequence-Number: 28428 --Signature=_Wed__27_Feb_2008_16_27_50_+1300_Pi=LWzUZPkC4HmYV Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, 27 Feb 2008 13:48:38 +1100 "Phillip Smith" wrote: > > Coming in the middle of this thread, so slap me if I'm off base here.=20 > > tar will accept standard in as: > >=20 > > tar -cf - > >=20 > > the '-f -' says take input. >=20 > That would be to write to stdout :) I can't figure out how to accept from > stdin :( >=20 > -f is where the send the output, either a file, a device (such as tape) or > stdout (aka '-') Not quite. tar cf - will pipe to stdout, but tar xf - will pipe from stdin.= =20 For the OP's problem, I'd try piping through dd as a file buffer, and run s= ync on completion. Is there a /dev/rst0, like on some of the old unixes ( d= oesn't look like it after checking my CentOS 4 server)? The difference was = that rst0 was unbuffered, and st0 was buffered. Either way, the sync may he= lp. Worth a try (: Steve. --Signature=_Wed__27_Feb_2008_16_27_50_+1300_Pi=LWzUZPkC4HmYV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHxNi2DN07rEXM5z0RAk2rAJ4loQIv8xeotSCxZgqvWmGv4L5eQgCfSkBH dWGnKUtQCjfVRWWCe34lVjw= =HYvE -----END PGP SIGNATURE----- --Signature=_Wed__27_Feb_2008_16_27_50_+1300_Pi=LWzUZPkC4HmYV--