| From: | Rui DeSousa <rui(dot)desousa(at)icloud(dot)com> |
|---|---|
| To: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
| Cc: | Dianne Skoll <dfs(at)roaringpenguin(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Reliable WAL file shipping over unreliable network |
| Date: | 2018-03-01 04:57:44 |
| Message-ID: | 6056907B-551F-4ED0-804B-0FCACD39EB23@icloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
It looks like rsync is not handling the disk quota when actually syncing the file — Disc quota exceeded (69) vs no space left (28). It only fails if it can’t rename the truncated temp file — and in some cases there is just enough space left to allow the rename to succeed thus leaving a truncated WAL file.
I’m using ZFS; and have 1GB quota on the given filesystem.
[postgres(at)hades ~/dbc1/pg_wal]$ rsync -a 000000010000005B00000035 ~/arch/dbc1/wal/000000010000005B00000035
rsync: rename "/usr/home/postgres/arch/dbc1/wal/.000000010000005B00000035.6bjO94" -> "000000010000005B00000035": Disc quota exceeded (69)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1200) [sender=3.1.2]
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2018-03-01 05:03:42 | Re: Reliable WAL file shipping over unreliable network |
| Previous Message | Ian Barwick | 2018-03-01 04:51:28 | Re: WAL segment not replicated |