<?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 Error dmesg command (type vxfs) in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204040#M167161</link>
    <description>On the dmesg command I have the follow error msg:&lt;BR /&gt;vxfs: mesg 001: vx_nospace - /dev/vg02/lvol1 file system full (1 block extent)&lt;BR /&gt;&lt;BR /&gt;but on the command bdf I have &lt;BR /&gt;Filesystem kbytes used avail %used Mounted on&lt;BR /&gt;/dev/vg02/lvol1 3072000 1648868 1336957 55% /disco7&lt;BR /&gt;&lt;BR /&gt;What does it mean ?&lt;BR /&gt;Thanks</description>
    <pubDate>Fri, 27 Feb 2004 04:06:28 GMT</pubDate>
    <dc:creator>Dimitri di Paolo</dc:creator>
    <dc:date>2004-02-27T04:06:28Z</dc:date>
    <item>
      <title>Error dmesg command (type vxfs)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204040#M167161</link>
      <description>On the dmesg command I have the follow error msg:&lt;BR /&gt;vxfs: mesg 001: vx_nospace - /dev/vg02/lvol1 file system full (1 block extent)&lt;BR /&gt;&lt;BR /&gt;but on the command bdf I have &lt;BR /&gt;Filesystem kbytes used avail %used Mounted on&lt;BR /&gt;/dev/vg02/lvol1 3072000 1648868 1336957 55% /disco7&lt;BR /&gt;&lt;BR /&gt;What does it mean ?&lt;BR /&gt;Thanks</description>
      <pubDate>Fri, 27 Feb 2004 04:06:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204040#M167161</guid>
      <dc:creator>Dimitri di Paolo</dc:creator>
      <dc:date>2004-02-27T04:06:28Z</dc:date>
    </item>
    <item>
      <title>Re: Error dmesg command (type vxfs)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204041#M167162</link>
      <description>Have you tried bdf -il in case inodes are full?&lt;BR /&gt;&lt;BR /&gt;Mark Syder (like the drink but spelt different)</description>
      <pubDate>Fri, 27 Feb 2004 04:08:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204041#M167162</guid>
      <dc:creator>MarkSyder</dc:creator>
      <dc:date>2004-02-27T04:08:35Z</dc:date>
    </item>
    <item>
      <title>Re: Error dmesg command (type vxfs)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204042#M167163</link>
      <description>Failing that, maybe the filesystem was full but isn't any more.</description>
      <pubDate>Fri, 27 Feb 2004 04:09:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204042#M167163</guid>
      <dc:creator>Mark Grant</dc:creator>
      <dc:date>2004-02-27T04:09:31Z</dc:date>
    </item>
    <item>
      <title>Re: Error dmesg command (type vxfs)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204043#M167164</link>
      <description>could u umount the filesystem. then move the /etc/mnttab to /etc/mnttab.old and then do a mount /disco7 and see how the things proceeds&lt;BR /&gt;&lt;BR /&gt;With Best Wishes&lt;BR /&gt;Naveej</description>
      <pubDate>Fri, 27 Feb 2004 04:12:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204043#M167164</guid>
      <dc:creator>Naveej.K.A</dc:creator>
      <dc:date>2004-02-27T04:12:32Z</dc:date>
    </item>
    <item>
      <title>Re: Error dmesg command (type vxfs)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204044#M167165</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Check the syslog.log when the error occured&lt;BR /&gt;&lt;BR /&gt;# cat /var/adm/syslog/syslog.log | grep nospace&lt;BR /&gt;Feb 10 13:15:07 db001 vmunix: vxfs: mesg 001: vx_nospace - /dev/vg01/lvol15&lt;BR /&gt;&lt;BR /&gt;Think it was full, not anymore.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Fri, 27 Feb 2004 04:15:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204044#M167165</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2004-02-27T04:15:07Z</dc:date>
    </item>
    <item>
      <title>Re: Error dmesg command (type vxfs)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204045#M167166</link>
      <description>Hi,&lt;BR /&gt;we had the same problem yesterday...&lt;BR /&gt;I think that was full but now itsn't.&lt;BR /&gt;the message on dmesg still remains.&lt;BR /&gt;if you check the syslog you should see the data when the fs was full.&lt;BR /&gt;Hope this helps&lt;BR /&gt;L.</description>
      <pubDate>Fri, 27 Feb 2004 05:13:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204045#M167166</guid>
      <dc:creator>Lorenzo Facello</dc:creator>
      <dc:date>2004-02-27T05:13:04Z</dc:date>
    </item>
    <item>
      <title>Re: Error dmesg command (type vxfs)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204046#M167167</link>
      <description>dmesg command read also the old error log in syslog file ??</description>
      <pubDate>Fri, 27 Feb 2004 05:50:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204046#M167167</guid>
      <dc:creator>Dimitri di Paolo</dc:creator>
      <dc:date>2004-02-27T05:50:10Z</dc:date>
    </item>
    <item>
      <title>Re: Error dmesg command (type vxfs)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204047#M167168</link>
      <description>Dimitri,&lt;BR /&gt;&lt;BR /&gt;Look inside the man page of dmesg, &lt;BR /&gt;&lt;BR /&gt;dmesg looks in a system buffer for recently printed diagnostic&lt;BR /&gt;      messages and prints them on the standard output.  The messages are&lt;BR /&gt;      those printed by the system when unusual events occur (such as when&lt;BR /&gt;      system tables overflow or the system crashes).  If the - argument is&lt;BR /&gt;      specified, dmesg computes (incrementally) the new messages since the&lt;BR /&gt;      last time it was run and places these on the standard output.  This is&lt;BR /&gt;      typically used with cron (see cron(1)) to produce the error log&lt;BR /&gt;&lt;BR /&gt;dmesg does put a timestamp to error message, the syslog will, in other words the error could be weeks old.&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;Robert-Jan</description>
      <pubDate>Fri, 27 Feb 2004 06:00:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204047#M167168</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2004-02-27T06:00:20Z</dc:date>
    </item>
    <item>
      <title>Re: Error dmesg command (type vxfs)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204048#M167169</link>
      <description>dmesg works only every few minutes while syslog works always.&lt;BR /&gt;If you make a&lt;BR /&gt;more /var/adm/syslog/syslog.log | grep -i vx_nospace&lt;BR /&gt;you should see the time when the error (file system full) occurred</description>
      <pubDate>Fri, 27 Feb 2004 06:29:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/error-dmesg-command-type-vxfs/m-p/3204048#M167169</guid>
      <dc:creator>Lorenzo Facello</dc:creator>
      <dc:date>2004-02-27T06:29:07Z</dc:date>
    </item>
  </channel>
</rss>

