William David Edwards via discuss <[email protected]> writes:
> What happened on 2026-04-02: > > - 14:05 CET: application gets `SQLSTATE[42S02] ... Table > 'app_db.users' doesn't exist` (error 1146). User confirms via > phpMyAdmin that the database `app_db` still exists but has no > tables. > - ~14:11 CET: everything works again. Data is intact (!) > > On disk: > > - All 12 .frm and all 12 .ibd files have Birth timestamps clustered in > a window of a few seconds, at `2026-04-02 14:11:30.xxx`. > - Order per table is .frm first, .ibd a few ms later. Example for one > table: > - foo.frm Birth `14:11:30.152` > - foo.ibd Birth `14:11:30.184` > - No #sql-* orphan files anywhere in the datadir. Right, it's hard to know from the information available. But I would say the most likely explanation looks to be something happened to the filesystem from outside of the database server. That would be consistent with the tables becoming invisible (database/table visibility is based on filesystem state IIRC), and with the file timestamps being so close. At least it's a place to look for other ideas: cron jobs, special filesystem / storage system properties, etc. Hope this helps, - Kristian. _______________________________________________ discuss mailing list -- [email protected] To unsubscribe send an email to [email protected]
