<?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: lvreduce in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745045#M642803</link>
    <description>In all of the cases I've tested on, lvreduce is okay ONCE you defrag first (with fsadm).  Apart from the obvious (don't defrag first) The only time I've seen trouble was when a failing CPU started screwing things up (on the defrag).&lt;BR /&gt;&lt;BR /&gt;However, if you haven't modified your filesystem (in any way) the space should still be unused.&lt;BR /&gt;&lt;BR /&gt;As the others suggest, backup, a quick tar to tape is always good to have.&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
    <pubDate>Mon, 17 Jun 2002 14:15:18 GMT</pubDate>
    <dc:creator>Bill McNAMARA_1</dc:creator>
    <dc:date>2002-06-17T14:15:18Z</dc:date>
    <item>
      <title>lvreduce</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745037#M642795</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;I have just increased in size the wrong logical volume. Stupid or what - don't answer that. Anyway, having read other threads on this, I gather in general that using lvreduce is not a good idea. However, as I have only just increased the lv and nothing is likely to have used the space, am I ok to reduce it or not? I have on-line jfs and os is 10.20 &lt;BR /&gt;&lt;BR /&gt;Thanks &lt;BR /&gt;Keely &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Jun 2002 13:50:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745037#M642795</guid>
      <dc:creator>Keely Jackson</dc:creator>
      <dc:date>2002-06-14T13:50:22Z</dc:date>
    </item>
    <item>
      <title>Re: lvreduce</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745038#M642796</link>
      <description>Hi Keely,&lt;BR /&gt;&lt;BR /&gt;You should be safe in this case.&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Fri, 14 Jun 2002 13:55:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745038#M642796</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2002-06-14T13:55:59Z</dc:date>
    </item>
    <item>
      <title>Re: lvreduce</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745039#M642797</link>
      <description>If you are sure that ng has been written on the disk after you have increased the lv, you can take a chance to reduce the lv. But be careful don't reduce more than whatever you have increased. It may require a fsck.&lt;BR /&gt;&lt;BR /&gt;Sandip</description>
      <pubDate>Fri, 14 Jun 2002 13:57:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745039#M642797</guid>
      <dc:creator>Sandip Ghosh</dc:creator>
      <dc:date>2002-06-14T13:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: lvreduce</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745040#M642798</link>
      <description>Hi Keely:&lt;BR /&gt;&lt;BR /&gt;If you have done an 'lvextend' but nothing more (i.e. no 'fsdm'), you have not affected the filesystem; only the container in which it sits.  In this case, you can safely 'lvreduce' to your *exact* original size.&lt;BR /&gt;&lt;BR /&gt;For insurance, of course, make a backup first!&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Fri, 14 Jun 2002 13:59:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745040#M642798</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2002-06-14T13:59:56Z</dc:date>
    </item>
    <item>
      <title>Re: lvreduce</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745041#M642799</link>
      <description>Hi Keely,&lt;BR /&gt;&lt;BR /&gt;Take a backup, just in case. The n try a lvreduce.&lt;BR /&gt;&lt;BR /&gt;But it is not such a good idea. you should be doing an lvremove and then recreate the lv.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Regds&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Jun 2002 14:02:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745041#M642799</guid>
      <dc:creator>Sanjay_6</dc:creator>
      <dc:date>2002-06-14T14:02:25Z</dc:date>
    </item>
    <item>
      <title>Re: lvreduce</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745042#M642800</link>
      <description>I would do a backup first. You will be able to reduce the LV without issues, if you haven't done anything after lvextend. While reducing it, clearly specify the original space. Check the FS with 'fsck' command, once everything is set right.&lt;BR /&gt;&lt;BR /&gt;2 cents ..</description>
      <pubDate>Fri, 14 Jun 2002 14:02:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745042#M642800</guid>
      <dc:creator>Helen French</dc:creator>
      <dc:date>2002-06-14T14:02:43Z</dc:date>
    </item>
    <item>
      <title>Re: lvreduce</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745043#M642801</link>
      <description>Yes, in your case, you can use lvreduce safely, good luck!&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Jun 2002 14:03:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745043#M642801</guid>
      <dc:creator>Victor_5</dc:creator>
      <dc:date>2002-06-14T14:03:22Z</dc:date>
    </item>
    <item>
      <title>Re: lvreduce</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745044#M642802</link>
      <description>Do a backup just in case! It better to be safe than sorry.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Marty</description>
      <pubDate>Mon, 17 Jun 2002 13:46:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745044#M642802</guid>
      <dc:creator>Martin Johnson</dc:creator>
      <dc:date>2002-06-17T13:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: lvreduce</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745045#M642803</link>
      <description>In all of the cases I've tested on, lvreduce is okay ONCE you defrag first (with fsadm).  Apart from the obvious (don't defrag first) The only time I've seen trouble was when a failing CPU started screwing things up (on the defrag).&lt;BR /&gt;&lt;BR /&gt;However, if you haven't modified your filesystem (in any way) the space should still be unused.&lt;BR /&gt;&lt;BR /&gt;As the others suggest, backup, a quick tar to tape is always good to have.&lt;BR /&gt;&lt;BR /&gt;Later,&lt;BR /&gt;Bill</description>
      <pubDate>Mon, 17 Jun 2002 14:15:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745045#M642803</guid>
      <dc:creator>Bill McNAMARA_1</dc:creator>
      <dc:date>2002-06-17T14:15:18Z</dc:date>
    </item>
    <item>
      <title>Re: lvreduce</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745046#M642804</link>
      <description>Hi Keely,&lt;BR /&gt;&lt;BR /&gt;I agree with Pete, Jim, et. al.  As long as you have NOT extended the filesystem and have only just extended the LV, you can lvreduce back to the original size with no damage.  I have done this successfully.&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;Jim</description>
      <pubDate>Mon, 17 Jun 2002 14:31:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745046#M642804</guid>
      <dc:creator>Jim Turner</dc:creator>
      <dc:date>2002-06-17T14:31:16Z</dc:date>
    </item>
    <item>
      <title>Re: lvreduce</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745047#M642805</link>
      <description>Hi Keely&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If you have just meaning like ( no reboots , file deletes and file creation on the lvol ) then you can safely reduce it.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Manoj Srivastava</description>
      <pubDate>Mon, 17 Jun 2002 14:55:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745047#M642805</guid>
      <dc:creator>MANOJ SRIVASTAVA</dc:creator>
      <dc:date>2002-06-17T14:55:11Z</dc:date>
    </item>
    <item>
      <title>Re: lvreduce</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745048#M642806</link>
      <description>I think is very important have a tape make_recovery done.&lt;BR /&gt;On case to use lvreduce, do not forget use newfs command to create a ew fs with the new lv size properties.&lt;BR /&gt;&lt;BR /&gt;If you wants the commands or more information, ask me.&lt;BR /&gt;&lt;BR /&gt;Juanma.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 17 Jun 2002 15:11:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lvreduce/m-p/2745048#M642806</guid>
      <dc:creator>Juan Manuel López</dc:creator>
      <dc:date>2002-06-17T15:11:34Z</dc:date>
    </item>
  </channel>
</rss>

