Différences

Ci-dessous, les différences entre deux révisions de la page.

--- linux:btrfs [08-07-2019 20:43] – [Passer de ext4 à btrfs] edmc73
+++ linux:btrfs [28-04-2021 14:16] (Version actuelle) – edmc73
@@ Ligne 128: / Ligne 128: @@
 Mettre à jour grub
   mount /dev/sda2 /mnt
-  mount /dev/sda1 /mnt/boot
+  mount /dev/sda1 /mnt/boot/efi
   for fs in proc sys dev dev/pts; do mount --bind /$fs /mnt/$fs; done
   chroot /mnt
@@ Ligne 134: / Ligne 134: @@
   update-grub
+La suite peut aider mais pas nécessaire normalement.
@@ Ligne 159: / Ligne 164: @@
+-----------------------
+Si votre grub est coincé au redémarrage
+<code>
+grub>ls #pour lister les partition
+set root=(hd0,gpt2) # faite TAB en cours de frappe montre pas mal d'info sur la partition à choisir)
+linux /vmlinuz root=/dev/sda2 ro
+initrd /initrd.img
+boot
+</code>
+ensuite, pour réparer grub
+  update-grub
+===== Scripts tiers =====
+  # btrfs-list: a wrapper to btrfs-progs to show a nice overview of your btrfs subvolumes and snapshots, a la 'zfs list'
+  #
+  # Check for the latest version at:
+  # https://github.com/speed47/btrfs-list
+  # git clone https://github.com/speed47/btrfs-list.git
+  # or wget https://raw.githubusercontent.com/speed47/btrfs-list/master/btrfs-list -O btrfs-list
+  # or curl -L https://raw.githubusercontent.com/speed47/btrfs-list/master/btrfs-list -o btrfs-list
+===== io disk =====
+-- source: https://kinvolk.io/docs/flatcar-container-linux/latest/setup/debug/btrfs-troubleshooting/
+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/volume that is mounted into the container.
+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 /var/lib/mysql
+The directory /var/lib/mysql is now ready to be used by a Docker container without COW. Let’s break down the command:
+-R indicates that want to recursively change the file attribute +C means we want to set the NOCOW attribute on the file/directory
+To verify, we can run:
+<code>
+$ lsattr /var/lib/
+---------------- /var/lib/portage
+---------------- /var/lib/gentoo
+---------------- /var/lib/iptables
+---------------- /var/lib/ip6tables
+---------------- /var/lib/arpd
+---------------- /var/lib/ipset
+---------------- /var/lib/dbus
+---------------- /var/lib/systemd
+---------------- /var/lib/polkit-1
+---------------- /var/lib/dhcpcd
+---------------- /var/lib/ntp
+---------------- /var/lib/nfs
+---------------- /var/lib/etcd
+---------------- /var/lib/docker
+---------------- /var/lib/update_engine
+---------------C /var/lib/mysql
+</code>

Outils pour utilisateurs

Outils du site

Différences

Outils de la page