Post Reply 
MinimServer & HDD Sleep
17-04-2014, 16:33
Post: #5
RE: MinimServer & HDD Sleep
Hi Simon, the log file isn't being appended to (just assumed it was). If MinimServer is switched off as an app - disks go to sleep.

If MinimServer is running - just prior to the 5 min mark I then see:

============= 15/100 test, Thu Apr 17 16:23:19 BST 2014 ===============
<7>[198372.805457] smbd(21011): dirtied inode 1435 (smbXsrv_open_global.tdb) on md13
<7>[198372.805469] smbd(21011): dirtied inode 1435 (smbXsrv_open_global.tdb) on md13
<7>[198372.806268] smbd(21011): dirtied inode 1432 (locking.tdb) on md13
<7>[198372.806272] smbd(21011): dirtied inode 1432 (locking.tdb) on md13
<7>[198372.805457] smbd(21011): dirtied inode 1435 (smbXsrv_open_global.tdb) on md13
<7>[198372.805469] smbd(21011): dirtied inode 1435 (smbXsrv_open_global.tdb) on md13
<7>[198372.806268] smbd(21011): dirtied inode 1432 (locking.tdb) on md13
<7>[198372.806272] smbd(21011): dirtied inode 1432 (locking.tdb) on md13

or

<7>[198683.174209] setcfg(30734): dirtied inode 6930 (vg2.log) on md9
<7>[198683.174487] setcfg(30734): dirtied inode 6895 (vg2.log.bak) on md9
<7>[198683.177471] sed(30741): dirtied inode 6928 (vg2.logBIyp1j) on md9
<7>[198683.181313] setcfg(30749): dirtied inode 6895 (vg2.log.bak) on md9
<4>[198683.158135] lvdisplay(30693): READ block 0 on md9 (8 sectors)
<4>[198683.168377] lvs(30709): READ block 0 on md9 (8 sectors)
<4>[198683.158515] lvdisplay(30693): READ block 0 on md13 (8 sectors)
<4>[198683.168772] lvs(30709): READ block 0 on md13 (8 sectors)

============= 16/100 test, Thu Apr 17 16:24:54 BST 2014 ===============
<4>[198378.724501] kjournald(3809): WRITE block 282816 on md13 (8 sectors)
<4>[198378.725005] md13_raid1(366): WRITE block 7797308216 on sdg (8 sectors)
....

Then nothing happens - and just before disks are due to sleep (5 mins) - the above repeats:


<4>[198505.218966] md13_raid1(366): WRITE block 7797308208 on sdh (8 sectors)
<4>[198505.235114] md13_raid1(366): WRITE block 7796248680 on sdh (8 sectors)
<4>[198505.437023] md13_raid1(366): WRITE block 7797308216 on sdh (8 sectors)
<4>[198505.452094] md13_raid1(366): WRITE block 7797308208 on sdh (8 sectors)

As if it's continually writing to somewhere. The ohNet is set to Default for logs. The MinimServer log is Info.

It's odd - in that it started happening around the time you release a whole lot of updates for MinimServer 0.8.x - and the disks have never slept since! And, if I turn off Minim, it reverts to normal.
Something has to be keeping it awake and it must be from Minim (or linked modules - JRE?).
Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
MinimServer & HDD Sleep - MikeSpragg - 16-04-2014, 17:39
RE: MinimServer & HDD Sleep - simoncn - 16-04-2014, 18:13
RE: MinimServer & HDD Sleep - simoncn - 17-04-2014, 15:39
RE: MinimServer & HDD Sleep - MikeSpragg - 17-04-2014 16:33
RE: MinimServer & HDD Sleep - simoncn - 17-04-2014, 17:12
RE: MinimServer & HDD Sleep - simoncn - 17-04-2014, 17:40
RE: MinimServer & HDD Sleep - simoncn - 17-04-2014, 18:44
RE: MinimServer & HDD Sleep - simoncn - 17-04-2014, 19:07
RE: MinimServer & HDD Sleep - simoncn - 17-04-2014, 19:47
RE: MinimServer & HDD Sleep - simoncn - 17-04-2014, 20:58
RE: MinimServer & HDD Sleep - simoncn - 18-04-2014, 12:59
RE: MinimServer & HDD Sleep - simoncn - 18-04-2014, 20:35
RE: MinimServer & HDD Sleep - simoncn - 18-04-2014, 21:40

Forum Jump:


User(s) browsing this thread: 1 Guest(s)