University of Reading cookie policy

We use cookies on to improve your experience, monitor site performance and tailor content to you.

Read our cookie policy to find out how to manage your cookie settings.

NDrive migration for NFS users

An overview of the impact of the migration on NFS users and why it is necessary.

Why are we migrating

The current file server has reached it end of life and we have run out of capacity to increase user quotas.

In order to continue providing Home folders to users and to increase the quotas assigned to each user, we have procured and deployed a replacement file server. In order to make use of the new file server we need to migrate everyone's data from the old file server to the new file server.

Current Configuration

The current file server that hosts user's Home folders (N drives) supports sharing a user's Home folder using both SMB and NFS protocols. This allows users to have one Home folder and access it from both protocols.

What's changing and why

Splitting NFS from SMB

As the replacement file server is unable to support the same flexibility with NFS exports as the current file server, we have decided to split SMB Home folders away from NFS Home folders. In effect users will now have TWO Home folders, one for the Windows (SMB) world and one for the Linux (NFS) world. The two folders will be separate and distinct.

As we migrate users to the new file server, we will be duplicating a user's Home folder, one which can be accessed via SMB and the other that can be accessed via NFS. The two folders will start as identical copies but will diverge over time. Linux users can of cause mount their SMB Home folder using mount.cifs and likewise Windows users can mount their NFS Home folder.

For the time being, NFS share will remain on the old file server so the paths will not change. NFS shres will be migrated separately at a later time.

At the moment the server that hosts accesses a folder called public_html in a user's Home folder via NFS.

After the migration the web server will look for the public_html folder in a user's SMB Home folder and permissions will be granted to the web server using NTFS permissions rather than unix. On the plus side, public_html users should no longer have to re-publich each time they create new files ino rder for the webserver to be able to read them. The down side if that sshgate and NFS will no longer provide a route to editing personal web pages.