I am unable to transfer any files onto the second drive of my core, as it keeps getting unmounted. I ran the following command:
while [ true ] ; do echo "`date` : `df | grep sdb`" ; sleep 5 ; done
and get this output:
Sat Apr 11 19:27:32 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /mnt/device/28
Sat Apr 11 19:27:38 BST 2009 :
Sat Apr 11 19:27:43 BST 2009 :
Sat Apr 11 19:27:48 BST 2009 :
Sat Apr 11 19:27:53 BST 2009 :
Sat Apr 11 19:27:58 BST 2009 :
Sat Apr 11 19:28:03 BST 2009 :
Sat Apr 11 19:28:08 BST 2009 :
Sat Apr 11 19:28:13 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /tmp/tmp.KryNc31477
Sat Apr 11 19:28:18 BST 2009 :
Sat Apr 11 19:28:23 BST 2009 :
Sat Apr 11 19:28:28 BST 2009 :
Sat Apr 11 19:28:33 BST 2009 :
Sat Apr 11 19:28:38 BST 2009 :
Sat Apr 11 19:28:43 BST 2009 :
Sat Apr 11 19:28:48 BST 2009 :
Sat Apr 11 19:28:53 BST 2009 :
Sat Apr 11 19:28:58 BST 2009 :
Sat Apr 11 19:29:03 BST 2009 :
Sat Apr 11 19:29:08 BST 2009 :
Sat Apr 11 19:29:13 BST 2009 :
Sat Apr 11 19:29:18 BST 2009 :
Sat Apr 11 19:29:23 BST 2009 :
Sat Apr 11 19:29:28 BST 2009 :
Sat Apr 11 19:29:33 BST 2009 :
Sat Apr 11 19:29:38 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /mnt/device/28
Sat Apr 11 19:29:43 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /mnt/device/28
Sat Apr 11 19:29:48 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /mnt/device/28
Sat Apr 11 19:29:53 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /mnt/device/28
Sat Apr 11 19:29:58 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /mnt/device/28
Sat Apr 11 19:30:03 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /mnt/device/28
Sat Apr 11 19:30:08 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /mnt/device/28
Sat Apr 11 19:30:13 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /mnt/device/28
Sat Apr 11 19:30:18 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /mnt/device/28
/dev/sdb1 961432072 204628 912389444 1% /tmp/tmp.NqdDbI1699
Sat Apr 11 19:30:23 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /mnt/device/28
Sat Apr 11 19:30:28 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /mnt/device/28
Sat Apr 11 19:30:33 BST 2009 : /dev/sdb1 961432072 204628 912389444 1% /mnt/device/28
Sat Apr 11 19:30:38 BST 2009 :
Is anyone aware of this? If not I will submit to Trac.
Regards,
Chris
This is normal.
It is caused by the automounter not detecting any open files or disk accesses to the mount, so it unmounts.
-Thom
Why is it required? It seems that most of the time it is unmounted, so I am unable to start copying files to it.
Chris
This is required so that the disk can be swapped out, if it is external.
While it is not perfect, typically a read to the directory where the disk is symlinked is sufficient to bring it online.
-Thom
Quote from: chrisbirkinshaw on April 13, 2009, 05:33:08 PM
Why is it required? It seems that most of the time it is unmounted, so I am unable to start copying files to it.
Chris
I agree this is a pain. We tend to create a detached screen session and ls into one of the subdirectories via the drives symlink. This keeps the drive mounted and available. Its a bit of a hack...but works ok as a temporary measure until we can come up with a more 'intelligent' automounter script.
Andrew
ack, its a pita. I'd vote for a longer timeout.
and while we are at it, a change from smbfs to nfs would be great.. any volunteers?
br, hari
I have found a problem where samba isn't following symlinks into my external drive. Have you seen this? Works ok on the box itself.