tdb file corruption when fsync/fdatasync fails

Tue Sep 18 05:48:41 UTC 2018

On Mon, Sep 17, 2018 at 12:52:23PM -0700, Jeremy Allison via samba-technical wrote:
> > Aug 29 09:35:02 localhost kernel: [ 4798.314228] EXT4-fs (sda1): Delayed block allocation failed for inode 1323116 at logical offset 4 with max blocks 2 with error 121
> > 
> > Aug 29 09:35:02 localhost kernel: [ 4798.315778] EXT4-fs (sda1): This should not happen!! Data will be lost
> 
> This is a kernel filesystem failure, not a Samba bug.
> 
> Sorry, you need to report this to the ext4 maintainers.

While this is correct, what exact kind of failure is this? Can we get
robust against it and not create a corrupt database? I'm fine if we
panic and crash, but are there ways to make sure the db is intact?

Volker

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de

Meet us at Storage Developer Conference (SDC)
Santa Clara, CA USA, September 24th-27th 2018