Ci-dessous, les différences entre deux révisions de la page.
Les deux révisions précédentes Révision précédente | |||
linux:btrfs [21-04-2021 14:45] edmc73 [Passer de ext4 à btrfs] |
linux:btrfs [28-04-2021 16:16] (Version actuelle) edmc73 |
||
---|---|---|---|
Ligne 189: | Ligne 189: | ||
# or curl -L https:// | # or curl -L https:// | ||
+ | ===== io disk ===== | ||
+ | |||
+ | -- source: https:// | ||
+ | |||
+ | Disable copy-on-write | ||
+ | |||
+ | Copy-On-write isn’t ideal for workloads that create or modify many small files, such as databases. Without disabling COW, you can heavily fragment the file system as explained above. | ||
+ | |||
+ | The best strategy for successfully running a database in a container is to disable COW on directory/ | ||
+ | |||
+ | The COW setting is stored as a file attribute and is modified with a utility called chattr. To disable COW for a MySQL container’s volume, run: | ||
+ | |||
+ | chattr -R +C / | ||
+ | | ||
+ | The directory / | ||
+ | |||
+ | -R indicates that want to recursively change the file attribute +C means we want to set the NOCOW attribute on the file/ | ||
+ | |||
+ | To verify, we can run: | ||
+ | |||
+ | < | ||
+ | $ lsattr /var/lib/ | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------- / | ||
+ | ---------------C / | ||
+ | </ |