| From: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
|---|---|
| To: | Rui DeSousa <rui(dot)desousa(at)icloud(dot)com> |
| 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 05:03:42 |
| Message-ID: | ea674584-85bc-3f63-c182-0d45123bb3eb@catalyst.net.nz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 01/03/18 17:57, Rui DeSousa wrote:
> 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]
>
>
Interesting - so could be rsync not handling the quota error sensibly -
or perhaps more likely ZFS and/or quota bugs. If the latter the solution
would be not to use these until the devs have fixed them... :-)
regards
Mark
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rui DeSousa | 2018-03-01 05:18:01 | Re: Reliable WAL file shipping over unreliable network |
| Previous Message | Rui DeSousa | 2018-03-01 04:57:44 | Re: Reliable WAL file shipping over unreliable network |