Innodb_file_format from antelope to barracuda

Nextcloud version (15.0.6):
Operating system (LXC debian 9):
Apache (Apache 2.4.25):
PHP version ( PHP: 7.3.3-1+0~20190307202245.32+stretch~1.gbp32ebb2)
mariaDB ( 10.1.37-MariaDB-0+deb9u1 - Debian 9.6)

Yesterday I updated nextcloud from 15.0.5 to 15.0.6. Everything was OK.
I only saw one alert.
MySQL is used as database but does not support 4-byte characters. To be able to handle 4-byte characters (like emojis) without issues in filenames or comments for example it is recommended to enable the 4-byte support in MySQL. For further details read the documentation page about this
I followed this tutorial.
All my tables are now barracuda.
±--------------------------------------±------±------------+
| NAME | SPACE | FILE_FORMAT |
±--------------------------------------±------±------------+
| nextcloud/oc_accounts | 325 | Barracuda |
| nextcloud/oc_activity | 326 | Barracuda |
| nextcloud/oc_activity_mq | 327 | Barracuda |
| nextcloud/oc_addressbookchanges | 328 | Barracuda |
| nextcloud/oc_addressbooks | 329 | Barracuda |
| nextcloud/oc_appconfig | 330 | Barracuda |
| nextcloud/oc_authtoken | 331 | Barracuda |
| nextcloud/oc_bruteforce_attempts | 332 | Barracuda |
| nextcloud/oc_calendar_invitations | 333 | Barracuda |
| nextcloud/oc_calendar_resources | 334 | Barracuda |
| nextcloud/oc_calendar_rooms | 335 | Barracuda |
| nextcloud/oc_calendarchanges | 336 | Barracuda |
| nextcloud/oc_calendarobjects | 337 | Barracuda |
| nextcloud/oc_calendarobjects_props | 338 | Barracuda |
| nextcloud/oc_calendars | 339 | Barracuda |
| nextcloud/oc_calendarsubscriptions | 340 | Barracuda |
| nextcloud/oc_cards | 341 | Barracuda |
| nextcloud/oc_cards_properties | 342 | Barracuda |
| nextcloud/oc_comments | 343 | Barracuda |
| nextcloud/oc_comments_read_markers | 344 | Barracuda |
| nextcloud/oc_credentials | 345 | Barracuda |
| nextcloud/oc_dav_shares | 346 | Barracuda |
| nextcloud/oc_directlink | 347 | Barracuda |
| nextcloud/oc_federated_reshares | 348 | Barracuda |
| nextcloud/oc_file_locks | 349 | Barracuda |
| nextcloud/oc_filecache | 350 | Barracuda |
| nextcloud/oc_files_trash | 351 | Barracuda |
| nextcloud/oc_flow_checks | 352 | Barracuda |
| nextcloud/oc_flow_operations | 353 | Barracuda |
| nextcloud/oc_group_admin | 354 | Barracuda |
| nextcloud/oc_group_user | 355 | Barracuda |
| nextcloud/oc_groups | 356 | Barracuda |
| nextcloud/oc_jobs | 357 | Barracuda |
| nextcloud/oc_migrations | 358 | Barracuda |
| nextcloud/oc_mimetypes | 359 | Barracuda |
| nextcloud/oc_mounts | 360 | Barracuda |
| nextcloud/oc_notifications | 361 | Barracuda |
| nextcloud/oc_notifications_pushtokens | 362 | Barracuda |
| nextcloud/oc_oauth2_access_tokens | 363 | Barracuda |
| nextcloud/oc_oauth2_clients | 364 | Barracuda |
| nextcloud/oc_preferences | 365 | Barracuda |
| nextcloud/oc_properties | 366 | Barracuda |
| nextcloud/oc_richdocuments_assets | 367 | Barracuda |
| nextcloud/oc_richdocuments_direct | 368 | Barracuda |
| nextcloud/oc_richdocuments_member | 369 | Barracuda |
| nextcloud/oc_richdocuments_wopi | 370 | Barracuda |
| nextcloud/oc_schedulingobjects | 371 | Barracuda |
| nextcloud/oc_share | 372 | Barracuda |
| nextcloud/oc_share_external | 373 | Barracuda |
| nextcloud/oc_storages | 374 | Barracuda |
| nextcloud/oc_systemtag | 375 | Barracuda |
| nextcloud/oc_systemtag_group | 376 | Barracuda |
| nextcloud/oc_systemtag_object_mapping | 377 | Barracuda |
| nextcloud/oc_trusted_servers | 378 | Barracuda |
| nextcloud/oc_twofactor_backupcodes | 379 | Barracuda |
| nextcloud/oc_twofactor_providers | 380 | Barracuda |
| nextcloud/oc_users | 381 | Barracuda |
| nextcloud/oc_vcategory | 382 | Barracuda |
| nextcloud/oc_vcategory_to_object | 383 | Barracuda |
| nextcloud/oc_whats_new | 384 | Barracuda |
±--------------------------------------±------±------------+

However, do not change it innodb_file_format from Antelope to Barracuda.
MariaDB [(none)]>show variables like “%innodb_file%”;
±-------------------------±----------+
| Variable_name | Value |
±-------------------------±----------+
| innodb_file_format | Antelope |
| innodb_file_format_check | ON |
| innodb_file_format_max | Barracuda |
| innodb_file_per_table | ON |
±-------------------------±----------+

Changing from Antelope to Barracuda
MariaDB [(none)]>SET GLOBAL innodb_file_format = barracuda;
±-------------------------±----------+
| Variable_name | Value |
±-------------------------±----------+
| innodb_file_format | Barracuda |
| innodb_file_format_check | ON |
| innodb_file_format_max | Barracuda |
| innodb_file_per_table | ON |
±-------------------------±----------+

Then restart mariadb
systemctl restart mariadb
And innodb_file_format is still antelope
±-------------------------±----------+
| Variable_name | Value |
±-------------------------±----------+
| innodb_file_format | Antelope |
| innodb_file_format_check | ON |
| innodb_file_format_max | Barracuda |
| innodb_file_per_table | ON |
±-------------------------±----------+

Does anyone have a similar problem?

Have you edited the mysql config and restarted as the guide says ?

[mysqld]
innodb_large_prefix=true
innodb_file_format=barracuda
innodb_file_per_table=1

That should be in the file, and after that restarted.

Yes of corse. After restart mariadb is innodb_file_format Antelope again.
Also, innodb_large_prefix is changed from ON to OFF (after restart).

The changes are not applied when you just sudo mysql
you have to sudo mysql -u root -p
then make changes to nextcloud db