Over 50GB - Revision history

Jurjen at 06:59, 1 July 2018

2018-07-01T06:59:51Z

← Older revision		Revision as of 06:59, 1 July 2018
Line 8:		Line 8:

	3. The next morning (bar some malfunction) when you log in, your home directory is now on another server. Moreover, the directories marked for <code>/project</code> are no longer where they were. They are now in <code>/project/whatever_name_we_agreed_on</code>.		3. The next morning (bar some malfunction) when you log in, your home directory is now on another server. Moreover, the directories marked for <code>/project</code> are no longer where they were. They are now in <code>/project/whatever_name_we_agreed_on</code>.


	Please note that		Please note that
	ls /project		ls /project
	will not show anything. Only when you actually access a directory under <code>/project</code> will it be mounted and shown.		will not show anything. Only when you actually access a directory under <code>/project</code> will it be mounted and shown.

			If <code>ls /project/yourdir</code> still doesn't show anything, the most likely cause is that your computer hasn't run for at least 20 minutes since we created the the /project/yourdir share. Your computer must be told about it (once) by the Puppet agent, which runs every 20 minutes.

	===Danger!===		===Danger!===

Jurjen at 11:45, 28 June 2018

2018-06-28T11:45:28Z

← Older revision		Revision as of 11:45, 28 June 2018
Line 5:		Line 5:
	But even when that is done, you won't be moved unless you log off from all LWPs.		But even when that is done, you won't be moved unless you log off from all LWPs.

	2. So at some point in time, you log off entirely, from all LWPs, when you leave from work in the evening.		2. So at some point in time, you log off entirely, from all LWPs, when you leave from work in the evening. You also turn off your computer, lest some process fails to stop and keeps the NFS server thinking you're logged in.

	3. The next morning (bar some malfunction) when you log in, your home directory is now on another server. Moreover, the directories marked for <code>/project</code> are no longer where they were. They are now in <code>/project/whatever_name_we_agreed_on</code>.		3. The next morning (bar some malfunction) when you log in, your home directory is now on another server. Moreover, the directories marked for <code>/project</code> are no longer where they were. They are now in <code>/project/whatever_name_we_agreed_on</code>.

Jurjen at 10:07, 24 June 2018

2018-06-24T10:07:42Z

← Older revision		Revision as of 10:07, 24 June 2018
Line 19:		Line 19:
	While <code>~/moved-dirs</code> still exist, the copy under <code>/project</code> is just that: a copy. It may lag behind, or be incomplete, or be currently written by our scripts, or all of these. By accessing it, you now have modifications in both copies. That constitutes a mess, and since we warned you, it is you who gets to sort it out.		While <code>~/moved-dirs</code> still exist, the copy under <code>/project</code> is just that: a copy. It may lag behind, or be incomplete, or be currently written by our scripts, or all of these. By accessing it, you now have modifications in both copies. That constitutes a mess, and since we warned you, it is you who gets to sort it out.

	Once <code>~/moved-dirs</code> have vanished, your account has been migrated, and the new path under /project is the only one. Only then is is fine to use it.		Once <code>~/moved-dirs</code> have vanished, your account has been migrated, and the new path under /project is the only one. Only then is it fine to use it.

	===Handy symlinks===		===Handy symlinks===

Jurjen at 10:06, 24 June 2018

2018-06-24T10:06:30Z

← Older revision		Revision as of 10:06, 24 June 2018
Line 7:		Line 7:
	2. So at some point in time, you log off entirely, from all LWPs, when you leave from work in the evening.		2. So at some point in time, you log off entirely, from all LWPs, when you leave from work in the evening.

	3. The next morning (bar some malfunction) when you log in, your home directory is now on another server. Moreover, the directories marked for /project are no longer where they were. They are now in /project/whatever_name_we_agreed_on.		3. The next morning (bar some malfunction) when you log in, your home directory is now on another server. Moreover, the directories marked for <code>/project</code> are no longer where they were. They are now in <code>/project/whatever_name_we_agreed_on</code>.


	Please note that		Please note that
	ls /project		ls /project
	will not show anything. Only when you actually access a directory under /project will it be mounted and shown.		will not show anything. Only when you actually access a directory under <code>/project</code> will it be mounted and shown.

			===Danger!===

			<em>Do not access</em> <code>/project/whatever_name_we_agreed_on/moved-dirs</code> until <code>~/moved-dirs</code> have vanished from your home directory.
			While <code>~/moved-dirs</code> still exist, the copy under <code>/project</code> is just that: a copy. It may lag behind, or be incomplete, or be currently written by our scripts, or all of these. By accessing it, you now have modifications in both copies. That constitutes a mess, and since we warned you, it is you who gets to sort it out.

			Once <code>~/moved-dirs</code> have vanished, your account has been migrated, and the new path under /project is the only one. Only then is is fine to use it.

			===Handy symlinks===

			Once you have been migrated (and not sooner, see the danger above), you could create symlinks from the old location to the new one:
			ln -sT /project/whatever_name_we_agreed_on/somedir ~/somedir
			There are programs that will treat a symlink differently from an ordinary file or directory, but most will keep working as if nothing had happened.

