Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100

Harry Ambrose <harry.ambrose@xxxxxxxxx> · Fri, 9 Jun 2017 17:02:50 +0100

Hi,

    Maybe you could give some info on :

    - your ext3 mkfs and mount options (journal, barriers, etc)
/etc/fstab details below: 
LABEL=/var/lib/pgsql        /var/lib/pgsql          	ext3    defaults        1 2
LABEL=/tablespace1          /tablespace1                ext3    defaults        1 2
LABEL=/tablespace2          /tablespace2                ext3    defaults        1 2
LABEL=/tablespace3          /tablespace3                ext3    defaults        1 2
pg_default:
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags:         signed_directory_hash 
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              36634624
Block count:              146506767
Reserved block count:     7325338
Free blocks:              143785740
Free inodes:              36627866
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      989
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
RAID stride:              64
RAID stripe width:        64
Filesystem created:       Fri Aug  9 16:11:53 2013
Last mount time:          Fri Apr 21 22:37:02 2017
Last write time:          Fri Apr 21 22:37:02 2017
Mount count:              2
Maximum mount count:      100
Last checked:             Thu Sep 15 18:52:43 2016
Check interval:           31536000 (12 months, 5 days)
Next check after:         Fri Sep 15 18:52:43 2017
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4

Journal backup:           inode blocks
tablespaces
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags:         signed_directory_hash 
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              73261056
Block count:              293013543
Reserved block count:     14650677
Free blocks:              286208439
Free inodes:              73174728
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      954
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
RAID stride:              64
RAID stripe width:        128
Filesystem created:       Fri Aug  9 16:11:53 2013
Last mount time:          Fri Apr 21 22:37:02 2017
Last write time:          Fri Apr 21 22:37:02 2017
Mount count:              2
Maximum mount count:      100
Last checked:             Thu Sep 15 18:52:43 2016
Check interval:           31536000 (12 months, 5 days)
Next check after:         Fri Sep 15 18:52:43 2017
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Journal backup:           inode blocks

    - your controller setup (battery should be working good and cache
    mode set to write back)
Cache Board Present: True
Cache Status: OK
Cache Ratio: 10% Read / 90% Write
Drive Write Cache: Disabled
Total Cache Size: 2.0 GB
Total Cache Memory Available: 1.8 GB
No-Battery Write Cache: Disabled
SSD Caching RAID5 WriteBack Enabled: False
SSD Caching Version: 1
Cache Backup Power Source: Capacitors
Battery/Capacitor Count: 1
Battery/Capacitor Status: OK 

    - your disks setup (write cache should be disabled)
Write cache is disabled, see above. 

    - you should check your syslogs/messages for any errors related to
    storage
No error messages found. 

    - is your RAM ECC? Did you run any memtest?
Yes, memory is ECC. No error messages found.

    - is your CPU overheating ?
No overheating issues. 

    - have you experienced any crashes/freezes ?

No crashes/freezes experienced.

Best wishes,
Harry