On 13.12.24 15:24, Andrey Zhadchenko wrote:
On 12/13/24 14:20, Alexander Atanasov wrote:
On 13.12.24 15:17, Andrey Zhadchenko wrote:
On 12/5/24 22:56, Alexander Atanasov wrote:
direct IO write result ENOTBLK or 0(in ext4 case) means
retry IO in buffered mode. We wrongly assumed that it is
On 12/13/24 14:20, Alexander Atanasov wrote:
On 13.12.24 15:17, Andrey Zhadchenko wrote:
On 12/5/24 22:56, Alexander Atanasov wrote:
direct IO write result ENOTBLK or 0(in ext4 case) means
retry IO in buffered mode. We wrongly assumed that it is
a short write and handled it incorrectly
Si
On 13.12.24 15:17, Andrey Zhadchenko wrote:
On 12/5/24 22:56, Alexander Atanasov wrote:
direct IO write result ENOTBLK or 0(in ext4 case) means
retry IO in buffered mode. We wrongly assumed that it is
a short write and handled it incorrectly
Since we can not retry in buffered mode, code is n
On 12/5/24 22:56, Alexander Atanasov wrote:
direct IO write result ENOTBLK or 0(in ext4 case) means
retry IO in buffered mode. We wrongly assumed that it is
a short write and handled it incorrectly
Since we can not retry in buffered mode, code is not ready
for it. Take a different route. Thi
