pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: Rui DeSousa <rui.desousa@icloud.com>
Cc: Dianne Skoll <dfs@roaringpenguin.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: Reliable WAL file shipping over unreliable network
Date: Thu, 1 Mar 2018 18:03:42 +1300
Message-ID: <ea674584-85bc-3f63-c182-0d45123bb3eb@catalyst.net.nz> (raw )
In-Reply-To: <6056907B-551F-4ED0-804B-0FCACD39EB23@icloud.com >
References: <dd116172-3ddf-ee56-57f3-6e18d49abf8e@shopzeus.com >
<400AC9CD-1E43-422C-A689-70BDBAFF231E@elevated-dev.com >
<ee3ae4be-ab24-8443-82c1-95bcd4f86a63@shopzeus.com >
<debd4205-e27a-cd9d-9169-6748e65083a2@shopzeus.com >
<BA4A1866-95B0-49C6-8CD1-3D1B60A7837E@elevated-dev.com >
<CF30D15A-BD42-42A7-9AD3-BB69AF9E8047@icloud.com >
<D5B11CF5-E816-435B-BFB8-1226E23C046A@elevated-dev.com >
<37C5A42B-4CDD-4F01-8F1E-1B185C1819B9@icloud.com >
<20180228132620.2c882f84@hydrogen.roaringpenguin.com >
<33220469-5BB2-4A40-8F56-8F4F392C95B3@icloud.com >
<21AF0CB4-0873-4960-BA14-E72FA08B352E@icloud.com >
<5a49c387-e4f4-f70c-537c-9c338c80b687@catalyst.net.nz >
<9DDA6F85-077E-4F8D-8708-632CC2907D3C@icloud.com >
<06dd8b81-8b1a-ae5c-8ddd-1556b5946176@catalyst.net.nz >
<6056907B-551F-4ED0-804B-0FCACD39EB23@icloud.com >
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@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
view thread (59+ messages) latest in thread
Message-ID: <ea674584-85bc-3f63-c182-0d45123bb3eb@catalyst.net.nz>
Permalink: ../ea674584-85bc-3f63-c182-0d45123bb3eb@catalyst.net.nz/
Also on: postgresql.org/message-id/ea674584-85bc-3f63-c182-0d45123bb3eb@catalyst.net.nz
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: mark.kirkwood@catalyst.net.nz, rui.desousa@icloud.com, dfs@roaringpenguin.com, pgsql-admin@lists.postgresql.org
Subject: Re: Reliable WAL file shipping over unreliable network
In-Reply-To: <ea674584-85bc-3f63-c182-0d45123bb3eb@catalyst.net.nz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox