HP-UX v11上明明只使用了10%，却报空间不足
HP-UX v11上明明只使用了10%，却报空间不足各位大哥，我的HP-UX v11上，有个/var的文件系统，空间有20G，通过bdf查看只用了2G，却不停的报：vx_nospace file system full 2 block extent
不知道是为什么呀 1. 这个报错是syslog.log一直报出来的还是你看dmesg看到的？如果是后者，检查一下最后报这个错的时间点是什么时候。
2. 如果是前者，使用下面的命令查一下体积最大的文件是哪些（顺便贴出下面命令的输出）。看看能不能删掉一些看看，然后再观察是否再报。
# bdf
# ff -s </var的lvol设备文件的绝对路径，比如/dev/vg00/lvol8> | sort -rnk 3 | more
3. 如果删掉一些文件后还是报，问HP要crashinfo的工具看看/var下面是否有些unlinked的文件被某些进程占用，有的话看看相应的进程是否能kill掉。 回复 2# lbseraph
回老大：
是dmesg报的，请问怎么看报错时间或者消除报错信息啊？
dmesg显示的是buffer里面的内容，查报错时间的话，就grep查一下syslog.log里面有没有一样报错内容的。如果要彻底刷掉dmesg的信息，还是抽时间重启OS吧，没有命令可以直接不显示旧报错的。
参考链接：
http://h30499.www3.hp.com/t5/System-Administration/Is-there-anyway-to-refresh-dmesg-output/td-p/2792557?profile.language=en l兄，我搞错了，仔细看了一下syslog.log里面也有报错的，而且是每天都在报，实在太奇怪了，明明只用了10%呀，具体请下面日志：# uname -a
HP-UX crstest B.11.31 U ia64 3709523152 unlimited-user license
# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 5242880278600 4925608 5% /
/dev/vg00/lvol1 2097152354240 1729376 17% /stand
/dev/vg00/lvweblogic
10485760 2555701 7456129 26% /weblogic
/dev/vg00/lvol8 20971520 2070528 18756600 10% /var
/dev/vg00/lvol7 10485760 3166528 7262144 30% /usr
/dev/vg00/lvol4 10485760741488 9668296 7% /tmp
/dev/vgtest/lvtest 839254016 367509977 442263179 45% /test
/dev/vg00/lvoracle 20971520 4000124 15910760 20% /oracle
/dev/vg00/lvol6 20971520 5922840 14931160 28% /opt
/dev/vg00/lvol5 5242880 20984 5181104 0% /home
/dev/vg00/lvdatastage
62914560 82064 58905472 0% /datastage
/dev/vg00/lvapache 1048576 17749966408 2% /apache
crsdsfs:/crsdata 314507264 106728141 194793054 35% /crsdata
# du -sk /var
1985768 /var# more /var/adm/syslog/syslog.log
Feb 16 11:27:06 crstest syslogd: restart
Feb 17 04:20:50 crstest vmunix: vxfs: NOTICE: msgcnt 1 mesg 001: V-2-1: vx_nospace - /dev/vg00/lvol8 file system full (2 bloc
k extent)
Feb 17 04:20:56 crstest vmunix: vxfs: NOTICE: msgcnt 3 mesg 001: V-2-1: vx_nospace - /dev/vg00/lvol8 file system full (2 bloc
k extent)
Feb 17 12:18:43 crstest vmunix: vxfs: NOTICE: msgcnt 5 mesg 001: V-2-1: vx_nospace - /dev/vg00/lvol8 file system full (2 bloc
k extent)
Feb 18 04:25:15 crstest vmunix: vxfs: NOTICE: msgcnt 7 mesg 001: V-2-1: vx_nospace - /dev/vg00/lvol8 file system full (2 bloc
k extent)
Feb 18 04:25:21 crstest vmunix: vxfs: NOTICE: msgcnt 9 mesg 001: V-2-1: vx_nospace - /dev/vg00/lvol8 file system full (2 bloc
k extent)
Feb 18 12:25:22 crstest vmunix: vxfs: NOTICE: msgcnt 11 mesg 001: V-2-1: vx_nospace - /dev/vg00/lvol8 file system full (2 blo
ck extent)
Feb 19 04:17:45 crstest vmunix: vxfs: NOTICE: msgcnt 13 mesg 001: V-2-1: vx_nospace - /dev/vg00/lvol8 file system full (2 blo
ck extent)
Feb 19 04:17:51 crstest vmunix: vxfs: NOTICE: msgcnt 15 mesg 001: V-2-1: vx_nospace - /dev/vg00/lvol8 file system full (1 blo
ck extent)
Feb 19 12:20:30 crstest vmunix: vxfs: NOTICE: msgcnt 17 mesg 001: V-2-1: vx_nospace - /dev/vg00/lvol8 file system full (2 blo
ck extent)
Feb 20 04:22:53 crstest vmunix: vxfs: NOTICE: msgcnt 19 mesg 001: V-2-1: vx_nospace - /dev/vg00/lvol8 file system full (2 blo
ck extent)
Feb 20 04:22:59 crstest vmunix: vxfs: NOTICE: msgcnt 21 mesg 001: V-2-1: vx_nospace - /dev/vg00/lvol8 file system full (2 blo
ck extent)
Feb 20 12:23:01 crstest vmunix: vxfs: NOTICE: msgcnt 23 mesg 001: V-2-1: vx_nospace - /dev/vg00/lvol8 file system full (2 blo
ck extent)
# ff -s /dev/vg00/lvol8 |sort -rnk 3 |more
./adm/cron/OLDlog 35 35741295
./opt/perf/datafiles/logproc 1110 32911964
./opt/ignite/recovery/2011-08-01,15:00/flist 43428 24405893
./opt/perf/datafiles/logglob 1108 24372228
./opt/ignite/recovery/2011-07-07,14:38/flist 37659 21965445
./adm/sw/save/PHKL_40650/VXFS-KRN/usr/conf/mod/vxfs50 19121 21477336
./adm/sw/save/PHKL_40640/VXFS-BASE-KRN/usr/conf/mod/vxfs 18795 20878312
./opt/perf/datafiles/logappl 1109 17544556
./opt/psb/db/pgsql/pg_xlog/0000000000000020 3329 16777216
./opt/psb/db/pgsql/pg_xlog/000000000000001F 3328 16777216
./opt/psb/db/pgsql/pg_xlog/000000000000001E 3327 16777216
./opt/psb/db/pgsql/pg_xlog/000000000000001D 3326 16777216
./adm/sw/save/PHSS_39650/KWDB-RUN/usr/contrib/kwdb/lib/kwdb.ia64.so 24854 16009352
./opt/perf/datafiles/logdev 1112 15875984
./adm/sw/save/PHSS_39650/KWDB-RUN/usr/contrib/kwdb/lib/kwdb32.so 24855 15830852
./adm/sw/save/PHSS_39650/KWDB-RUN/usr/contrib/kwdb/bin/kwdb.ia64 24842 15732840
./adm/sw/save/PHSS_39650/KWDB-RUN/usr/contrib/kwdb/lib/kwdb64.so 24856 15577252
./adm/sw/save/PHSS_39650/KWDB-RUN/usr/contrib/kwdb/bin/kwdb32 24843 15517184
./adm/sw/save/PHSS_39650/KWDB-RUN/usr/contrib/kwdb/bin/kwdb64 24844 15285828
./adm/sw/products/ProviderSvcsCore/PSB_CER/cerdump-min15989 14757888 那照第3步查一下先吧~ 仔细找找原因吧 在HPUX下有三种工具可以查找这些unlinked文件和它相关的进程，分别是crashinfo(4.45以上版本)、lsof、uli
crashinfo -unlinked
lsof +aL1 /var 1.4天的时间点很接近，是不是你的应用当时有动作，然后又释放了空间，如果一直有的话，报错应该是长期的。
2.inode是不是用完的，可以查看一下。
页:
[1]