- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- loopback filesystem, or what?
Operating System - HP-UX
1752577
Members
4814
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2000 03:23 AM
тАО11-02-2000 03:23 AM
While collecting fstype information for writing a Perl script that should run on different flavours of Unix (i.e. HP-UX, AIX, Solaris, Linux) I stumbled over the fstype lofs in HP-UX's fstab manpage.
Looking for a more explicit explantion I couldn't find a mkfs_lofs manpage.
The only somewhat disturbing hint I found is the WARNINGS paragraph in the mount_lofs manpage, "...should only be used by experienced users...blah blah...can be confusing...blah blah".
Doing occasional backups on CD-R/RW on my Linux box at home using mkisofs and cdrecord, I know you can create an image file before burning, that you can mount as a loopback device as if accessing an already burned CDROM to check that everything has been included.
Is HP-UX's lofs something similar or am I on a totally wrong track?
Looking for a more explicit explantion I couldn't find a mkfs_lofs manpage.
The only somewhat disturbing hint I found is the WARNINGS paragraph in the mount_lofs manpage, "...should only be used by experienced users...blah blah...can be confusing...blah blah".
Doing occasional backups on CD-R/RW on my Linux box at home using mkisofs and cdrecord, I know you can create an image file before burning, that you can mount as a loopback device as if accessing an already burned CDROM to check that everything has been included.
Is HP-UX's lofs something similar or am I on a totally wrong track?
Madness, thy name is system administration
Solved! Go to Solution.
- Tags:
- LOFS
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2000 04:20 AM
тАО11-02-2000 04:20 AM
Solution
Hi Ralph,
The following is an extract from the 10.20 Release notes (found in /usr/share/doc):-
LOFS allows mounting an existing directory onto another directory.
The effect is similar to that of a symbolic link, except that the
usual mount options are available, and there are no issues with the
meaning of "..". When an application does a stat(2) on a LOFS file,
the values returned are the same as for the file in its original
location, except that the st_fstype field indicates LOFS. In particular,
st_dev and st_ino are the same, so that the conventional test for
whether two pathnames name the same file (device and inumber match)
continues to work.
Some applications that walk file trees use stat's st_dev to detect the
crossing of mount points. This will not work with LOFS because an
LOFS file has the st_dev of its original location. Code that needs
to identify a particular file system (in the sense of a particular
mount) should use f_fsid from statfs(2) or statvfs(2).
Hope this helps,
John
The following is an extract from the 10.20 Release notes (found in /usr/share/doc):-
LOFS allows mounting an existing directory onto another directory.
The effect is similar to that of a symbolic link, except that the
usual mount options are available, and there are no issues with the
meaning of "..". When an application does a stat(2) on a LOFS file,
the values returned are the same as for the file in its original
location, except that the st_fstype field indicates LOFS. In particular,
st_dev and st_ino are the same, so that the conventional test for
whether two pathnames name the same file (device and inumber match)
continues to work.
Some applications that walk file trees use stat's st_dev to detect the
crossing of mount points. This will not work with LOFS because an
LOFS file has the st_dev of its original location. Code that needs
to identify a particular file system (in the sense of a particular
mount) should use f_fsid from statfs(2) or statvfs(2).
Hope this helps,
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2000 04:24 AM
тАО11-02-2000 04:24 AM
Re: loopback filesystem, or what?
For lofs see this site:
http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90672/B2355-90672_top.html&con=/hpux/onlinedocs/B2355-90672/00/00/39-con.html&toc=/hpux/onlinedocs/B2355-90672/00/00/39-toc.html&searchterms=lofs&queryid=20001102-042219
and
http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90129/B2355-90129_top.html&con=/hpux/onlinedocs/B2355-90129/00/01/194-con.html&toc=/hpux/onlinedocs/B2355-90129/00/01/194-toc.html&searchterms=lofs&queryid=20001102-042219
http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90672/B2355-90672_top.html&con=/hpux/onlinedocs/B2355-90672/00/00/39-con.html&toc=/hpux/onlinedocs/B2355-90672/00/00/39-toc.html&searchterms=lofs&queryid=20001102-042219
and
http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90129/B2355-90129_top.html&con=/hpux/onlinedocs/B2355-90129/00/01/194-con.html&toc=/hpux/onlinedocs/B2355-90129/00/01/194-toc.html&searchterms=lofs&queryid=20001102-042219
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2000 05:42 AM
тАО11-02-2000 05:42 AM
Re: loopback filesystem, or what?
John,
thank you for the lengthy explanation.
Now I know I will have no need for employing HP-UX's loopback filesystems. ;-)
But at least my conclusion to loopback FS from the acronym lofs was correct, even though my notion and usage of lofs under Linux is slightly deviating.
Rainer,
thank you for providing the link.
Isn't it amazing how much CGI URL encoding line noise the HP webdevelopers can put in a single string? ;-)
thank you for the lengthy explanation.
Now I know I will have no need for employing HP-UX's loopback filesystems. ;-)
But at least my conclusion to loopback FS from the acronym lofs was correct, even though my notion and usage of lofs under Linux is slightly deviating.
Rainer,
thank you for providing the link.
Isn't it amazing how much CGI URL encoding line noise the HP webdevelopers can put in a single string? ;-)
Madness, thy name is system administration
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP