Difference: PetalLinux (3 vs. 4)

Revision 413 Oct 2017 - StuartBorthwick1

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

The PETAL archive is accessible from all University clients via kerberized NFSv4. For the School of Earth and Environment (SEE), the access point is:

>
>

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

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:

  /nfs/petal/my_project
Changed:
<
<

Users outside of the School of Earth and 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 can then access and use it with normal Linux commands. For example:

 
Changed:
<
<
petal -fstype=nfs4,sec=krb5,hard,intr petal-fs.leeds.ac.uk:/archive/spectra2/my_project
>
>
cp -aruv ~/data /nfs/petal/my_project
 
Added:
>
>

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:

petal -fstype=nfs4,sec=krb5,hard,intr petal-fs.leeds.ac.uk:/archive/spectra2/my_project

 
Changed:
<
<

On the PETAL server, the normal archive root point is /export/archive/spectra2. When a user requests storage on the system, a directory with the research project name needs to be created in this subdirectory. Users can then access and use it with normal Linux commands. For example:

>
>

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.

 
Deleted:
<
<
cd /nfs/petal/my_project # this will automount the archive directory under the client /nfs folder
cp -aruv ~/data /nfs/petal/my_project # data will be copied from the data folder to the archive storage allocation
 
Added:
>
>

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

 
<--===== END CONTENT: ===================================-->
Changed:
<
<
<--===== START FOOTER ====================================-->

<--===== WEB LINKS ========================================-->

Useful Links

<--===== START PAGE =====================================-->

<--===== BANNER IMAGE =========================================-->

<--===== CONTENT: =========-->

<--===== PAGE TITLE ============================================-->

<--===== PAGE TEXT ============================================-->

<--===== END CONTENT: =========-->

<--===== END PAGE ============================================-->

<--===== END PAGE =======================================-->

<--===== END FOOTER ====================================-->
>
>
<--===== START FOOTER ====================================-->

<--===== WEB LINKS ========================================-->

Useful Links

<--===== START PAGE =====================================-->

<--===== BANNER IMAGE =========================================-->

<--===== CONTENT: =========-->

<--===== PAGE TITLE ============================================-->

<--===== PAGE TEXT ============================================-->

<--===== END CONTENT: =========-->

<--===== END PAGE ============================================-->

<--===== IMAGE ===========================================-->

T950

<--===== END PAGE =======================================-->

<--===== END FOOTER ====================================-->
 
<--===== END PAGE =======================================-->
 
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.