<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Running UNIX &#187; error</title>
	<atom:link href="http://www.runningunix.com/tag/error/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.runningunix.com</link>
	<description>UNIX/Solaris tips, tricks, and advice</description>
	<lastBuildDate>Sun, 25 Apr 2010 17:33:40 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Unable to shrink VXFS volume</title>
		<link>http://www.runningunix.com/2008/12/unable-to-shrink-vxfs-volume/</link>
		<comments>http://www.runningunix.com/2008/12/unable-to-shrink-vxfs-volume/#comments</comments>
		<pubDate>Wed, 24 Dec 2008 00:54:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Solaris]]></category>
		<category><![CDATA[UNIX]]></category>
		<category><![CDATA[defrag]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[vxfs]]></category>
		<category><![CDATA[vxresize]]></category>
		<category><![CDATA[vxvm]]></category>

		<guid isPermaLink="false">http://www.runningunix.com/?p=44</guid>
		<description><![CDATA[Never seen this before. This volume is about 50% full, total size 300GB. I tried defragging the file system with fsadm, but didn&#8217;t seem to help. I even unmounted it, mounted it somewhere else and immediately tried the resize again &#8211; still the same error. I know there are no open files on the file [...]]]></description>
			<content:encoded><![CDATA[<p>Never seen this before. This volume is about 50% full, total size 300GB. I tried defragging the file system with fsadm, but didn&#8217;t seem to help. I even unmounted it, mounted it somewhere else and immediately tried the resize again &#8211; still the same error. I know there are no open files on the file system.</p>
<p><code>server# vxresize -g rootdg perforce 285g<br />
UX:vxfs fsadm: ERROR: V-3-20343: cannot shrink /dev/vx/rdsk/rootdg/perforce - blocks are currently in use.<br />
VxVM vxresize ERROR V-5-1-7514 Problem running fsadm command for volume perforce, in diskgroup rootdg</code></p>
<p>I may have to backup/newfs/restore on this one. Too lazy to open a Symantec case because it&#8217;s not a big priority.</p>
<p></p>
<p><a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.runningunix.com%2F2008%2F12%2Funable-to-shrink-vxfs-volume%2F&amp;linkname=Unable%20to%20shrink%20VXFS%20volume"><img src="http://www.runningunix.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a> </p>]]></content:encoded>
			<wfw:commentRss>http://www.runningunix.com/2008/12/unable-to-shrink-vxfs-volume/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Solaris 10 mount point permissions are important</title>
		<link>http://www.runningunix.com/2008/05/solaris-10-mount-point-permissions-are-important/</link>
		<comments>http://www.runningunix.com/2008/05/solaris-10-mount-point-permissions-are-important/#comments</comments>
		<pubDate>Tue, 13 May 2008 22:44:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Solaris]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[mount point]]></category>
		<category><![CDATA[permissions]]></category>
		<category><![CDATA[solaris 10]]></category>

		<guid isPermaLink="false">http://www.cybersand.com/blog/?p=9</guid>
		<description><![CDATA[rm: cannot determine if this is an ancestor of the current working directory
This is caused by an underlying mount point permission that is too strict (700). You can change the permissions on the mount point without unmounting the volume by using lofs creatively:
#create temp directory
server1&#62; mkdir -m 755 /fix-mnt 
# mount the directory which contains the [...]]]></description>
			<content:encoded><![CDATA[<p>rm: cannot determine if this is an ancestor of the current working directory</p>
<p>This is caused by an underlying mount point permission that is too strict (700). You can change the permissions on the mount point without unmounting the volume by using lofs creatively:</p>
<p>#create temp directory</p>
<blockquote><p>server1&gt; mkdir -m 755 /fix-mnt </p></blockquote>
<p># mount the directory which <strong>contains</strong> the mount point, not the mount point itself, but its parent directory.</p>
<blockquote><p>server1&gt; mount -F lofs -o nosub /users/zones/server1-z3/root/users/  /fix-mnt<br />
server1&gt; ls -ld /fix-mnt/mountpoint        #confirms the permssions are not 775<br />
server1&gt; chmod 775 /fix-mnt/mountpoint<br />
server1&gt; umount /fix-mnt<br />
server1&gt; rmdir /fix-mnt</p></blockquote>
<p><a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fwww.runningunix.com%2F2008%2F05%2Fsolaris-10-mount-point-permissions-are-important%2F&amp;linkname=Solaris%2010%20mount%20point%20permissions%20are%20important"><img src="http://www.runningunix.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a> </p>]]></content:encoded>
			<wfw:commentRss>http://www.runningunix.com/2008/05/solaris-10-mount-point-permissions-are-important/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
