Ubuntu root can't give any permissions?
Information about my Ubuntu:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial
I have a problem. I can't give any permissions nor change them as a root (sudo su, sudo -i etc). What should I do? How do I find the cause of this? How to fix it?
sudo nano test.sh
Output: Error writing lock file ./.test.sh.swp: Permission denied
Giving an user account its own permissions:
sudo chown -R student121:student121 /home/opilane121/
Output: Tons of Operation not permitted texts
Answer to comments:
1) NFS4 is read-write only
2) Output of mount | grep home:
mount | grep home
10.16.122.2:/data/users/students on /home type nfs4 (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,po rt=0,timeo=14,retrans=2,sec=sys,clientaddr=10.16.122.146,local_lock=none,addr= 10.16.122.2)
permissions root
asked Feb 4 at 11:07
Kristen UngurKristen Ungur
284
add a comment |
Information about my Ubuntu:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial
I have a problem. I can't give any permissions nor change them as a root (sudo su, sudo -i etc). What should I do? How do I find the cause of this? How to fix it?
sudo nano test.sh
Output: Error writing lock file ./.test.sh.swp: Permission denied
Giving an user account its own permissions:
sudo chown -R student121:student121 /home/opilane121/
Output: Tons of Operation not permitted texts
Answer to comments:
1) NFS4 is read-write only
2) Output of mount | grep home:
mount | grep home
10.16.122.2:/data/users/students on /home type nfs4 (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,po rt=0,timeo=14,retrans=2,sec=sys,clientaddr=10.16.122.146,local_lock=none,addr= 10.16.122.2)
permissions root
asked Feb 4 at 11:07
Kristen UngurKristen Ungur
284
1
I don't know your issue, but are you trying to change details on a read-only device/partition? Is it mounted read-write? or read-only? (has the file-system got errors that need fixing before you can mount it read-write?)
– guiverc
Feb 4 at 11:22
1
Please edit your post and include the output ofmount | grep /home
– vidarlo
Feb 4 at 11:45
Hi there! I updated the post. Answered to your questions and included the output of that command. Please, take a look at it, sir/ma'am.
– Kristen Ungur
Feb 4 at 11:50
1
The fact that you mount the NFS as r/w doesn't mean that the server gives you full rights on it (especially NFS4...)
– xenoid
Feb 4 at 12:21
Hmm. What should I do then? Where should I start doing things? :( I'm clueless right now. :/
– Kristen Ungur
Feb 4 at 12:22
add a comment |
Information about my Ubuntu:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial
I have a problem. I can't give any permissions nor change them as a root (sudo su, sudo -i etc). What should I do? How do I find the cause of this? How to fix it?
sudo nano test.sh
Output: Error writing lock file ./.test.sh.swp: Permission denied
Giving an user account its own permissions:
sudo chown -R student121:student121 /home/opilane121/
Output: Tons of Operation not permitted texts
Answer to comments:
1) NFS4 is read-write only
2) Output of mount | grep home:
mount | grep home
10.16.122.2:/data/users/students on /home type nfs4 (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,po rt=0,timeo=14,retrans=2,sec=sys,clientaddr=10.16.122.146,local_lock=none,addr= 10.16.122.2)
permissions root
asked Feb 4 at 11:07
Kristen UngurKristen Ungur
284
Information about my Ubuntu:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.5 LTS
Release: 16.04
Codename: xenial
I have a problem. I can't give any permissions nor change them as a root (sudo su, sudo -i etc). What should I do? How do I find the cause of this? How to fix it?
sudo nano test.sh
Output: Error writing lock file ./.test.sh.swp: Permission denied
Giving an user account its own permissions:
sudo chown -R student121:student121 /home/opilane121/
Output: Tons of Operation not permitted texts
Answer to comments:
1) NFS4 is read-write only
2) Output of mount | grep home:
mount | grep home
10.16.122.2:/data/users/students on /home type nfs4 (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,po rt=0,timeo=14,retrans=2,sec=sys,clientaddr=10.16.122.146,local_lock=none,addr= 10.16.122.2)
permissions root
permissions root
asked Feb 4 at 11:07
Kristen UngurKristen Ungur
284
asked Feb 4 at 11:07
Kristen UngurKristen Ungur
284
edited Feb 4 at 12:07
Kristen Ungur
asked Feb 4 at 11:07
Kristen UngurKristen Ungur
284
asked Feb 4 at 11:07
Kristen UngurKristen Ungur
284
asked Feb 4 at 11:07
Kristen UngurKristen Ungur
284
284
1
I don't know your issue, but are you trying to change details on a read-only device/partition? Is it mounted read-write? or read-only? (has the file-system got errors that need fixing before you can mount it read-write?)
– guiverc
Feb 4 at 11:22
1
Please edit your post and include the output ofmount | grep /home
– vidarlo
Feb 4 at 11:45
Hi there! I updated the post. Answered to your questions and included the output of that command. Please, take a look at it, sir/ma'am.
– Kristen Ungur
Feb 4 at 11:50
1
The fact that you mount the NFS as r/w doesn't mean that the server gives you full rights on it (especially NFS4...)
– xenoid
Feb 4 at 12:21
Hmm. What should I do then? Where should I start doing things? :( I'm clueless right now. :/
– Kristen Ungur
Feb 4 at 12:22
add a comment |
1
I don't know your issue, but are you trying to change details on a read-only device/partition? Is it mounted read-write? or read-only? (has the file-system got errors that need fixing before you can mount it read-write?)
– guiverc
Feb 4 at 11:22
1
Please edit your post and include the output ofmount | grep /home
– vidarlo
Feb 4 at 11:45
Hi there! I updated the post. Answered to your questions and included the output of that command. Please, take a look at it, sir/ma'am.
– Kristen Ungur
Feb 4 at 11:50
1
The fact that you mount the NFS as r/w doesn't mean that the server gives you full rights on it (especially NFS4...)
– xenoid
Feb 4 at 12:21
Hmm. What should I do then? Where should I start doing things? :( I'm clueless right now. :/
– Kristen Ungur
Feb 4 at 12:22
1
1
I don't know your issue, but are you trying to change details on a read-only device/partition? Is it mounted read-write? or read-only? (has the file-system got errors that need fixing before you can mount it read-write?)
– guiverc
Feb 4 at 11:22
I don't know your issue, but are you trying to change details on a read-only device/partition? Is it mounted read-write? or read-only? (has the file-system got errors that need fixing before you can mount it read-write?)
– guiverc
Feb 4 at 11:22
1
1
Please edit your post and include the output of
mount | grep /home– vidarlo
Feb 4 at 11:45
Please edit your post and include the output of
mount | grep /home– vidarlo
Feb 4 at 11:45
Hi there! I updated the post. Answered to your questions and included the output of that command. Please, take a look at it, sir/ma'am.
– Kristen Ungur
Feb 4 at 11:50
Hi there! I updated the post. Answered to your questions and included the output of that command. Please, take a look at it, sir/ma'am.
– Kristen Ungur
Feb 4 at 11:50
1
1
The fact that you mount the NFS as r/w doesn't mean that the server gives you full rights on it (especially NFS4...)
– xenoid
Feb 4 at 12:21
The fact that you mount the NFS as r/w doesn't mean that the server gives you full rights on it (especially NFS4...)
– xenoid
Feb 4 at 12:21
Hmm. What should I do then? Where should I start doing things? :( I'm clueless right now. :/
– Kristen Ungur
Feb 4 at 12:22
Hmm. What should I do then? Where should I start doing things? :( I'm clueless right now. :/
– Kristen Ungur
Feb 4 at 12:22
add a comment |
1 Answer
1
active
oldest
votes
The NFS-server is probably running with root_squash:
Very often, it is not desirable that the root user on a client machine is also treated as root when accessing files on the NFS server. To this end, uid 0 is normally mapped to a different id: the so-called anonymous or nobody uid. This mode of operation (called 'root squashing') is the default, and can be turned off with no_root_squash.
It basically maps root to a different user with least privileges. This is the default setting on NFS.
Talk with you server administrator, or if you are the server administrator, add option no_root_squash to the /etc/exports on the server.
answered Feb 4 at 12:57
vidarlovidarlo
10.7k52748
Thank you! It worked :)
– Kristen Ungur
Feb 5 at 13:51
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f1115500%2fubuntu-root-cant-give-any-permissions%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 NFS-server is probably running with root_squash:
Very often, it is not desirable that the root user on a client machine is also treated as root when accessing files on the NFS server. To this end, uid 0 is normally mapped to a different id: the so-called anonymous or nobody uid. This mode of operation (called 'root squashing') is the default, and can be turned off with no_root_squash.
It basically maps root to a different user with least privileges. This is the default setting on NFS.
Talk with you server administrator, or if you are the server administrator, add option no_root_squash to the /etc/exports on the server.
answered Feb 4 at 12:57
vidarlovidarlo
10.7k52748
Thank you! It worked :)
– Kristen Ungur
Feb 5 at 13:51
add a comment |
The NFS-server is probably running with root_squash:
Very often, it is not desirable that the root user on a client machine is also treated as root when accessing files on the NFS server. To this end, uid 0 is normally mapped to a different id: the so-called anonymous or nobody uid. This mode of operation (called 'root squashing') is the default, and can be turned off with no_root_squash.
It basically maps root to a different user with least privileges. This is the default setting on NFS.
Talk with you server administrator, or if you are the server administrator, add option no_root_squash to the /etc/exports on the server.
answered Feb 4 at 12:57
vidarlovidarlo
10.7k52748
Thank you! It worked :)
– Kristen Ungur
Feb 5 at 13:51
add a comment |
The NFS-server is probably running with root_squash:
Very often, it is not desirable that the root user on a client machine is also treated as root when accessing files on the NFS server. To this end, uid 0 is normally mapped to a different id: the so-called anonymous or nobody uid. This mode of operation (called 'root squashing') is the default, and can be turned off with no_root_squash.
It basically maps root to a different user with least privileges. This is the default setting on NFS.
Talk with you server administrator, or if you are the server administrator, add option no_root_squash to the /etc/exports on the server.
answered Feb 4 at 12:57
vidarlovidarlo
10.7k52748
The NFS-server is probably running with root_squash:
Very often, it is not desirable that the root user on a client machine is also treated as root when accessing files on the NFS server. To this end, uid 0 is normally mapped to a different id: the so-called anonymous or nobody uid. This mode of operation (called 'root squashing') is the default, and can be turned off with no_root_squash.
It basically maps root to a different user with least privileges. This is the default setting on NFS.
Talk with you server administrator, or if you are the server administrator, add option no_root_squash to the /etc/exports on the server.
answered Feb 4 at 12:57
vidarlovidarlo
10.7k52748
answered Feb 4 at 12:57
vidarlovidarlo
10.7k52748
answered Feb 4 at 12:57
vidarlovidarlo
10.7k52748
answered Feb 4 at 12:57
vidarlovidarlo
10.7k52748
10.7k52748
Thank you! It worked :)
– Kristen Ungur
Feb 5 at 13:51
add a comment |
Thank you! It worked :)
– Kristen Ungur
Feb 5 at 13:51
Thank you! It worked :)
– Kristen Ungur
Feb 5 at 13:51
Thank you! It worked :)
– Kristen Ungur
Feb 5 at 13:51
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1115500%2fubuntu-root-cant-give-any-permissions%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
1
I don't know your issue, but are you trying to change details on a read-only device/partition? Is it mounted read-write? or read-only? (has the file-system got errors that need fixing before you can mount it read-write?)
– guiverc
Feb 4 at 11:22
1
Please edit your post and include the output of
mount | grep /home– vidarlo
Feb 4 at 11:45
Hi there! I updated the post. Answered to your questions and included the output of that command. Please, take a look at it, sir/ma'am.
– Kristen Ungur
Feb 4 at 11:50
1
The fact that you mount the NFS as r/w doesn't mean that the server gives you full rights on it (especially NFS4...)
– xenoid
Feb 4 at 12:21
Hmm. What should I do then? Where should I start doing things? :( I'm clueless right now. :/
– Kristen Ungur
Feb 4 at 12:22