NerdCulture

0 posts0 participants0 posts today

NigelI have a database table with several rows showing whitespace in the Path column and -1 in the Parent columnIt's the oc_filecache table in my Nextcloud MariaDB and NC log throws up warning the index is corruptedBut it's part of InnoDB and the usual MariaDB repair tools won't workI can access the table manually with the Webmin module and easily delete whatever I like but therein lies the danger!Making assumption that those rows are the problem but... help?<a href="https://musicians.today/tags/mariadb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mariadb</a> <a href="https://musicians.today/tags/innodb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#innodb</a> <a href="https://musicians.today/tags/sql" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sql</a> <a href="https://musicians.today/tags/database" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#database</a>

NigelNeed help... MariaDB is giving me Warning and Error messages in the log about InnoDB corruption in my Nextcloud table. Tried backups but no joy. Seems I need to rebuild... Before I get stuck into new territory for me, anyone an expert in MariaDB/Mysql and the InnoDB tables? Poor, but just about legible when zoomed, screenshot. This seems the only error, repeated over. <a href="https://musicians.today/tags/mariadb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mariadb</a> <a href="https://musicians.today/tags/mysql" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mysql</a> <a href="https://musicians.today/tags/innodb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#innodb</a> <a href="https://musicians.today/tags/database" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#database</a> <a href="https://musicians.today/tags/NextCloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NextCloud</a> <a href="https://musicians.today/tags/askfedi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#askfedi</a>

SchenklWas genau ist eigentlich <a href="https://chaos.social/tags/AIO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AIO</a> im Context von <a href="https://chaos.social/tags/InnoDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InnoDB</a> und <a href="https://chaos.social/tags/MariaDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MariaDB</a>?Also wenn ich das jetzt ausschalte, vermute ich mal wird die DB langsamer, aber vielleicht auch ein bisschen stabiler, was Schreibvorgänge auf die Disk angeht?

Remkus de Vries2/ 🛠️ Switch to a Modern Storage EngineConsider switching your database storage engine to InnoDB if you haven't already. InnoDB supports row-level locking and transactions, making it ideal for high-concurrency environments typical in busy online stores. <a href="https://social.devries.frl/tags/DatabaseOptimization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DatabaseOptimization</a> <a href="https://social.devries.frl/tags/InnoDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InnoDB</a>

Howard Chu @ SymasThe reliability studies are particularly damning, they show <a href="https://mastodon.social/tags/MySQL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MySQL</a>/#MariaDB's <a href="https://mastodon.social/tags/InnoDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InnoDB</a> loses the entire database after a system crash on every workload tested. <a href="https://lists.openldap.org/hyperkitty/list/openldap-devel@openldap.org/message/K5XMXFFGHQOWKB6G2UGHWHW5WVH7X77C/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://lists.openldap.org/hyperkitty/list/openldap-devel@openldap.org/message/K5XMXFFGHQOWKB6G2UGHWHW5WVH7X77C/</a>(Note that they claimed to have found 1 flaw in <a href="https://mastodon.social/tags/LMDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LMDB</a> that occurred in 0.05% of their test runs, but it was actually a bug in the ext3 fs driver. One that had been fixed in Linux 2+ years before they began their research. In fact LMDB's reliability is flawless.) LMDB is the only DB that is perfectly crash-proof.

Howard Chu @ SymasSo while he's doing extra administrative work (fine tuning to search for safe memory allocation parameters) he's getting orders of magnitude slower performance using <a href="https://mastodon.social/tags/InnoDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InnoDB</a> than <a href="https://mastodon.social/tags/LMDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LMDB</a>, and none of the crash reliability that he claims to value. <a href="http://www.lmdb.tech/bench/memcache/" rel="nofollow noopener noreferrer" translate="no" target="_blank">http://www.lmdb.tech/bench/memcache/</a>

Marcus "MajorLinux" SummersSo, an update:I was able to get the site back up without losing any data!Apparently, something happened with <a href="https://toot.majorshouse.com/tags/InnoDB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InnoDB</a>, so I had to manually "massage" some files to get it working again.I need to figure out a way to back up the data.Any tips on how to do that via <a href="https://toot.majorshouse.com/tags/Docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Docker</a>?

saiki 🚒💨:manjaro: :debian:<a href="https://fulda.social/@lars" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@lars</a> <a href="https://support.plesk.com/hc/en-us/articles/213939865-How-to-fix-InnoDB-corruption-cases-for-the-MySQL-databases-on-Plesk-for-Linux-#:~:text=InnoDB%20corruption.,allocating%20InnoDB%20databases%20on%20it" rel="nofollow noopener noreferrer" target="_blank">https://support.plesk.com/hc/en-us/articles/213939865-How-to-fix-InnoDB-corruption-cases-for-the-MySQL-databases-on-Plesk-for-Linux-#:~:text=InnoDB%20corruption.,allocating%20InnoDB%20databases%20on%20it</a>.Ist zwar für was anderes beschrieben, aber vom Grundprinzip her: database in recovery Modus hauen. <a href="https://social.tchncs.de/tags/Backup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Backup</a> ziehen. Datenbank löschen und neu anlegen. Danach Backup rückspielen.<a href="https://social.tchncs.de/tags/mysql" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mysql</a> <a href="https://social.tchncs.de/tags/innodb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#innodb</a> <a href="https://social.tchncs.de/tags/recovery" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#recovery</a>

Recent searches

Search options

Administered by:

Server stats:

#InnoDB