Difference: PetalLinux (1 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: ===================================-->

Revision 517 Nov 2017 - StuartBorthwick1

Line: 1 to 1
 
META TOPICPARENT name="PetalSys"
<--===== START PAGE =====================================-->
Line: 7 to 7
 
<--===== PAGE TITLE ======================================-->

<--===== PAGE TEXT ======================================-->
Added:
>
>

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

 

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:

Line: 29 to 31
 

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.

Changed:
<
<

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

>
>

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

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

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 =======================================-->

Revision 313 Oct 2017 - StuartBorthwick1

Line: 1 to 1
 
META TOPICPARENT name="PetalSys"
<--===== START PAGE =====================================-->
Line: 16 to 16
  /nfs/petal/my_project
Changed:
<
<

On the PETAL server, the 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:

>
>

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:

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

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:

 
Line: 30 to 35
 
Deleted:
<
<

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:

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

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

Revision 211 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 mounted path is:

>
>

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

  /nfs/petal/my_project
Changed:
<
<

On the PETAL server, the archive root point is /export/archive. 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:

>
>

On the PETAL server, the 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:

 
Changed:
<
<
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
>
>
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
 
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:
petal -fstype=nfs4,sec=krb5,hard,intr petal-fs.leeds.ac.uk:/archive/deep1/my_project

>
>

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:

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

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

Revision 111 Oct 2017 - StuartBorthwick1

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="PetalSys"
<--===== START PAGE =====================================-->

<--===== START HEADER ====================================-->

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

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

PETAL: 1.4 Linux client access

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

<--===== END HEADER ====================================-->

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

<-- 
  • Set THISPAGETITLE = PETAL: Linux client access
-->

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

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

/nfs/petal/my_project

On the PETAL server, the archive root point is /export/archive. 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:

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


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:
petal -fstype=nfs4,sec=krb5,hard,intr petal-fs.leeds.ac.uk:/archive/deep1/my_project

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

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

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

Useful Links

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

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

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

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

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

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

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

<--===== 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.