fusermount: failed to mark mounts private: Invalid argument

670 views
Skip to first unread message

Imre Dávid Kosztka

unread,
May 23, 2012, 7:12:14 AM5/23/12
to tup-...@googlegroups.com
Hi,

Why get I this error? On SLED10, I have no root rights. What Can I do?

fusermount: failed to mark mounts private: Invalid argument
tup error: Unable to unmount the fuse file-system on .tup/mnt (return code = 256). You may have to unmount this manually as root: umount -f .tup/mnt

Mike Shal

unread,
May 24, 2012, 10:07:00 AM5/24/12
to tup-...@googlegroups.com
Any idea what version of fuse SLED 10 comes with? This might show you:

$ rpm -qi fuse

It looks like SLED10 was released a while ago, so perhaps it has an
older version of fuse (I started using fuse-2.8.5 I think). You
shouldn't need root access to run tup unless you want to run processes
in a chroot environment, though I don't know exactly what is causing
this particular error. Are you able to use other fuse-based
filesystems (like sshfs) and unmount them with 'fusermount -u'?

-Mike

Gábor Márton

unread,
Feb 11, 2013, 11:44:07 AM2/11/13
to tup-...@googlegroups.com
Hi Kocka!

Do you have any update on this?

BR,
Gabor

Anatol Pomozov

unread,
Feb 11, 2013, 12:07:09 PM2/11/13
to tup-...@googlegroups.com
Hi

On Wed, May 23, 2012 at 4:12 AM, Imre Dávid Kosztka <kosz...@gmail.com> wrote:
Hi,

Why get I this error? On SLED10, I have no root rights. What Can I do?

fusermount: failed to mark mounts private: Invalid argument

The error comes from this line in fusermount code:

res = mount("", "/", "", MS_PRIVATE | MS_REC, NULL);
        if (res == -1) {
                fprintf(stderr, "%s: failed to mark mounts private: %s\n",
                        progname, strerror(errno));
                return 1;
        }

And my guess that SLED has ancient version of kernel that does not support MS_PRIVATE key in mount() call. Private mounts support was added in kernel version 2.6.15 (released in January 2006)

What kernel do you have? Show us output of

$ uname -r
 

tup error: Unable to unmount the fuse file-system on .tup/mnt (return code = 256). You may have to unmount this manually as root: umount -f .tup/mnt

Gábor Márton

unread,
Feb 12, 2013, 4:15:10 AM2/12/13
to tup-...@googlegroups.com
Hi, 

I am experiencing this error on SLES 11. 
uname -r gives:
2.6.32.45-0.3-xen

Thanks,
Gabor

Gábor Márton

unread,
Feb 12, 2013, 4:18:32 AM2/12/13
to tup-...@googlegroups.com
Update:

I have recognized that this problem is appearing only, when a ClearCase dynamic view is also mounted by cleartool setview command.
When I am not setting any dynamic ClearCase view there is no such problem. Maybe CC also uses fusermount?

BR,
Gabor

Anatol Pomozov

unread,
Feb 12, 2013, 3:55:48 PM2/12/13
to tup-...@googlegroups.com
Hi,

On Tue, Feb 12, 2013 at 1:18 AM, Gábor Márton <marton...@gmail.com> wrote:
Update:

I have recognized that this problem is appearing only, when a ClearCase dynamic view is also mounted by cleartool setview command.
When I am not setting any dynamic ClearCase view there is no such problem. Maybe CC also uses fusermount?

I do not use ClearCase and do not know the answer to your question, but following discussion seems relevant to your question https://groups.google.com/group/tup-users/tree/browse_frm/month/2012-06/4e324070fe23616c?rnum=31&_done=/group/tup-users/browse_frm/month/2012-06?&pli=1
 

--
---
You received this message because you are subscribed to the Google Groups "tup-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tup-users+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Gábor Márton

unread,
Feb 13, 2013, 6:05:50 AM2/13/13
to tup-...@googlegroups.com
Hi Anatol,

Thanks for your answer. 
Though my problem is not solved, I've found a workaround which I would like to share with other ClearCase and TUP users:
I have discovered, that ClearCase uses a specific filesystem which is kinda similar to the fuse: MVFS. The specific problem with fusermount happens only, when a view is set with the cleartool setview command. However a view can be accessed (even checkout is working) without explicitly setting it, through /view/your_view_tag/. So the workaround is to not use the setview command, and access the files in CC through /view/your_view_tag.

BR,
Gabor
Reply all
Reply to author
Forward
0 new messages