What is overriding the fstab permissions mounting option? Announcing the arrival of Valued...

Searching extreme points of polyhedron

Keep at all times, the minus sign above aligned with minus sign below

Twin's vs. Twins'

3D Masyu - A Die

One-one communication

Why is there so little support for joining EFTA in the British parliament?

calculator's angle answer for trig ratios that can work in more than 1 quadrant on the unit circle

Any stored/leased 737s that could substitute for grounded MAXs?

My mentor says to set image to Fine instead of RAW — how is this different from JPG?

What does 丫 mean? 丫是什么意思?

Does the main washing effect of soap come from foam?

Flight departed from the gate 5 min before scheduled departure time. Refund options

How could a hydrazine and N2O4 cloud (or it's reactants) show up in weather radar?

Is the time—manner—place ordering of adverbials an oversimplification?

As a dual citizen, my US passport will expire one day after traveling to the US. Will this work?

Is the Mordenkainen's Sword spell underpowered?

Centre cell vertically in tabularx

First paper to introduce the "principal-agent problem"

How to resize main filesystem

Noise in Eigenvalues plot

Did any compiler fully use 80-bit floating point?

Why do C and C++ allow the expression (int) + 4*5;

What was the last profitable war?

Are there any irrational/transcendental numbers for which the distribution of decimal digits is not uniform?



What is overriding the fstab permissions mounting option?



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionNTFS mount using fstab is forced to nosuid,nodevPartition not mounting from fstabError mounting drive with fstabWhat does the noload option do in fstab?Unable to change permissions of file system rootDo you need to specify the “defaults” option in fstab?Can't mount disksfstab creates directory without execute permissionsProper way to set the umask for SFTP transactions?How to properly mount other partitions (NTFS) on my Fedora FSH?Mounting using alternate fstab file





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







2















fstab:



LABEL="Shared" /home/howard/Shared/ ntfs permissions,rw,nosuid,nodev,relatime,uid=howard,gid=howard,allow_other,noatime,fmask=033,dmask=022 0 2


Mount with:



mount LABEL="Shared"


mount reports:




/dev/sda3 on /home/howard/Shared type fuseblk (rw,nosuid,nodev,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)




Note "permissions" option was not honored, and instead "default_permissions" appears. (Also blksize=4096 is being added without my request.) Why does the "permissions" option get changed to "default_permissions"?



I've tried both ntfs and ntfs-3g mount types. They both return with a "fuseblk" mount type.



The permissions option allows each file's owner, group, and ugo_rwx permissions to be set independently. With default_permissions you can only set these one time for all files in the filesystem, and you can't individual set each file's user, group and permissions.



Debian 8.5, Cinnamon 2.2.16, Linux Kernel 3.16.0-4-amd64










share|improve this question
















bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Answer: no, there is not a 2nd place which provides mounting information. This is almost certainly an issue with ntfs-3g specifically. Can you please clarify whether the first invocation of mount (using fstab) is performed with root privileges / sudo or not. (This isn't as stupid as it sounds because it is specifically possible for ntfs-3g to be setuid-root).

    – sourcejedi
    Sep 17 '16 at 14:35


















2















fstab:



LABEL="Shared" /home/howard/Shared/ ntfs permissions,rw,nosuid,nodev,relatime,uid=howard,gid=howard,allow_other,noatime,fmask=033,dmask=022 0 2


Mount with:



mount LABEL="Shared"


mount reports:




/dev/sda3 on /home/howard/Shared type fuseblk (rw,nosuid,nodev,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)




Note "permissions" option was not honored, and instead "default_permissions" appears. (Also blksize=4096 is being added without my request.) Why does the "permissions" option get changed to "default_permissions"?



I've tried both ntfs and ntfs-3g mount types. They both return with a "fuseblk" mount type.



The permissions option allows each file's owner, group, and ugo_rwx permissions to be set independently. With default_permissions you can only set these one time for all files in the filesystem, and you can't individual set each file's user, group and permissions.



Debian 8.5, Cinnamon 2.2.16, Linux Kernel 3.16.0-4-amd64










share|improve this question
















bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Answer: no, there is not a 2nd place which provides mounting information. This is almost certainly an issue with ntfs-3g specifically. Can you please clarify whether the first invocation of mount (using fstab) is performed with root privileges / sudo or not. (This isn't as stupid as it sounds because it is specifically possible for ntfs-3g to be setuid-root).

    – sourcejedi
    Sep 17 '16 at 14:35














2












2








2








fstab:



LABEL="Shared" /home/howard/Shared/ ntfs permissions,rw,nosuid,nodev,relatime,uid=howard,gid=howard,allow_other,noatime,fmask=033,dmask=022 0 2


Mount with:



mount LABEL="Shared"


mount reports:




/dev/sda3 on /home/howard/Shared type fuseblk (rw,nosuid,nodev,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)




Note "permissions" option was not honored, and instead "default_permissions" appears. (Also blksize=4096 is being added without my request.) Why does the "permissions" option get changed to "default_permissions"?



I've tried both ntfs and ntfs-3g mount types. They both return with a "fuseblk" mount type.



The permissions option allows each file's owner, group, and ugo_rwx permissions to be set independently. With default_permissions you can only set these one time for all files in the filesystem, and you can't individual set each file's user, group and permissions.



Debian 8.5, Cinnamon 2.2.16, Linux Kernel 3.16.0-4-amd64










share|improve this question
















fstab:



LABEL="Shared" /home/howard/Shared/ ntfs permissions,rw,nosuid,nodev,relatime,uid=howard,gid=howard,allow_other,noatime,fmask=033,dmask=022 0 2


Mount with:



mount LABEL="Shared"


mount reports:




/dev/sda3 on /home/howard/Shared type fuseblk (rw,nosuid,nodev,noatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096)




Note "permissions" option was not honored, and instead "default_permissions" appears. (Also blksize=4096 is being added without my request.) Why does the "permissions" option get changed to "default_permissions"?



I've tried both ntfs and ntfs-3g mount types. They both return with a "fuseblk" mount type.



The permissions option allows each file's owner, group, and ugo_rwx permissions to be set independently. With default_permissions you can only set these one time for all files in the filesystem, and you can't individual set each file's user, group and permissions.



Debian 8.5, Cinnamon 2.2.16, Linux Kernel 3.16.0-4-amd64







permissions mount fstab options






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 17 '16 at 16:21







Elliptical view

















asked Sep 17 '16 at 5:12









Elliptical viewElliptical view

6331623




6331623





bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Answer: no, there is not a 2nd place which provides mounting information. This is almost certainly an issue with ntfs-3g specifically. Can you please clarify whether the first invocation of mount (using fstab) is performed with root privileges / sudo or not. (This isn't as stupid as it sounds because it is specifically possible for ntfs-3g to be setuid-root).

    – sourcejedi
    Sep 17 '16 at 14:35



















  • Answer: no, there is not a 2nd place which provides mounting information. This is almost certainly an issue with ntfs-3g specifically. Can you please clarify whether the first invocation of mount (using fstab) is performed with root privileges / sudo or not. (This isn't as stupid as it sounds because it is specifically possible for ntfs-3g to be setuid-root).

    – sourcejedi
    Sep 17 '16 at 14:35

















Answer: no, there is not a 2nd place which provides mounting information. This is almost certainly an issue with ntfs-3g specifically. Can you please clarify whether the first invocation of mount (using fstab) is performed with root privileges / sudo or not. (This isn't as stupid as it sounds because it is specifically possible for ntfs-3g to be setuid-root).

– sourcejedi
Sep 17 '16 at 14:35





Answer: no, there is not a 2nd place which provides mounting information. This is almost certainly an issue with ntfs-3g specifically. Can you please clarify whether the first invocation of mount (using fstab) is performed with root privileges / sudo or not. (This isn't as stupid as it sounds because it is specifically possible for ntfs-3g to be setuid-root).

– sourcejedi
Sep 17 '16 at 14:35










1 Answer
1






active

oldest

votes


















0














The permissions option is ignored and automatically changed to default_permissions whenever any of the following options is also included with it:



uid, gid, umask, dmask, or fmask



To help fix this you can use user_id and group_id in place of uid and gid.



But you must not use umask, dmask or fmask with permissions.



You'll know it's working when you get the following status from mount:




Using default user mapping






Note that initially all files are owned by root. You might want to change them recursively to be owned by you.






share|improve this answer


























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f310470%2fwhat-is-overriding-the-fstab-permissions-mounting-option%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    The permissions option is ignored and automatically changed to default_permissions whenever any of the following options is also included with it:



    uid, gid, umask, dmask, or fmask



    To help fix this you can use user_id and group_id in place of uid and gid.



    But you must not use umask, dmask or fmask with permissions.



    You'll know it's working when you get the following status from mount:




    Using default user mapping






    Note that initially all files are owned by root. You might want to change them recursively to be owned by you.






    share|improve this answer






























      0














      The permissions option is ignored and automatically changed to default_permissions whenever any of the following options is also included with it:



      uid, gid, umask, dmask, or fmask



      To help fix this you can use user_id and group_id in place of uid and gid.



      But you must not use umask, dmask or fmask with permissions.



      You'll know it's working when you get the following status from mount:




      Using default user mapping






      Note that initially all files are owned by root. You might want to change them recursively to be owned by you.






      share|improve this answer




























        0












        0








        0







        The permissions option is ignored and automatically changed to default_permissions whenever any of the following options is also included with it:



        uid, gid, umask, dmask, or fmask



        To help fix this you can use user_id and group_id in place of uid and gid.



        But you must not use umask, dmask or fmask with permissions.



        You'll know it's working when you get the following status from mount:




        Using default user mapping






        Note that initially all files are owned by root. You might want to change them recursively to be owned by you.






        share|improve this answer















        The permissions option is ignored and automatically changed to default_permissions whenever any of the following options is also included with it:



        uid, gid, umask, dmask, or fmask



        To help fix this you can use user_id and group_id in place of uid and gid.



        But you must not use umask, dmask or fmask with permissions.



        You'll know it's working when you get the following status from mount:




        Using default user mapping






        Note that initially all files are owned by root. You might want to change them recursively to be owned by you.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Sep 17 '16 at 16:32

























        answered Sep 17 '16 at 16:20









        Elliptical viewElliptical view

        6331623




        6331623






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f310470%2fwhat-is-overriding-the-fstab-permissions-mounting-option%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

            Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

            Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...