From: | Andrea Gelmini <andrea(dot)gelmini(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Noah Misch <noah(at)leadboat(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Direct I/O |
Date: | 2023-04-10 07:04:22 |
Message-ID: | CAK-xaQZ8AmE=eeaq_=VuQAPtDnXzYAQoKV0_Qs9ukjhBOpD5Wg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Il giorno lun 10 apr 2023 alle ore 04:58 Andres Freund
<andres(at)anarazel(dot)de> ha scritto:
> We should definitely let the brtfs folks know of this issue... It's possible
> that this bug was recently introduced even. What kernel version did you repro
> this on Thomas?
In these days on BTRFS ml they are discussing about Direct I/O data
corruption. No patch at the moment, they are still discussing how to
address it:
https://lore.kernel.org/linux-btrfs/aa1fb69e-b613-47aa-a99e-a0a2c9ed273f(at)app(dot)fastmail(dot)com/
Ciao,
Gelma
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2023-04-10 07:27:27 | Re: Direct I/O |
Previous Message | Michael Paquier | 2023-04-10 04:08:43 | Re: WAL Insertion Lock Improvements |