Jurjen at 12:11, 19 June 2018

2018-06-19T12:11:19Z

← Older revision		Revision as of 12:11, 19 June 2018
Line 10:		Line 10:


	Please note that ls /project will not show anything. Only when you actually access a directory under /project will it be mounted and shown.		Please note that
			ls /project
			will not show anything. Only when you actually access a directory under /project will it be mounted and shown.

Jurjen at 12:10, 19 June 2018

2018-06-19T12:10:35Z

← Older revision		Revision as of 12:10, 19 June 2018
Line 1:		Line 1:
	So we have contacted you, and ~~you are reading this~~.		So we have contacted you, and we have agreed on what to move where. Here's what will happen now.

	~~Your account is so big~~, ~~the~~ data ~~doesn't fit in your quota on the new server~~. ~~How to proceed?~~		1. Once you've told us what to move and where to move it, our servers will start copying data over.

	~~1. Decide what to move elsewhere.~~		But even when that is done, you won't be moved unless you log off from all LWPs.
	~~For your (and our) convenience~~, ~~we have created the file $HOME/migration/du. It lists the sizes of your subdirectories.~~
	~~We have also created $HOME/migration/proposed~~. ~~It looks like this:~~

	~~79828 /research~~		2. So at some point in time, you log off entirely, from all LWPs, when you leave from work in the evening.
	~~32987 /rawdata~~
	~~------ cut here - dirs below add up to less than 49000MB -------~~
	~~9159 /edu~~
	~~7428 /MyBackups~~
	~~4113 /~~.~~thunderbird~~
	~~3228 /educonf18~~

	~~That's just a suggestion~~. ~~Please feel free to select different~~ directories ~~than we did~~. ~~But do tell us what to move~~.		3. The next morning (bar some malfunction) when you log in, your home directory is now on another server. Moreover, the directories marked for /project are no longer where they were. They are now in /project/whatever_name_we_agreed_on.

	~~2. Decide where to move it. Please see [[Project_Directories]].~~

	~~3. Once you've told us what to move and where to move it, our servers will start copying data over.~~		Please note that ls /project will not show anything. Only when you actually access a directory under /project will it be mounted and shown.
	~~4. Once the data is copied, we mark your account for migration.~~
	~~5. At a moment when you are logged off (from all LWPs, not just your own), your account will be migrated.~~

	~~6. The next time you log in, your home directory will not contain the project directories any more. They will be under /project/whatever_name_we_agreed_on.~~

	Please ~~not~~ that ls /project will not show anything. Only when you actually access a directory under /project will it be mounted and shown.

	~~When you are migrated, not only will your home directory server be on another server, some data will now be under /project~~

Jurjen: Created page with "So we have contacted you, and you are reading this. Your account is so big, the data doesn't fit in your quota on the new server. How to proceed? 1. Decide what to move else..."

2018-06-19T12:03:54Z

Created page with "So we have contacted you, and you are reading this. Your account is so big, the data doesn't fit in your quota on the new server. How to proceed? 1. Decide what to move else..."

New page

So we have contacted you, and you are reading this.

Your account is so big, the data doesn't fit in your quota on the new server. How to proceed?

1. Decide what to move elsewhere.
For your (and our) convenience, we have created the file $HOME/migration/du. It lists the sizes of your subdirectories.
We have also created $HOME/migration/proposed. It looks like this:

79828 /research
32987 /rawdata
------ cut here - dirs below add up to less than 49000MB -------
9159 /edu
7428 /MyBackups
4113 /.thunderbird
3228 /educonf18

That's just a suggestion. Please feel free to select different directories than we did. But do tell us what to move.

2. Decide where to move it. Please see [[Project_Directories]].

3. Once you've told us what to move and where to move it, our servers will start copying data over.
4. Once the data is copied, we mark your account for migration.
5. At a moment when you are logged off (from all LWPs, not just your own), your account will be migrated.

6. The next time you log in, your home directory will not contain the project directories any more. They will be under /project/whatever_name_we_agreed_on.

Please not that ls /project will not show anything. Only when you actually access a directory under /project will it be mounted and shown.

When you are migrated, not only will your home directory server be on another server, some data will now be under /project