What is overriding the fstab permissions mounting option?
Clash Royale CLAN TAG#URR8PPP
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
asked Sep 17 '16 at 5:12
Eliptical view
5441622
add a comment |
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
asked Sep 17 '16 at 5:12
Eliptical view
5441622
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 ofmount(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
add a comment |
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
asked Sep 17 '16 at 5:12
Eliptical view
5441622
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
permissions mount fstab options
asked Sep 17 '16 at 5:12
Eliptical view
5441622
asked Sep 17 '16 at 5:12
Eliptical view
5441622
edited Sep 17 '16 at 16:21
asked Sep 17 '16 at 5:12
Eliptical view
5441622
asked Sep 17 '16 at 5:12
Eliptical view
5441622
asked Sep 17 '16 at 5:12
Eliptical view
5441622
5441622
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 ofmount(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
add a comment |
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 ofmount(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
add a comment |
1 Answer
1
active
oldest
votes
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.
answered Sep 17 '16 at 16:20
Eliptical view
5441622
add a comment |
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
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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.
answered Sep 17 '16 at 16:20
Eliptical view
5441622
add a comment |
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.
answered Sep 17 '16 at 16:20
Eliptical view
5441622
add a comment |
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.
answered Sep 17 '16 at 16:20
Eliptical view
5441622
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.
answered Sep 17 '16 at 16:20
Eliptical view
5441622
edited Sep 17 '16 at 16:32
answered Sep 17 '16 at 16:20
Eliptical view
5441622
answered Sep 17 '16 at 16:20
Eliptical view
5441622
answered Sep 17 '16 at 16:20
Eliptical view
5441622
5441622
add a comment |
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
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