Aller au contenu
  • 0

Disque dur jamais mis en veille à cause de Samba ?

olrik

Posée par olrik,

 Share

Question

olrik Newbie

olrik

Posté(e)
Posté(e)

Bonjour,

après pas mal d'heures passées à sillonner des pages en anglais et en français, je donne ma langue au chat.

Le matériel :

- un TS-431 reçu hier.

- un disque dur seagate   ST4000VN000 (neuf et faisant partie de la liste de compatibilité).

Pas de problème pour l'installation, le disque est reconnu et l'indicateur de santé indique "bon".

Le souci est qu'il ne se met jamais en veille. Toutes les 10 ou 20 secondes, une sorte de "tic" semble le stimuler pour le faire écrire. Il n'est du coup jamais en veille.

J'ai utilisé la combine du script blkdevMonitor afin de voir de quoi il en retournait et voici ce que j'obtiens :

<7>[ 2058.236962] smbstatus(28732): dirtied inode 139984906 (smbXsrv_session_global.tdb) on dm-0
<7>[ 2058.236996] smbstatus(28732): dirtied inode 139984906 (smbXsrv_session_global.tdb) on dm-0
<7>[ 2058.506512] smbstatus(28733): dirtied inode 139984907 (smbXsrv_tcon_global.tdb) on dm-0
<7>[ 2058.506541] smbstatus(28733): dirtied inode 139984907 (smbXsrv_tcon_global.tdb) on dm-0
<7>[ 2128.577071] smbstatus(29381): dirtied inode 139984906 (smbXsrv_session_global.tdb) on dm-0
<7>[ 2128.577105] smbstatus(29381): dirtied inode 139984906 (smbXsrv_session_global.tdb) on dm-0
<7>[ 2128.849397] smbstatus(29400): dirtied inode 139984907 (smbXsrv_tcon_global.tdb) on dm-0
<7>[ 2128.849427] smbstatus(29400): dirtied inode 139984907 (smbXsrv_tcon_global.tdb) on dm-0
<7>[ 2198.221783] smbstatus(29916): dirtied inode 139984906 (smbXsrv_session_global.tdb) on dm-0
<7>[ 2198.221817] smbstatus(29916): dirtied inode 139984906 (smbXsrv_session_global.tdb) on dm-0
<7>[ 2198.498617] smbstatus(29918): dirtied inode 139984907 (smbXsrv_tcon_global.tdb) on dm-0
<7>[ 2198.498645] smbstatus(29918): dirtied inode 139984907 (smbXsrv_tcon_global.tdb) on dm-0
<7>[ 2268.253741] smbstatus(30455): dirtied inode 139984906 (smbXsrv_session_global.tdb) on dm-0
<7>[ 2268.253775] smbstatus(30455): dirtied inode 139984906 (smbXsrv_session_global.tdb) on dm-0
<7>[ 2268.525478] smbstatus(30457): dirtied inode 139984907 (smbXsrv_tcon_global.tdb) on dm-0
<7>[ 2268.525507] smbstatus(30457): dirtied inode 139984907 (smbXsrv_tcon_global.tdb) on dm-0
<7>[ 1993.982045] jbd2/dm-0-8(1920): WRITE block 7071975296 on dm-0 (8 sectors)
<7>[ 1994.229779] jbd2/dm-0-8(1920): WRITE block 7071975288 on dm-0 (8 sectors)
<7>[ 1994.229913] jbd2/dm-0-8(1920): WRITE block 3854832344 on dm-0 (8 sectors)
<7>[ 1994.229949] jbd2/dm-0-8(1920): WRITE block 3854832352 on dm-0 (8 sectors)
<7>[ 1994.229974] jbd2/dm-0-8(1920): WRITE block 3854832360 on dm-0 (8 sectors)
<7>[ 1994.229993] jbd2/dm-0-8(1920): WRITE block 3854832368 on dm-0 (8 sectors)
<7>[ 1994.230017] jbd2/dm-0-8(1920): WRITE block 3854832376 on dm-0 (8 sectors)
<7>[ 1994.231407] jbd2/dm-0-8(1920): WRITE block 3854832384 on dm-0 (8 sectors)
<7>[ 2028.732022] flush-253:0(2037): WRITE block 0 on dm-0 (8 sectors)
<7>[ 2029.112244] flush-253:0(2037): WRITE block 1688 on dm-0 (8 sectors)
<7>[ 2029.112292] flush-253:0(2037): WRITE block 4479516928 on dm-0 (8 sectors)
<7>[ 2029.112319] flush-253:0(2037): WRITE block 7071596552 on dm-0 (8 sectors)
<7>[ 2064.022012] jbd2/dm-0-8(1920): WRITE block 7071919736 on dm-0 (8 sectors)
<7>[ 2064.265375] jbd2/dm-0-8(1920): WRITE block 7071919728 on dm-0 (8 sectors)
<7>[ 2064.265506] jbd2/dm-0-8(1920): WRITE block 3854832392 on dm-0 (8 sectors)
<7>[ 2064.265536] jbd2/dm-0-8(1920): WRITE block 3854832400 on dm-0 (8 sectors)
<7>[ 2064.265559] jbd2/dm-0-8(1920): WRITE block 3854832408 on dm-0 (8 sectors)
<7>[ 2064.265578] jbd2/dm-0-8(1920): WRITE block 3854832416 on dm-0 (8 sectors)
<7>[ 2064.265599] jbd2/dm-0-8(1920): WRITE block 3854832424 on dm-0 (8 sectors)
<7>[ 2064.266824] jbd2/dm-0-8(1920): WRITE block 3854832432 on dm-0 (8 sectors)
<7>[ 2098.242009] flush-253:0(2037): WRITE block 7071596552 on dm-0 (8 sectors)
<7>[ 2098.606194] flush-253:0(2037): WRITE block 0 on dm-0 (8 sectors)
<7>[ 2098.606245] flush-253:0(2037): WRITE block 1688 on dm-0 (8 sectors)
<7>[ 2098.606273] flush-253:0(2037): WRITE block 4479516928 on dm-0 (8 sectors)
<7>[ 2134.022012] jbd2/dm-0-8(1920): WRITE block 7071975328 on dm-0 (8 sectors)
<7>[ 2134.072918] jbd2/dm-0-8(1920): WRITE block 7071975320 on dm-0 (8 sectors)
<7>[ 2134.073044] jbd2/dm-0-8(1920): WRITE block 3854832440 on dm-0 (8 sectors)
<7>[ 2134.073072] jbd2/dm-0-8(1920): WRITE block 3854832448 on dm-0 (8 sectors)
<7>[ 2134.073094] jbd2/dm-0-8(1920): WRITE block 3854832456 on dm-0 (8 sectors)
<7>[ 2134.073115] jbd2/dm-0-8(1920): WRITE block 3854832464 on dm-0 (8 sectors)
<7>[ 2134.073133] jbd2/dm-0-8(1920): WRITE block 3854832472 on dm-0 (8 sectors)
<7>[ 2134.074427] jbd2/dm-0-8(1920): WRITE block 3854832480 on dm-0 (8 sectors)
<7>[ 2168.582009] flush-253:0(2037): WRITE block 4479516928 on dm-0 (8 sectors)
<7>[ 2168.636923] flush-253:0(2037): WRITE block 7071596552 on dm-0 (8 sectors)
<7>[ 2168.636977] flush-253:0(2037): WRITE block 0 on dm-0 (8 sectors)
<7>[ 2168.637006] flush-253:0(2037): WRITE block 1688 on dm-0 (8 sectors)
<7>[ 2203.982014] jbd2/dm-0-8(1920): WRITE block 7071919784 on dm-0 (8 sectors)
<7>[ 2204.362151] jbd2/dm-0-8(1920): WRITE block 7071919776 on dm-0 (8 sectors)
<7>[ 2204.362289] jbd2/dm-0-8(1920): WRITE block 3854832488 on dm-0 (8 sectors)
<7>[ 2204.362321] jbd2/dm-0-8(1920): WRITE block 3854832496 on dm-0 (8 sectors)
<7>[ 2204.362341] jbd2/dm-0-8(1920): WRITE block 3854832504 on dm-0 (8 sectors)
<7>[ 2204.362360] jbd2/dm-0-8(1920): WRITE block 3854832512 on dm-0 (8 sectors)
<7>[ 2204.362380] jbd2/dm-0-8(1920): WRITE block 3854832520 on dm-0 (8 sectors)
<7>[ 2204.363622] jbd2/dm-0-8(1920): WRITE block 3854832528 on dm-0 (8 sectors)
<7>[ 2238.222022] flush-253:0(2037): WRITE block 1688 on dm-0 (8 sectors)
<7>[ 2238.602555] flush-253:0(2037): WRITE block 4479516928 on dm-0 (8 sectors)
<7>[ 2238.602608] flush-253:0(2037): WRITE block 7071596552 on dm-0 (8 sectors)
<7>[ 2238.602649] flush-253:0(2037): WRITE block 0 on dm-0 (8 sectors)
<7>[ 2273.982015] jbd2/dm-0-8(1920): WRITE block 7071975392 on dm-0 (8 sectors)
<7>[ 2274.227280] jbd2/dm-0-8(1920): WRITE block 7071975384 on dm-0 (8 sectors)
<7>[ 2274.227411] jbd2/dm-0-8(1920): WRITE block 3854832536 on dm-0 (8 sectors)
<7>[ 2274.227441] jbd2/dm-0-8(1920): WRITE block 3854832544 on dm-0 (8 sectors)
<7>[ 2274.227460] jbd2/dm-0-8(1920): WRITE block 3854832552 on dm-0 (8 sectors)
<7>[ 2274.227478] jbd2/dm-0-8(1920): WRITE block 3854832560 on dm-0 (8 sectors)
<7>[ 2274.227500] jbd2/dm-0-8(1920): WRITE block 3854832568 on dm-0 (8 sectors)
<7>[ 2274.228901] jbd2/dm-0-8(1920): WRITE block 3854832576 on dm-0 (8 sectors)
<7>[ 2308.262017] flush-253:0(2037): WRITE block 0 on dm-0 (8 sectors)
<7>[ 2308.507675] flush-253:0(2037): WRITE block 1688 on dm-0 (8 sectors)
<7>[ 2308.507723] flush-253:0(2037): WRITE block 4479516928 on dm-0 (8 sectors)
<7>[ 2308.507751] flush-253:0(2037): WRITE block 7071596552 on dm-0 (8 sectors)
<7>[ 2117.255312] touch(29223): dirtied inode 6617 (volumeStatus.conf) on md9
<7>[ 2122.982052] kjournald(533): WRITE block 549512 on md9 (8 sectors)
<7>[ 2122.982103] md9_raid1(523): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 2123.014325] md9_raid1(523): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 2123.034457] kjournald(533): WRITE block 549520 on md9 (8 sectors)
<7>[ 2123.034938] kjournald(533): WRITE block 549528 on md9 (8 sectors)
<7>[ 2123.261989] md9_raid1(523): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 2123.315546] md9_raid1(523): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 2157.262000] flush-9:9(952): WRITE block 787528 on md9 (8 sectors)
<7>[ 2157.262049] md9_raid1(523): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 2157.297475] md9_raid1(523): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 2157.521992] md9_raid1(523): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 2157.568363] md9_raid1(523): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 1993.982143] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 1994.432016] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2028.732091] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2029.321984] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2064.022082] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2064.471993] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2098.242079] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2098.811993] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2117.231770] lvs(29219): READ block 0 on md1 (8 sectors)
<7>[ 2134.022081] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2134.281978] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2155.341766] vgdisplay(29568): READ block 0 on md1 (8 sectors)
<7>[ 2155.469305] vgdisplay(29572): READ block 0 on md1 (8 sectors)
<7>[ 2168.582078] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2168.841977] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2203.982088] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2204.572018] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2238.222092] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2238.812029] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2273.982088] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2274.431980] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2308.262087] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2308.711985] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 1993.982143] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 1994.432016] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2028.732091] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2029.321984] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2064.022082] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2064.471993] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2098.242079] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2098.811993] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2122.982103] md9_raid1(523): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 2123.014325] md9_raid1(523): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 2123.261989] md9_raid1(523): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 2123.315546] md9_raid1(523): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 2134.022081] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2134.281978] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2157.262049] md9_raid1(523): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 2157.297475] md9_raid1(523): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 2157.521992] md9_raid1(523): WRITE block 1060216 on sda1 (1 sectors)
<7>[ 2157.568363] md9_raid1(523): WRITE block 1060232 on sda1 (1 sectors)
<7>[ 2168.582078] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2168.841977] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2203.982088] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2204.572018] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2238.222092] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2238.812029] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2273.982088] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2274.431980] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2308.262087] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
<7>[ 2308.711985] md1_raid1(1768): WRITE block 7794127504 on sda3 (1 sectors)
 

