i have 30 file systems on my production system and my system is responding too slow and / is 99% full is there any way i can run the du -sh only on root file systems and skip all the SAN file systems as the system is unable to do du -sdh * / as it would try to run du on all the SAN/NAS file systems too.
Hi.
If I understand the man page correctly:
/usr/xpg4/bin/du -shx /*
might give what you want?
Can you housekeep you root filesystem first then redo du or df. If df still shows 99%, then you might need to check the open files in cache and fuser to track and kill open processes
i have already done housekeeping and still unable to find anything .. my /usr, /var, /tmp ,/export and they all are fine & how can i check open files in / .. i know i can do this with lsof but for /var or /usr not for entire root file system i would appreciate if you can help me on this
---------- Post updated at 06:01 AM ---------- Previous update was at 05:52 AM ----------
and one more thing i didn;t understand how to use /usr/xpg4/bin/du -shx /*
as my SAN file systems are vxfs and root file system are on zfs
rpool 132G 0 94K /rpool
rpool/ROOT 126G 0 18K legacy
rpool/ROOT/s10s_u6wos_07b 126G 0 126G /
rpool/dump 4.00G 0 4.00G -
rpool/swap 2G 2.00G 16K -
df -h /
Filesystem size used avail capacity Mounted on
rpool/ROOT/s10s_u6wos_07b
132G 126G 0K 100% /
It might be a ZFS snapshot.
What says
zfs list
or
zfs list -t all
?
$ zfs list -t all
invalid type 'all'
$ zfs list -r rpool
NAME USED AVAIL REFER MOUNTPOINT
rpool 132G 0 94K /rpool
rpool/ROOT 126G 0 18K legacy
rpool/ROOT/s10s_u6wos_07b 126G 0 126G /
rpool/dump 4.00G 0 4.00G -
rpool/swap 2G 2.00G 16K -
---------- Post updated at 06:17 AM ---------- Previous update was at 06:17 AM ----------
$ zfs list -t all
invalid type 'all'
$ zfs list -r rpool
NAME USED AVAIL REFER MOUNTPOINT
rpool 132G 0 94K /rpool
rpool/ROOT 126G 0 18K legacy
rpool/ROOT/s10s_u6wos_07b 126G 0 126G /
rpool/dump 4.00G 0 4.00G -
rpool/swap 2G 2.00G 16K -
as far as in can see there is no snapshot .. this was the first thing we checked
---------- Post updated at 07:04 AM ---------- Previous update was at 06:17 AM ----------
the /var/cores directory was the culprit and since i was using sudo with normal user i it was not showing me the contents of /var/cores ..
sorry for confusion .. this thread can be closed now.