-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hi,
one of the problems we often see on the Toolserver is users accidentally using too much disk space (for example, broken tools generating 100GB logfiles). to avoid this happening in the future, we will be bringing back disk quotas over the next week or two. this will work as follows:
* newly created accounts will get 250MB disk quota * users currently using less than 200MB will also get 250MB disk quota * users using more than 200MB will get 1.5x their current usage. (for example, a user currently using 500MB will get 500 * 1.5 = 750MB quota).
this is a 'soft' limit; the 'hard' limit will be 2x the soft limit. you can exceed the soft limit for up to 7 days, which allows people to temporarily use more disk space if necessary. however, you can never exceed the hard limit. if the soft limit is exceeded for more than 7 days, you will be unable to use any more space until your use is brought back under the soft limit.
we recognise that users sometimes need to use more than 250MB of disk space for legitimate reasons. therefore, if you need more quota than you have, you may file a request in JIRA (TS project), specifying how much space you need, and a general description of the purpose (for example, "storing rendered map tiles"). if, based on the description above, you think you will need more disk space than the amount you will be assigned automatically, you should file a request in JIRA now, so your initial limit is set correctly.
while it's always important to monitor your disk space, and avoid using space unnecessarily, there is nothing wrong with needing more space than your current quota allows. please don't feel like you can't run a tool because it would need more disk space. (however, a tool using 200GB disk space is probably excessive.)
you will be informed at login time if your disk usage exceeds your soft or hard quota. you can always check your current usage by running 'quota -v'.
in the past we've had quotas on and off at various times; from now on, it's likely to be permanent.
- river.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
River Tarnell:
to avoid this happening in the future, we will be bringing back disk quotas
... on the /home filesystem. there will be no quotas (for now) on the user-store filesystem
- river.
Pardon the noob question, but how can I tell how much disk space my account is using?
On Mon, Nov 16, 2009 at 7:21 PM, River Tarnell < river@loreley.flyingparchment.org.uk> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
River Tarnell:
to avoid this happening in the future, we will be bringing back disk quotas
... on the /home filesystem. there will be no quotas (for now) on the user-store filesystem
- river.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (HP-UX)
iEYEARECAAYFAksB7JMACgkQIXd7fCuc5vLtkwCeMbOsptCPO0zqX56sCRyxOJon P+EAni8fiMIMWuR7FRho+iS1Qvh5YviJ =IHJS -----END PGP SIGNATURE-----
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
James Hare:
Pardon the noob question, but how can I tell how much disk space my account is using?
$ quota -v
- river.
Hallo,
I am under the top 25 at number 2. The most data in my home are from the Templatetiger. I produce this overview for over 40 languages. After a run of the script I put the data in my home-directory.
http://toolserver.org/~kolossos/templatetiger/
One question: In the last time I play more and more with MySQL. Is there a limit for data in this database for one user? If not, then I will try to change the script, so that this script put this data into the database.
Best regards Stefan (sk)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
"Stefan Kühn":
In the last time I play more and more with MySQL. Is there a limit for data in this database for one user? If not, then I will try to change the script, so that this script put this data into the database.
there is no technological limit (other than total available disk space), but that is not the right way to think about it. it is no cheaper for us to provide the disk space for MySQL than for /home; each GB of storage costs money wherever you put it.
as i explained in the original mail, the disk quota is not intended as a limit on disk use. if you need to use more disk space, you can file a request in JIRA to have your quota increased.
- river.
toolserver-l@lists.wikimedia.org