Si j'ai bien compris certains commentaires, le souci viendrait des dirtied inodes. En l'occurence smbXsrv_session_global.tdb et volumeStatus.conf. 

Pour le premier, j'ai compris qu'il s'agissait de Samba, que j'ai désactivé dans l'onglet "Bonjour" de "découverte de service". J'ai redémarré le NAS mais le problème perdure avec ce smbXsrv_session_global.tdb qui continue d'apparaître.

J'ai pensé à un souci de disque dur mais je ne sais pas, je l'ai installé à un boitier relié en USP à mon PC et tout a l'air normal. Pas ce "tic" qui relance tout le temps le disque.

Bref, si quelqu'un a une idée précise du souci, je suis preneur car je pense avoir exploré toutes les solutions que mes faibles connaissances en NAS me permettent.

 

 

Lien vers le commentaire
Partager sur d’autres sites

2 réponses à cette question

Messages recommandés

  • 0
FranckB Newbie

FranckB

Posté(e)
Posté(e)

je ne pense pas qu'il s'agit d'un problème de disque dur...

La mise en veille est un problème récurrent selon les versions de QTS. En effet par expérience depuis 6ans, la mise en veille des DD est aléatoire selon la version de QTS. Depuis QTS 4.2 pas de mise en veille de mes disques... j'ai laissé tombé depuis longtemps !

 

Lien vers le commentaire
Partager sur d’autres sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Invité
Répondre à cette question…

×   Vous avez collé du contenu avec mise en forme.   Supprimer la mise en forme

  Seulement 75 émoticônes maximum sont autorisées.

×   Votre lien a été automatiquement intégré.   Afficher plutôt comme un lien

×   Votre contenu précédent a été rétabli.   Vider l’éditeur

×   Vous ne pouvez pas directement coller des images. Envoyez-les depuis votre ordinateur ou insérez-les depuis une URL.

Chargement
×
 Share
Aller à la liste des questions
×
×
  • Créer...