<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Disk mount points... in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979958#M121963</link>
    <description>We've used links quite a bit for this kind of thing and have had no problems.  One note though - pay close attention to the attributes and ownerships of the link that you create.</description>
    <pubDate>Thu, 22 May 2003 16:28:26 GMT</pubDate>
    <dc:creator>Mike Miller_8</dc:creator>
    <dc:date>2003-05-22T16:28:26Z</dc:date>
    <item>
      <title>Disk mount points...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979953#M121958</link>
      <description>We are currently moving two systems from one datacenter to another.  Right now all of the external disk logical volumes are mounted off of the / filesystem (e.g. /m008). For obviuos reasons we would like to move the mounts but we are going to have a lot of issues with customized scripts etc that will need to be re-written.  Would there be a performance impact to disk i/o if we put a link at /m008 that went to /var/opt/xxx/xxxx.... Our project has an impossible timeline and no budget (what's new) and we are looking for a workable temporary solution.  All replies appreciated...Thanks.</description>
      <pubDate>Thu, 22 May 2003 15:01:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979953#M121958</guid>
      <dc:creator>Scott E Smith</dc:creator>
      <dc:date>2003-05-22T15:01:01Z</dc:date>
    </item>
    <item>
      <title>Re: Disk mount points...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979954#M121959</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;A symbolic link will not cost anything in performance.  It's a very appropriate solution.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Thu, 22 May 2003 15:02:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979954#M121959</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2003-05-22T15:02:35Z</dc:date>
    </item>
    <item>
      <title>Re: Disk mount points...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979955#M121960</link>
      <description>are the logical volumes in a seperate volume group?  if so then there is no need to move them.  if the logical volumes are directly off / then yes, I would recommend moving them to a different mount point or just create a different volume group and keep the mount point the same. - this way yours scripts won't be affected</description>
      <pubDate>Thu, 22 May 2003 15:04:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979955#M121960</guid>
      <dc:creator>John Meissner</dc:creator>
      <dc:date>2003-05-22T15:04:07Z</dc:date>
    </item>
    <item>
      <title>Re: Disk mount points...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979956#M121961</link>
      <description>James... you're too fast... this was the second time you beat me today.</description>
      <pubDate>Thu, 22 May 2003 15:06:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979956#M121961</guid>
      <dc:creator>John Meissner</dc:creator>
      <dc:date>2003-05-22T15:06:02Z</dc:date>
    </item>
    <item>
      <title>Re: Disk mount points...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979957#M121962</link>
      <description>As a "workable temporary solution" yes the sym link makes sense. In the long run having too many sym link will impact the performance in general, not significant though. I usually shy away from having to create sym link unless it takes major resources to update the application scripts/programs.&lt;BR /&gt;my $0.02</description>
      <pubDate>Thu, 22 May 2003 15:10:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979957#M121962</guid>
      <dc:creator>S.K. Chan</dc:creator>
      <dc:date>2003-05-22T15:10:49Z</dc:date>
    </item>
    <item>
      <title>Re: Disk mount points...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979958#M121963</link>
      <description>We've used links quite a bit for this kind of thing and have had no problems.  One note though - pay close attention to the attributes and ownerships of the link that you create.</description>
      <pubDate>Thu, 22 May 2003 16:28:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979958#M121963</guid>
      <dc:creator>Mike Miller_8</dc:creator>
      <dc:date>2003-05-22T16:28:26Z</dc:date>
    </item>
    <item>
      <title>Re: Disk mount points...</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979959#M121964</link>
      <description>Scott,&lt;BR /&gt;&lt;BR /&gt;There will be no performance issue at all with your mountpoint approach.  You can in fact make this a permanent solution if you wish.&lt;BR /&gt;&lt;BR /&gt;Hai</description>
      <pubDate>Thu, 22 May 2003 16:35:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/disk-mount-points/m-p/2979959#M121964</guid>
      <dc:creator>Hai Nguyen_1</dc:creator>
      <dc:date>2003-05-22T16:35:20Z</dc:date>
    </item>
  </channel>
</rss>

