Gluster users - Apr 2012 - errors on restoring postgresql binary dump to glusterfs

Hi There,

While trying to restore a ~700GM binary dump by command

pg_restore -d dbdata < sampledbdata-20120327.pgdump

I encountered following errors repeatedly

pg_restore: [archiver (db)] Error from TOC entry 2882463; 2613
10267347 BLOB 10267347 sdmcleod
pg_restore: [archiver (db)] could not execute query: ERROR:
unexpected data beyond EOF in block 500 of relation base/16386/11743
HINT:  This has been seen to occur with buggy kernels; consider
updating your system.
    Command was: SELECT pg_catalog.lo_create('10267347');



pg_restore: [archiver (db)] could not execute query: ERROR:  large
object 10267347 does not exist
    Command was: ALTER LARGE OBJECT 10267347 OWNER TO sdmcleod;


pg_restore: [archiver (db)] Error from TOC entry 2882464; 2613
10267348 BLOB 10267348 sdmcleod
pg_restore: [archiver (db)] could not execute query: ERROR:
unexpected data beyond EOF in block 500 of relation base/16386/11743
HINT:  This has been seen to occur with buggy kernels; consider
updating your system.
    Command was: SELECT pg_catalog.lo_create('10267348');



pg_restore: [archiver (db)] could not execute query: ERROR:  large
object 10267348 does not exist
    Command was: ALTER LARGE OBJECT 10267348 OWNER TO sdmcleod;


......
......


pg_restore: [archiver (db)] Error from TOC entry 53398; 0 16503 TABLE
DATA l1aaux_sci sdmcleod
pg_restore: [archiver (db)] COPY failed for table "l1aaux_sci": ERROR:
 unexpected data beyond EOF in block 9391 of relation base/16386/17043
HINT:  This has been seen to occur with buggy kernels; consider
updating your system.
CONTEXT:  COPY l1aaux_sci, line 319329: "1854661        \N
1.05156717906094999     1378796678.44843268     2012-02-01
07:04:39.5+00        2012-02-01 07:04:38.4484..."
pg_restore: [archiver (db)] Error from TOC entry 53399; 0 16528 TABLE
DATA l1afts_dbl sdmcleod
pg_restore: [archiver (db)] COPY failed for table "l1afts_dbl": ERROR:
 unexpected data beyond EOF in block 10097 of relation
base/16386/17068
HINT:  This has been seen to occur with buggy kernels; consider
updating your system.
CONTEXT:  COPY l1afts_dbl, line 454411: "459755 2012-03-23
05:31:02.185562+00   ace.sr45190     52867958        299     2591429
FTS     1.1.0   1376321941.75799..."


The server runs Ubuntu server 10.04 LTS with postgresql upgraded to
version 9.1.3-1~lucid. The postgresql data directory is located in a
glusterfs mounted directory to a replicated volume vol-2

192.168.244.101:/vol-2
                     5731222400 3041313920 2398779136  56% /mnt/gluster-2

Here is the gluster info for vol-2:

Volume Name: vol-2
Type: Replicate
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: 192.168.244.101:/data/glbrk-2
Brick2: 192.168.244.102:/data/glbrk-2

The version of glusterfs is 3.2.6.

I think this may have someting to do with glusterfs, because when I
restore the same dump to a same ubuntu 10.04 server with postgresql
upgraded to the same 9.1.3-1~lucid located in a local ext4 filesystem,
the pg_restore went well without a single error.

Has anyone seen something similar before?

Thank you.

Liang Ma