Unable to unmount a BaseSpace mount

349 views
Skip to first unread message

Moiz Bootwalla

unread,
Aug 31, 2015, 11:48:09 AM8/31/15
to basespace-developers
Hi,

I read that in order to refresh any changes made through the Web GUI I need to unmount and remount the BaseSpace mount. I'm trying to unmount my directory but keep getting the following error:

Warning: Max number of open files (`ulimit -n` / `ulimit -Hn`) == 4096 < 16384. Accessing many "Files" directories simultaneously or in quick succession may lead to a series of "Resource temporarily unavailable" system errors.

BaseSpaceFS version: 1.1.632
Launching: fusermount -u BaseSpace_Mount
fusermount: failed to unmount /data/BaseSpace_Mount: Device or resource busy

Is there any way to force the unmount? If not can you point me to more detailed instructions on how to unmount the directory and restart basemount. Kindly help me out.

Thank You,

Moiz

Lilian Janin

unread,
Sep 2, 2015, 1:25:18 AM9/2/15
to basespace-developers
Hi Moiz,

You used the correct way to unmount BaseMount.
But the message "fusermount: failed to unmount /data/BaseSpace_Mount: Device or resource busy"
shows that you still have at least one process using the mounted directory.
It may just be one of your terminals still inside the directory, even if no command is running. You just need to `cd` somewhere else and the unmount will work.

Lilian

Joseph Charalel

unread,
Jan 6, 2017, 1:22:25 PM1/6/17
to basespace-developers
Hi All,

I am also having issues with unmounting, 

basemount --unmount ./Basespace

yields:

fusermount: entry for /home/jcharale/BaseSpace not found in /etc/mtab

--------------------------

Unmount failed. Some processes may still be using one of the sub-directories.


And I cannot mount the directory again either.  I don't have the folder open in any terminals/screen sessions... any ideas?

Thanks so much!
Joe

Lilian Janin

unread,
Jan 6, 2017, 1:25:31 PM1/6/17
to basespace-developers
Hi Joseph,

Can you try just `basemount ./Basespace`?

If the directory is already mounted, it will go through several different unmount strategies (I don't think --unmount goes through all of them, weirdly).

Kind regards,
Lilian

Joseph Charalel

unread,
Jan 6, 2017, 1:33:02 PM1/6/17
to basespace-developers
Thanks for the quick reply Lillian!

Command called:

    basemount BaseSpace

From:

    /home/jcharale


* Soft unmounting of BaseSpace

Launching: fusermount -u BaseSpace

fusermount: entry for /home/jcharale/BaseSpace not found in /etc/mtab

--------------------------

Unmount failed. Some processes may still be using one of the sub-directories.


List of processes (fuser -mv BaseSpace):

Cannot stat BaseSpace: Transport endpoint is not connected

Cannot stat BaseSpace: Transport endpoint is not connected

Cannot stat BaseSpace: Transport endpoint is not connected


Should I lazy-unmount the mount point (the mount point will be available for new mounts, while current processes will be able to finish using the currently opened files)? (Y/n) Y 

Launching: fusermount -uz BaseSpace

fusermount: entry for /home/jcharale/BaseSpace not found in /etc/mtab


** Unmount complete. Your mount point should now be re-useable.


but then if I try basemount BaseSpace again, it repeats the same error.


Thanks again,

Joe

Lilian Janin

unread,
Jan 6, 2017, 1:42:14 PM1/6/17
to basespace-developers
Wow it looks pretty messed up!

Choose a different mount point until the next reboot? (Sorry I don't have a better suggestion...)



On Monday, 31 August 2015 16:48:09 UTC+1, Moiz Bootwalla wrote:

Joseph Charalel

unread,
Jan 6, 2017, 1:46:48 PM1/6/17
to basespace-developers
:( will do, thanks for helping!
Reply all
Reply to author
Forward
0 new messages