Difference: PetalLinux (5 vs. 6)

Revision 601 Dec 2017 - StuartBorthwick1

Line: 1 to 1
 
META TOPICPARENT name="PetalSys"
<--===== START PAGE =====================================-->
Line: 12 to 12
 
<--===== PAGE TEXT ======================================-->
Changed:
<
<

Previous: 1.3 Filesystem and Directories Next: 1.5 SMB Client Access Home: Petal Documentation

>
>
Previous: 1.3 Filesystem and Directories Next: 1.5 SMB Client Access Home: Petal Documentation
 
Changed:
<
<

The PETAL archive is accessible from all University clients via kerberized NFSv4.

>
>
The PETAL archive is accessible from all University clients via kerberized NFSv4.
 
Changed:
<
<

For the Faculty of Environment, after a project directory is created on petal-fs-01 in /export/archive/spectra, the project also has to be added to the NFS automount tables. This is on see-app-01 in /var/yp/ypfiles/see.leeds.ac.uk/auto.petal. Just create a new line along the lines of the existing ones. For some reason, we have followed a convention of changing all uppercase to lowercase in this file - not sure why we did that ! After the Yellow Pages have been rebuild, the access point is:

>
>
For the Faculty of Environment, after a project directory is created on petal-fs-01 in /export/archive/spectra, the project also has to be added to the NFS automount tables. This is on see-app-01 in /var/yp/ypfiles/see.leeds.ac.uk/auto.petal. Just create a new line along the lines of the existing ones. For some reason, we have followed a convention of changing all uppercase to lowercase in this file - not sure why we did that ! After the Yellow Pages have been rebuild, the access point is:
 
Changed:
<
<
/nfs/petal/my_project
>
>
/nfs/petal/my_project
 
Changed:
<
<

Users can then access and use it with normal Linux commands. For example:

>
>
Users can then access and use it with normal Linux commands. For example:
 
Changed:
<
<
cp -aruv ~/data /nfs/petal/my_project
>
>
cp -aruv ~/data /nfs/petal/my_project
 
Changed:
<
<

Users outside of Environment will require the PETAL cache to be set up on a machine which they have access to. Typically, an entry has to be added to local ‘automount’ maps like:

>
>
Users outside of Environment will require the PETAL cache to be set up on a machine which they have access to. Typically, an entry has to be added to local ‘automount’ maps like:
 
Changed:
<
<
petal -fstype=nfs4,sec=krb5,hard,intr petal-fs.leeds.ac.uk:/archive/spectra2/my_project
>
>
petal -fstype=nfs4,sec=krb5,hard,intr petal-fs.leeds.ac.uk:/archive/spectra2/my_project
 
Changed:
<
<

We have found that the system can't deal properly with sparsedata - so users should be advised that options like rsync -S and cp --sparse should not be used - data may get corrupted.

>
>
We have found that the system can't deal properly with sparse data - so users should be advised that options like rsync -S and cp --sparse should not be used - data may get corrupted.
 
Changed:
<
<

Previous: 1.3 Filesystem and Directories Next: 1.5 SMB Client Access Home: Petal Documentation

>
>
Previous: 1.3 Filesystem and Directories Next: 1.5 SMB Client Access Home: Petal Documentation
 
<--===== END CONTENT: ===================================-->
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2014 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.