View Single Post
Old 11-06-2012, 12:00 AM   #53
EternalCyclist
Member
EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.EternalCyclist for a long time would go to bed early.
 
Posts: 17
Karma: 17948
Join Date: Oct 2012
Device: KT
Quote:
Originally Posted by geekmaster View Post
But I thought we were supposed to avoid using /mnt/base-us/.
Using /mnt/base-us seems to work unless you are accessing userstore from host PC at the same time.

The lock ups might not be caused by loop mounting in general, but by fsp. /etc/fstab includes:
Code:
 fsp#/mnt/base-us  /mnt/us       fuse   
rw,max_write=65536,max_readahead=65536,noatime,exec,nosuid,nodev,nonempty
Quick look at fsp:
Code:
strings /sbin/fsp
says that it is a "filesystem proxy".

Code:
ps  -eo %mem,rss,args | grep fsp
shows
Code:
 0.4  1116 fsp /mnt/base-us /mnt/us -o rw,nosuid,nodev,noatime,max_write=65536,max_readahead=65536,nonempty
fsp uses 0.4% of physical memory, 1116 kB. Not too bad. But maybe it changes dynamically.
EternalCyclist is offline   Reply With Quote