- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: shared LVM
Operating System - HP-UX
1754186
Members
4138
Online
108811
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
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
тАО07-30-2000 05:57 PM
тАО07-30-2000 05:57 PM
Re: shared LVM
Rick,
I read your message in my original post.
I followed the steps that Denver gave me exactly. I have written files to the disk from System A, unmounted it and then mounted it on System B. All OK - the new files are there. I also mirrored the drive to another one that existed in the High Availability Storage Server. So to answer your quesiton, I didn't do anything special. Just followed the steps in Denver's post on my original message.
I read your message in my original post.
I followed the steps that Denver gave me exactly. I have written files to the disk from System A, unmounted it and then mounted it on System B. All OK - the new files are there. I also mirrored the drive to another one that existed in the High Availability Storage Server. So to answer your quesiton, I didn't do anything special. Just followed the steps in Denver's post on my original message.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2000 09:39 AM
тАО08-11-2000 09:39 AM
Re: shared LVM
HI All,
Sorry it as been a few days since I have been back here. Well, end result is yes we do in fact have to make sure only one system is mounted at a time. I am writing a script on each machine called sh-mount that will accept a parameter for the lvol name to be mounted and a R or W for permision desired.
On each systems mount point directory I have put a file called unmounted. When the FS is mounted there the file "disappears" when it is unmounted the file is visable.
Using an nfs mount to other systems mount point dir I check for this file. If it exists I go ahead and mount the fs as desired. If the file is not there I attempt a remshell command to unmount the FS remotely. If it fails I echo an error to screen.
Not real pretty but it works for now. We are still in discussions over final solution. We were thinking about a dedicated backbone across the systems involved and simply use NFS. Now I am being told there are performance problems with NFS as well....SIGH...
BTW. I went to assing points to everyone but I dont seem to have an option to do so. Is there a time limit?
Sorry it as been a few days since I have been back here. Well, end result is yes we do in fact have to make sure only one system is mounted at a time. I am writing a script on each machine called sh-mount that will accept a parameter for the lvol name to be mounted and a R or W for permision desired.
On each systems mount point directory I have put a file called unmounted. When the FS is mounted there the file "disappears" when it is unmounted the file is visable.
Using an nfs mount to other systems mount point dir I check for this file. If it exists I go ahead and mount the fs as desired. If the file is not there I attempt a remshell command to unmount the FS remotely. If it fails I echo an error to screen.
Not real pretty but it works for now. We are still in discussions over final solution. We were thinking about a dedicated backbone across the systems involved and simply use NFS. Now I am being told there are performance problems with NFS as well....SIGH...
BTW. I went to assing points to everyone but I dont seem to have an option to do so. Is there a time limit?
Of all the times in my life I have had, this has got to be one of them
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-20-2000 06:53 AM
тАО08-20-2000 06:53 AM
Re: shared LVM
Just as a followup, sharing a filesystem between two different computers is incredibly complicated. It is complex enough inside a single system with multiple processors that perform independent changes to the filesystems. In many cases, the kernel must use internal software signals to synchronize events.
On the surface, it would seem simple enough to read and write the files but the reality is that there must be very detailed locking in both directories as well as inodes and individual records to prevent trashing the entire filesystem. Just flushing the buffer cache with sync commands performs a very lengthy set of directory updates, from requesting additional space and/or allocating new inodes, to making changes to the directories and posting the new data into appropriate data files.
NFS accomplishes file sharing by running all requests through a single server, that is, all requests are made to the server and the results are sent back to the client.
Yes, NFS is going to be significantly slower than physical disk channels, especially fiber disk channels. But without special software to coordinate all the dozens of tasks need to keep a filesystem stable, sharing filesystems between machines is not possible.
Bill Hassell, sysadmin
On the surface, it would seem simple enough to read and write the files but the reality is that there must be very detailed locking in both directories as well as inodes and individual records to prevent trashing the entire filesystem. Just flushing the buffer cache with sync commands performs a very lengthy set of directory updates, from requesting additional space and/or allocating new inodes, to making changes to the directories and posting the new data into appropriate data files.
NFS accomplishes file sharing by running all requests through a single server, that is, all requests are made to the server and the results are sent back to the client.
Yes, NFS is going to be significantly slower than physical disk channels, especially fiber disk channels. But without special software to coordinate all the dozens of tasks need to keep a filesystem stable, sharing filesystems between machines is not possible.
Bill Hassell, sysadmin
- « Previous
-
- 1
- 2
- Next »
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