Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 653E4632E5A for ; Tue, 17 Feb 2009 07:21:00 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 18724-04 for ; Tue, 17 Feb 2009 07:20:57 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mailsrv1.zmi.at (mailsrv1.zmi.at [212.69.162.198]) by mail.postgresql.org (Postfix) with ESMTP id 6ADAD632E56 for ; Tue, 17 Feb 2009 07:20:57 -0400 (AST) Received: from saturn.localnet (h081217054243.dyn.cm.kabsi.at [81.217.54.243]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mailsrv1.zmi.at (Postfix) with ESMTP id 79EA6404F for ; Tue, 17 Feb 2009 12:20:54 +0100 (CET) From: Michael Monnerie Organization: it-management http://it-management.at To: pgsql-admin@postgresql.org Subject: Re: 8.3.5 broken after power fail Date: Tue, 17 Feb 2009 12:20:54 +0100 User-Agent: KMail/1.10.3 (Linux/2.6.27.13-ZMI; KDE/4.1.3; x86_64; ; ) MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200902171220.54530@zmi.at> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200902/112 X-Sequence-Number: 31333 > tether your daughter to the other side of the room? I'm not sure > which parts of those mount options are dangerous or not. I use ext3 > stock with noatime. And a battery backed RAID. Smaller slower work > group / station controllers (i.e. 5 year old server conrollers) go > for pretty cheap and give pretty good performance with 2 or 4 drives. I know the problem is with XFS and mount option "nobarrier" within a XEN vm. Just last week I discussed with the XFS devs if that would be save to use with a battery backed RAID. They said "depends on the hypervisor". So now I proofed (not that I wanted!) that within XEN, XFS should always have "barrier" on. > AS for fixing it, I believe the answer involves creating a clog file > full of zeros 16Meg or so, and pg_reset_xlog. Don't count on all > your data being there or all your FK-PK type relationships to be > correct, Immediately dump it, initdb and reload your data, fixing it > as you go. OK, that's a start. Trying... still an error: pg_dump: Fehlermeldung vom Server: ERROR: missing chunk number 0 for toast value 1460201 in pg_toast_1281127 pg_dump: Die Anweisung war: COPY public.dbmail_messageblks (messageblk_idnr, physmessage_id, messageblk, blocksize, is_header) TO stdout; What now? mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0660 / 415 65 31 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import" // Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4 // Keyserver: wwwkeys.eu.pgp.net Key-ID: 1C1209B4