Comments - [ Option innodb_log_file_buffering non prise en compte ]
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
Bonjour et merci pour vos retours. innodb_flush_log_at_trx_commit est = 0 et définit dans mon fichier mariadb.cnf. Micka
À partir du lien, Daniel Black a posté: "On Linux, when the physical block size cannot be determined to be a power of 2 between 64 and 4096 bytes, the file system cache cannot be disabled, and innodb_log_file_buffering=ON cannot be changed."
Merci pour ce retour. Quand je lance la commande sudo xfs_info /dev/md0 : J'ai ce retour qui m'indique que j'ai bien une puissance de 2 : meta-data=/dev/md0 isize=512 agcount=6, agsize=268435455 blks
sectsz=4096 attr=2, projid32bit=1
crc=1 finobt=1, sparse=1, rmapbt=0
reflink=1 bigtime=0
data = bsize=4096 blocks=1465097616, imaxpct=5
sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=521728, version=2
sectsz=4096 sunit=1 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0