Author Topic: Why does LinuxMCE 0710/0810 mount/umount the Storage partition every 6 seconds?  (Read 1091 times)

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Hi,

in the sys log i see that my video partition (/dev/md1 three disks RADI5) is mounten and unmounted all the time. Is that normal ?
I have seen this on 0710 and now also on 0810 alpha.

Syslog :

Code: [Select]
Aug  3 09:10:13 dcerouter kernel: [29179.315607] kjournald starting.  Commit interval 5 seconds
Aug  3 09:10:13 dcerouter kernel: [29179.316853] EXT3-fs: mounted filesystem with ordered data mode.
Aug  3 09:10:14 dcerouter kernel: [29180.306370] kjournald starting.  Commit interval 5 seconds
Aug  3 09:10:14 dcerouter kernel: [29180.307593] EXT3-fs: mounted filesystem with ordered data mode.
Aug  3 09:10:15 dcerouter kernel: [29181.082995] kjournald starting.  Commit interval 5 seconds
Aug  3 09:10:15 dcerouter kernel: [29181.084233] EXT3-fs: mounted filesystem with ordered data mode.
...


From /var/log/pluto/umount-wrapper.log :

Code: [Select]
9937 CALLED TO 'mount /dev/md1 /tmp/tmp.mDrhne9936'
9937 Mon Aug  3 09:07:59 CEST 2009 WaitLock 'mtab' (mount-wrapper)
9937 Mon Aug  3 09:07:59 CEST 2009 WaitLock 'mtab' (mount-wrapper) success
9937 Mon Aug  3 09:07:59 CEST 2009 Unlock 'mtab' (mount-wrapper)
9937 Mon Aug  3 09:07:59 CEST 2009 Unlock 'mtab' (mount-wrapper) success
9937 EXIT WITH STATUS 0


9952 CALLED TO 'umount -lf /tmp/tmp.mDrhne9936'
9952 Mon Aug  3 09:07:59 CEST 2009 WaitLock 'mtab' (umount-wrapper)
9952 Mon Aug  3 09:07:59 CEST 2009 WaitLock 'mtab' (umount-wrapper) success
9952 Mon Aug  3 09:07:59 CEST 2009 Unlock 'mtab' (umount-wrapper)
9952 Mon Aug  3 09:07:59 CEST 2009 Unlock 'mtab' (umount-wrapper) success
9952 EXIT WITH STATUS 0


10374 CALLED TO 'mount /dev/md1 /tmp/tmp.nswPx10372'
10374 Mon Aug  3 09:08:05 CEST 2009 WaitLock 'mtab' (mount-wrapper)
10374 Mon Aug  3 09:08:05 CEST 2009 WaitLock 'mtab' (mount-wrapper) success
10374 Mon Aug  3 09:08:05 CEST 2009 Unlock 'mtab' (mount-wrapper)
10374 Mon Aug  3 09:08:05 CEST 2009 Unlock 'mtab' (mount-wrapper) success
10374 EXIT WITH STATUS 0


10407 CALLED TO 'umount -lf /tmp/tmp.nswPx10372'
10407 Mon Aug  3 09:08:05 CEST 2009 WaitLock 'mtab' (umount-wrapper)
10407 Mon Aug  3 09:08:05 CEST 2009 WaitLock 'mtab' (umount-wrapper) success
10407 Mon Aug  3 09:08:05 CEST 2009 Unlock 'mtab' (umount-wrapper)
10407 Mon Aug  3 09:08:05 CEST 2009 Unlock 'mtab' (umount-wrapper) success
10407 EXIT WITH STATUS 0

Greetings
Viking

pigdog

  • NEEDS to work for LinuxMCE
  • ***
  • Posts: 1008
    • View Profile

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
Hi,

OK, thanks. Don't see the reason though.

Greetings
Viking

merkur2k

  • Addicted
  • *
  • Posts: 513
    • View Profile
yep, I just learned to live with it too. It's just how lmce works, most of it is caused by UpdateMedia since it is always running and looking for stuff to index.

tschak909

  • LinuxMCE God
  • ****
  • Posts: 5501
  • DOES work for LinuxMCE.
    • View Profile
We have an intricate auto-mounter, with a very short timeout, and when updatemedia does its runs, it triggers the automount again.

-Thom

merkur2k

  • Addicted
  • *
  • Posts: 513
    • View Profile
I dont mind the constant mounting/unmounting, the annoying part for me is that it makes the kernel log completely useless because of the filesystem messages that get logged each time. I will try to find out if there is a way to suppress those...

Viking

  • Addicted
  • *
  • Posts: 521
    • View Profile
I dont mind the constant mounting/unmounting, the annoying part for me is that it makes the kernel log completely useless because of the filesystem messages that get logged each time. I will try to find out if there is a way to suppress those...
Same here.

though I noticed on sunday that the server was really busy mounting/umounting. There was around 50 mount processes when I did an "ps ax|grep mount" and "mount" (without any options) took 10-20 sek. to complete.
So sometimes the system seems to get into trouble. I waited several hours, but it did not really get much better so I rebootet the core and it was gone.

Greetings
Viking