summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
6bfd39a)
Apparently, it's possible for 'fusermount -u' to return before a NTFS-3g-based
filesystem has actually unmounted, therefore causing a subsequent mount to the
same location to fail if it happens quickly enough. Using a lazy unmount should
fix this I think...
- if ! fusermount -u $1; then
+ if ! fusermount -z -u $1; then
error "Failed to unmount \"$1\""
fi
error "Failed to unmount \"$1\""
fi