Hello, After a power loss at the model town recently, I discovered the NAS box's database had become corrupted. Fortunately, it was able to recover the lost data with the "REPAIR TABLE" SQL command.
Unfortunately, when I was investigating the cause, I found that the
following mount options are being used for the storage:
* The commit interval is set to 30 seconds instead of the default 5.
* The data mode is set to writeback
* barrier is set to 0, which, from what I understand, can also
compromise data consistency.
My understanding of these issues from what I read here
https://www.kernel.org/doc/html/latest/admin-guide/ext4.html#options is
that this effectively disables journaling, and seriously impacts the
reliability of the storage system (RAID 1). Unfortunately, it is
D-Link's scripts that mount the RAID array, so I doubt that I can change
the options.
After a quick call with Terry, I had the idea of running the "sync"
command regularly as a kind of kludgy workaround, in addition to
automatically repairing the database tables on each start. I'm not
particularly happy with either of these solutions.
Does anyone else have any ideas? I know there are some smart people here
so I figure it's worth asking.
Hamish
signature.asc
Description: OpenPGP digital signature
-- Next meeting: Online, Jitsi, Tuesday, 2020-09-01 20:00 Check to whom you are replying Meetings, mailing list, IRC, ... http://dorset.lug.org.uk New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
