a. Exécutez le script :
Ce script peut prendre des heures sur les volumes de stockage qui contiennent des données.
b. Au fur et à mesure de l'exécution du script, vérifiez le résultat et répondez aux invites.
Si nécessaire, vous pouvez utiliser le
contenu du fichier journal du script (/var/local/log/sn-remount-volumes.log) .
Le fichier journal contient des informations plus détaillées que la sortie de la ligne de
commande.
root@SG:~ # sn-remount-volumes
The configured LDR noid is 12632740
====== Device /dev/sdb ======
Mount and unmount device /dev/sdb and checking file system
consistency:
The device is consistent.
Check rangedb structure on device /dev/sdb:
Mount device /dev/sdb to /tmp/sdb-654321 with rangedb mount options
This device has all rangedb directories.
Found LDR node id 12632740, volume number 0 in the volID file
Attempting to remount /dev/sdb
Device /dev/sdb remounted successfully
====== Device /dev/sdc ======
Mount and unmount device /dev/sdc and checking file system
consistency:
Error: File system consistency check retry failed on device /dev/sdc.
You can see the diagnosis information in the /var/local/log/sn-
remount-volumes.log.
This volume could be new or damaged. If you run sn-recovery-
postinstall.sh, this volume and any data on this volume will be
deleted. If you only had two copies of object data, you will
temporarily have only a single copy.
StorageGRID Webscale will attempt to restore data redundancy by
making additional replicated copies or EC fragments, according to the
rules in the active ILM policy.
Do not continue to the next step if you believe that the data
remaining on this volume cannot be rebuilt from elsewhere in the grid
(for example, if your ILM policy uses a rule that makes only one copy
or if volumes have failed on multiple nodes). Instead, contact
support to determine how to recover your data.
====== Device /dev/sdd ======
2184
sn-remount-volumes
commande permettant de contrôler le
tail -f