<?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: ls ig giving the wrong sizing? in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955709#M617907</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;"ls -al" gives you the size in bytes and "ls -as" will give you the size in blocks (512 bytes = 1 block)...&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;&lt;BR /&gt;Eric Antunes</description>
    <pubDate>Mon, 30 Jan 2006 05:58:55 GMT</pubDate>
    <dc:creator>Eric Antunes</dc:creator>
    <dc:date>2006-01-30T05:58:55Z</dc:date>
    <item>
      <title>ls ig giving the wrong sizing?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955706#M617904</link>
      <description>Hi,&lt;BR /&gt;I have a 90 gig filesystem and if I look whit ls there is 100 gig is used&lt;BR /&gt;I found that i have some files:&lt;BR /&gt;&lt;BR /&gt;du -ks tempimp_2.dbf&lt;BR /&gt;1518616 tempimp_2.dbf&lt;BR /&gt;&lt;BR /&gt; ls -al tempimp_2.dbf&lt;BR /&gt;-rw-r-----   1 oraccr     dba        5368717312 Jan 26 23:25 tempimp_2.dbf&lt;BR /&gt;&lt;BR /&gt;Does is this a bug in ls ore is ther a explanation?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 30 Jan 2006 05:02:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955706#M617904</guid>
      <dc:creator>F Verschuren</dc:creator>
      <dc:date>2006-01-30T05:02:36Z</dc:date>
    </item>
    <item>
      <title>Re: ls ig giving the wrong sizing?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955707#M617905</link>
      <description>Hello, &lt;BR /&gt;&lt;BR /&gt;It is not a bug, you can check this thread for more information &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=968235" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=968235&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;-Arun</description>
      <pubDate>Mon, 30 Jan 2006 05:11:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955707#M617905</guid>
      <dc:creator>Arunvijai_4</dc:creator>
      <dc:date>2006-01-30T05:11:30Z</dc:date>
    </item>
    <item>
      <title>Re: ls ig giving the wrong sizing?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955708#M617906</link>
      <description>Nope.&lt;BR /&gt;&lt;BR /&gt;You have to check as,&lt;BR /&gt;&lt;BR /&gt;du -s filename&lt;BR /&gt;ls -s filename&lt;BR /&gt;&lt;BR /&gt;it will be same. It is meaning to show size in 512 blocks.&lt;BR /&gt;&lt;BR /&gt;du -ks filename&lt;BR /&gt;ls -s filename (size field * 2 ) will be same to denote 1024k blocks.&lt;BR /&gt;&lt;BR /&gt;Read du and ls man page.&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;Muthu</description>
      <pubDate>Mon, 30 Jan 2006 05:26:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955708#M617906</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2006-01-30T05:26:58Z</dc:date>
    </item>
    <item>
      <title>Re: ls ig giving the wrong sizing?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955709#M617907</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;"ls -al" gives you the size in bytes and "ls -as" will give you the size in blocks (512 bytes = 1 block)...&lt;BR /&gt;&lt;BR /&gt;Best Regards,&lt;BR /&gt;&lt;BR /&gt;Eric Antunes</description>
      <pubDate>Mon, 30 Jan 2006 05:58:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955709#M617907</guid>
      <dc:creator>Eric Antunes</dc:creator>
      <dc:date>2006-01-30T05:58:55Z</dc:date>
    </item>
    <item>
      <title>Re: ls ig giving the wrong sizing?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955710#M617908</link>
      <description>whit the -s option it is the same, &lt;BR /&gt;after reading the man page prealloc&lt;BR /&gt;I think that that was used when creating the file</description>
      <pubDate>Mon, 30 Jan 2006 07:47:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955710#M617908</guid>
      <dc:creator>F Verschuren</dc:creator>
      <dc:date>2006-01-30T07:47:25Z</dc:date>
    </item>
    <item>
      <title>Re: ls ig giving the wrong sizing?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955711#M617909</link>
      <description>This is an artifact of sparse files; it is not at all uncommon for database files to be sparse. Essentially, all that happens is that an lseek() is done to very large offset and then data are written there and the file is closed. The "missing" data are filled in with NUL's when the data are actually read. Just as airlines can overbook a flight, sparse files can overcommit a filesystem.</description>
      <pubDate>Mon, 30 Jan 2006 10:02:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955711#M617909</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-01-30T10:02:35Z</dc:date>
    </item>
    <item>
      <title>Re: ls ig giving the wrong sizing?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955712#M617910</link>
      <description>Tanks, I have mailed the Oracle DBA the reason.</description>
      <pubDate>Mon, 30 Jan 2006 10:34:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955712#M617910</guid>
      <dc:creator>F Verschuren</dc:creator>
      <dc:date>2006-01-30T10:34:00Z</dc:date>
    </item>
    <item>
      <title>Re: ls ig giving the wrong sizing?</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955713#M617911</link>
      <description>closed</description>
      <pubDate>Mon, 30 Jan 2006 10:34:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ls-ig-giving-the-wrong-sizing/m-p/4955713#M617911</guid>
      <dc:creator>F Verschuren</dc:creator>
      <dc:date>2006-01-30T10:34:33Z</dc:date>
    </item>
  </channel>
</rss>

