<?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:  /var/log/lastlog - huge file in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117314#M49874</link>
    <description>The apparent size of /var/log/lastlog will correspond to the largest&lt;BR /&gt;uid that is recorded in it.  The offset into the file can be really huge&lt;BR /&gt;for a uid that is a small negative number such as 'nobody'.  With a 64-bit&lt;BR /&gt;system that can make a file that seems to be a terabyte in size.  The file&lt;BR /&gt;is actually sparse, taking up little room on disk.  But any copy utility&lt;BR /&gt;will have a very hard time with it because there is no way to seek to the&lt;BR /&gt;next non-zero block in such a file.  The complete file will need to be&lt;BR /&gt;read to find the non-zero blocks.  Clever commands such as cp can then&lt;BR /&gt;write the file out to a new location by seeking and creating a new sparse&lt;BR /&gt;file.  But the full apparent size of the file will flood into the file&lt;BR /&gt;system buffer cache, pushing out more useful data.&lt;BR /&gt;</description>
    <pubDate>Sun, 06 Jul 2008 20:36:15 GMT</pubDate>
    <dc:creator>Mike Stroyan</dc:creator>
    <dc:date>2008-07-06T20:36:15Z</dc:date>
    <item>
      <title>/var/log/lastlog - huge file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117308#M49868</link>
      <description>Hi guys,&lt;BR /&gt;&lt;BR /&gt;I have a question. On my HP DL585 box running RH4, I could see huge file around 273GB - /var/log/lastlog. Whats causing this to so big ?</description>
      <pubDate>Thu, 03 Jul 2008 01:44:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117308#M49868</guid>
      <dc:creator>Jees Joy</dc:creator>
      <dc:date>2008-07-03T01:44:20Z</dc:date>
    </item>
    <item>
      <title>Re:  /var/log/lastlog - huge file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117309#M49869</link>
      <description>Check the actual size with:&lt;BR /&gt;&lt;BR /&gt;# du -h /var/log/lastlog&lt;BR /&gt;&lt;BR /&gt;This file contains sparse blocks, the real size is correctly reported with command above</description>
      <pubDate>Fri, 04 Jul 2008 06:27:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117309#M49869</guid>
      <dc:creator>Aleksandar Mitsev</dc:creator>
      <dc:date>2008-07-04T06:27:15Z</dc:date>
    </item>
    <item>
      <title>Re:  /var/log/lastlog - huge file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117310#M49870</link>
      <description>That file is a log for sessions on your system, and you examine it by using lastlog. Every time a users login/logout from your system, the file is updated.&lt;BR /&gt;&lt;BR /&gt;You should ensure that the file is included in your "logrotate" configuration and that "logrotate" is enabled.</description>
      <pubDate>Fri, 04 Jul 2008 12:38:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117310#M49870</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2008-07-04T12:38:28Z</dc:date>
    </item>
    <item>
      <title>Re:  /var/log/lastlog - huge file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117311#M49871</link>
      <description>you can better do  purge this file but before taking a backup.</description>
      <pubDate>Sun, 06 Jul 2008 11:41:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117311#M49871</guid>
      <dc:creator>Jeeshan</dc:creator>
      <dc:date>2008-07-06T11:41:24Z</dc:date>
    </item>
    <item>
      <title>Re:  /var/log/lastlog - huge file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117312#M49872</link>
      <description>you can better do  purge this file but after takes a backup.</description>
      <pubDate>Sun, 06 Jul 2008 11:41:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117312#M49872</guid>
      <dc:creator>Jeeshan</dc:creator>
      <dc:date>2008-07-06T11:41:48Z</dc:date>
    </item>
    <item>
      <title>Re:  /var/log/lastlog - huge file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117313#M49873</link>
      <description>sorry, follow my last comment. (typo mistake)</description>
      <pubDate>Sun, 06 Jul 2008 11:42:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117313#M49873</guid>
      <dc:creator>Jeeshan</dc:creator>
      <dc:date>2008-07-06T11:42:25Z</dc:date>
    </item>
    <item>
      <title>Re:  /var/log/lastlog - huge file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117314#M49874</link>
      <description>The apparent size of /var/log/lastlog will correspond to the largest&lt;BR /&gt;uid that is recorded in it.  The offset into the file can be really huge&lt;BR /&gt;for a uid that is a small negative number such as 'nobody'.  With a 64-bit&lt;BR /&gt;system that can make a file that seems to be a terabyte in size.  The file&lt;BR /&gt;is actually sparse, taking up little room on disk.  But any copy utility&lt;BR /&gt;will have a very hard time with it because there is no way to seek to the&lt;BR /&gt;next non-zero block in such a file.  The complete file will need to be&lt;BR /&gt;read to find the non-zero blocks.  Clever commands such as cp can then&lt;BR /&gt;write the file out to a new location by seeking and creating a new sparse&lt;BR /&gt;file.  But the full apparent size of the file will flood into the file&lt;BR /&gt;system buffer cache, pushing out more useful data.&lt;BR /&gt;</description>
      <pubDate>Sun, 06 Jul 2008 20:36:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117314#M49874</guid>
      <dc:creator>Mike Stroyan</dc:creator>
      <dc:date>2008-07-06T20:36:15Z</dc:date>
    </item>
    <item>
      <title>Re:  /var/log/lastlog - huge file</title>
      <link>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117315#M49875</link>
      <description>Thanks friends, those answers helped me thanks</description>
      <pubDate>Wed, 09 Jul 2008 07:36:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/var-log-lastlog-huge-file/m-p/5117315#M49875</guid>
      <dc:creator>Jees Joy</dc:creator>
      <dc:date>2008-07-09T07:36:27Z</dc:date>
    </item>
  </channel>
</rss>

