Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 91D859FBCF5 for ; Tue, 29 May 2007 19:15:54 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 65254-05 for ; Tue, 29 May 2007 19:15:47 -0300 (ADT) X-Greylist: delayed 00:06:48.942254 by SQLgrey-1.7.4 Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by postgresql.org (Postfix) with ESMTP id C204F9FBC6F for ; Tue, 29 May 2007 19:15:50 -0300 (ADT) Received: by wa-out-1112.google.com with SMTP id v27so801483wah for ; Tue, 29 May 2007 15:15:49 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=JaSzJVSFdgtrFDV0oeYzb0KAUvtcQm74PODEIKw/zokbVvNT7GYdTNWd2djw29jdCFFrnlIkK6ZGO9HCciHISjOdJyR8HLETZmVFGeA/16CRK1PpJ2Qu6U0Ae2eJCBpqUwBM4Hy97qSG4Z2gCA+POAI8dA7AnpjbG/CdqtEstm4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=m991OPBxFfeMS6KNwNN9cEi5kfz7xZWmB8nbb2H73OVbyxW6cStIJ8ZTUbUha6l3IEQxTMmaFS0EQYYk5kZdlYQv2L9QdnV+xCcptrvO8WD2zG1bF7TuzHQtCVbc3jSuXEdqzse1CDS3ecWCLGbTfYWaiYvPSodACgLmvU87sUw= Received: by 10.115.78.1 with SMTP id f1mr3640168wal.1180476540374; Tue, 29 May 2007 15:09:00 -0700 (PDT) Received: by 10.114.80.6 with HTTP; Tue, 29 May 2007 15:09:00 -0700 (PDT) Message-ID: Date: Wed, 30 May 2007 02:09:00 +0400 From: "Roman Chervotkin" To: pgsql-admin@postgresql.org Subject: pg_dump: Error message from server: ERROR: compressed data is corrupt MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_208286_33172501.1180476540348" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.19 tagged_above=0 required=5 tests=BAYES_40=-0.185, HTML_30_40=0.374, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200705/310 X-Sequence-Number: 25630 ------=_Part_208286_33172501.1180476540348 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Do usual pg_dump today and have got an error. --------------------- pg_dump: SQL command failed pg_dump: Error message from server: ERROR: compressed data is corrupt pg_dump: The command was: COPY public.candidates (id, name, surname, mid_name, compensation, created, birthday, updated, creator_id, updater_id, home_region_id, home_city, home_street, other_languages, home_region_other, edu_conformity, sex, deleted, resume_text, resume_text_index, mark, kids, driving_license, marital_status, software_knowledge, business_contacts, type_writing_rus, type_writing_lat, desired_duties, desired_other, updater_name, citizenship, compensation_currency, folder_id, plus, random_cat, temp_reg, "temp") TO stdout; ---------------------- I had 8.2.0 on Solaris 10 (SunOS server3 5.10 Generic_125101-05 ), pg_data_dir on zfs mirrored pool. I've checked status of pool and got: ---------------------- -bash-3.00# zpool status tank pool: tank state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: scrub completed with 0 errors on Tue May 29 19:46:12 2007 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 mirror ONLINE 0 0 0 c1t0d0 ONLINE 1 0 0 c1t4d0 ONLINE 0 0 0 errors: No known data errors -------------------------------------------------------- So it seems a drive should be replaced but pool is still functioning. I still can copy pg_data_dir to other filesystem without any errors. And database seems working as usual. So I guess pg_dump should work but It does not. I've upgraded to 8.2.4 but still have the same error. Copy pg_data_dir to another file system, start postgres with that data_dir, tried pg_dump again but still have the error. So the question is what should I do in order to pg_dump start working as usual? Thanks Roman. ------=_Part_208286_33172501.1180476540348 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline Do usual pg_dump today and have got an error.

---------------------
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR:  compressed data is corrupt
pg_dump: The command was: COPY public.candidates (id, name, surname, mid_name, compensation, created, birthday, updated, creator_id, updater_id, home_region_id, home_city, home_street, other_languages, home_region_other, edu_conformity, sex, deleted, resume_text, resume_text_index, mark, kids, driving_license, marital_status, software_knowledge, business_contacts, type_writing_rus, type_writing_lat, desired_duties, desired_other, updater_name, citizenship, compensation_currency, folder_id, plus, random_cat, temp_reg, "temp") TO stdout;
----------------------

I had 8.2.0 on Solaris 10 (SunOS server3 5.10 Generic_125101-05 ), pg_data_dir on zfs mirrored pool. I've checked status of pool and got:

----------------------
-bash-3.00# zpool status tank
  pool: tank
 state: ONLINE
status: One or more devices has experienced an unrecoverable error.  An
        attempt was made to correct the error.  Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
        using 'zpool clear' or replace the device with 'zpool replace'.
   see: http://www.sun.com/msg/ZFS-8000-9P
 scrub: scrub completed with 0 errors on Tue May 29 19:46:12 2007
config:

        NAME        STATE     READ WRITE CKSUM
        tank        ONLINE       0     0     0
          mirror    ONLINE       0     0     0
            c1t0d0  ONLINE       1     0     0
            c1t4d0  ONLINE       0     0     0

errors: No known data errors
--------------------------------------------------------

So it seems a drive should be replaced but pool is still functioning. I still can copy pg_data_dir to other filesystem without any errors. And database seems working as usual. So I guess pg_dump should work but It does not. I've upgraded to 8.2.4 but still have the same error. Copy pg_data_dir to another file system, start postgres with that data_dir, tried pg_dump again but still have the error.

So the question is what should I do in order to pg_dump start working as usual?


Thanks
Roman.


------=_Part_208286_33172501.1180476540348--