Bonjour à tous, tous les jours dans ma boite mail je reçois une dizaine d'alerte Netdata (logiciel de monitoring) me disant que le serveur utilisait 100% de ces capacités cpu, mémoire et disque pendant environs 10 minutes. Ce soir je regardais un film sur mon serveur Plex et à 2:03, ça a couper et j'ai commencer à recevoir les mails. Je me suis donc intéresser au problème sans pouvoir le résoudre.

Un aperçu du monitoring sur la ram :

Même l'agent Netdata freeze. Bref, j'ai éplucher les logs et je crois que justement ça vient de Plex :

J'ai l'impression qu'il essaie de scanner un dossier récursif ou quelque chose dont il n'a pas accès. Le problème c'est que j'ai désactiver le paramètre qui fait que Plex scan la librairie de façon periodique, seul le paramètre qui détecte la présence d'un nouveau fichier est coché. Autre problème, j'ai bien vérifier ma librairie et aucun dossier récursif ni aucun fichier inaccessible en lecture par Plex.

Un dernier truc, j'ai lancer un scan forcé de la bibliothèque depuis l'application Plex et le serveur n'a pas freeze du tout.

Quelqu'un aurait une idée ?

J'ai lancer une opération de réparation de mauvais secteurs avec :

fsck -cfvr /dev/sdb2

avec le résultat

fsck de util-linux 2.36.1
e2fsck 1.46.2 (28-Feb-2021)

Checking for bad blocks (read-only test): done
/dev/sdb2: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Inode 49414146 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49414157 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49414241 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49414245 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49414249 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49414255 extent tree (at level 1) could be narrower.  Optimize<y>? yes
Inode 49414268 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49414311 extent tree (at level 1) could be narrower.  Optimize<y>? yes
Inode 49414345 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49414349 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49414351 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyyInode 49414354 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyyInode 49414623 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49415244 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyInode 49416502 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49416505 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yyyInode 49425440 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49425472 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyInode 49428440 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yyInode 49428614 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49428622 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49428678 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yyInode 49428684 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49428706 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49428722 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49428729 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yInode 49429364 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yyInode 49429375 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyyInode 49429385 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyInode 49429405 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49429437 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49429452 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49429461 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49429474 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49429493 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yInode 49429496 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429500 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yyyyInode 49429537 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49429562 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49429580 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429631 extent tree (at level 1) could be narrower.  Optimize<y>? yes
Inode 49429636 extent tree (at level 1) could be narrower.  Optimize<y>? yes
Inode 49429821 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429825 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429833 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429834 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429837 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429844 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429850 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429863 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429880 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429898 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429901 extent tree (at level 1) could be narrower.  Optimize<y>? yes
Inode 49429904 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429906 extent tree (at level 1) could be narrower.  Optimize<y>? yes
Inode 49429918 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yyInode 49429953 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49429956 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyInode 49429959 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49429962 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyyInode 49429965 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429968 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 49429971 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yyInode 49429975 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyyInode 49429981 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49429986 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yInode 49429995 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyyyInode 49430000 extent tree (at level 2) could be narrower.  Optimize<y>? yes
Inode 49430006 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yyyyyyyyyInode 49430010 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyInode 49430014 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyyyInode 49430022 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyyyyyyyyyyyyInode 49430024 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyyInode 49545337 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyInode 49547286 extent tree (at level 1) could be narrower.  Optimize<y>? yes
Inode 49547347 extent tree (at level 1) could be narrower.  Optimize<y>? yes
Inode 49547350 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yyInode 49547352 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yInode 49547355 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyyyyInode 51118082 extent tree (at level 1) could be narrower.  Optimize<y>? yes
yyyInode 51249156 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyInode 56229912 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yyyyyyyyyyInode 65142997 extent tree (at level 2) could be narrower.  Optimize<y>? yes
yInode 65143794 extent tree (at level 2) could be narrower.  Optimize<y>? yes

Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
yyyyyyyyyMultiply-claimed block(s) in inode 22413318: 90266439
yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyPass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1D: Reconciling multiply-claimed blocks
(There are 1 inodes containing multiply-claimed blocks.)

File /Music/Europe/The Final Countdown/Europe - The Final Countdown (The Best Of) Disc 1/01. The Final Countdown.flac (inode #22413318, mod time Mon Dec 31 07:12:13 2018)
  has 1 multiply-claimed block(s), shared with 1 file(s):
        <The bad blocks inode> (inode #1, mod time Mon Jan  9 02:30:16 2023)
Clone multiply-claimed blocks<y>? yes
Error reading block 90266439 (Erreur d'entrée/sortie).  Ignore error<y>? yes
Force rewrite<y>? yes

Il n'a pas réussis à réparer le fichier de musique alors j'ai supprimé le dossier Europe entier directement (de toute faon l'album est pas top).

Malheuresement j'ai du kill le process qui était bloqué alors j'éspère qu'il n'y avait rien d'autre.

EDIT :

Le problème semble résolu après la manip

-
Edité par nicolasdemailly7 10 janvier 2023 à 4:31:55