Frequently Asked Questions: Difference between revisions

no edit summary
(Marked this version for translation)
No edit summary
Line 53: Line 53:
If you are the owner of the files, you can run the <code>chgrp</code> command to change their group ownership to the appropriate project group. To ask us to change the group owner for several users, contact [[Technical Support|technical support]].
If you are the owner of the files, you can run the <code>chgrp</code> command to change their group ownership to the appropriate project group. To ask us to change the group owner for several users, contact [[Technical Support|technical support]].
You can also use the command <tt>chmod g+s <directory name></tt> to ensure that files created in that directory will inherit the directory's group membership.
You can also use the command <tt>chmod g+s <directory name></tt> to ensure that files created in that directory will inherit the directory's group membership.
=== Another explanation ===
Each file in Linux belongs to a person and a group at the same time.
By default, a file you create belongs to you, user “username", and your group, named the
same “username". That is it is owned by “username:username".
You group is created at the same time your account was created and you are the only user
in that group.
This file ownership is good for your home directory, or the scratch space.
See the "Home" and "Scratch" lines in the output:
<pre>
                              Description                Space          # of files
                      Home (user username)              15G/53G            74k/500k
                  Scratch (user username)          1522G/100T            65k/1000k
                  Project (group username)            34G/2048k            330/2048
              Project (group def-professor)            28k/1000G              9/500k
</pre>
The quota is set for these for a user “username".
The other two lines are set for groups “username" and “def-professor" in Project space.
It is not important what users own the files in that space, but the group the files belong
to determines the quota limit.
You see, that files that are owned by “username" group (your default group) have very small
limit in the project space, only 2MB, and you already have 34 GB of data that is owned by
your group (your files). This is why you cannot write more data there. Because you are
trying to place data there owned by a group that has very little allocation there.
The allocation for the group “def-professor", your professor's group, on the other hand does
not use almost any space and has 1 TB limit. The files that can be put there should have
“username:def-professor" ownership.
Now, depending on how you copy you files, what software you use, that software either will
respect the ownership of the directory and apply the correct group, or it may insist on
retaining the ownership of the source data. In the latter case you have the problem like
you have.
Most probably your original data belongs to “username:username", properly, upon moving it,
it should belong to “username:def-professor", but you software probably insists on keeping
the original ownership and this causes the problem.
If you already have data in your project directory with wrong ownership, you can correct this with
commands:
<pre>
$ cd project/$USER
$ chown -R username:def-professor data_dir
</pre>
This will correct the ownership of the files inside '''data_dir''' directory in your project space.
You can read more about the problem here:
https://docs.computecanada.ca/wiki/Frequently_Asked_Questions#Disk_quota_exceeded_error_on_.2Fproject_filesystems


=== Finding files with the wrong group ownership === <!--T:18-->
=== Finding files with the wrong group ownership === <!--T:18-->
cc_staff
32

edits