Viewing 1 post (of 1 total)
  • Author
    Posts
  • #369599
    kray
    Participant

    I have an odd disk ussage problem that I need some advice about. This morning I notices that one of my disks is full. I have 3 disks on a 10.4.10 Server machine with the boot disk named “disk0”. The finder clained that the disk was full, as did the df command:

    truffula:~ root# df -h
    Filesystem Size Used Avail Capacity Mounted on
    /dev/disk0s9 234G 233G 0B 100% /
    devfs 110K 110K 0B 100% /dev
    fdesc 1.0K 1.0K 0B 100% /dev
    512K 512K 0B 100% /.vol
    /dev/disk2s6 931G 654G 278G 70% /Volumes/disk2
    /dev/disk1s9 234G 125G 108G 54% /Volumes/disk1
    automount -nsl [209] 0B 0B 0B 100% /Network
    automount -fstab [228] 0B 0B 0B 100% /automount/Servers
    automount -static [228] 0B 0B 0B 100% /automount/static

    After running du

    truffula:/Volumes/disk0 root# du -hd 1
    16K ./.Trashes
    2.0K ./.vol
    7.2G ./Applications
    1.5K ./automount
    3.5M ./bin
    16K ./cores
    2.0K ./dev
    3.2G ./Developer
    0B ./Groups
    3.8G ./Library
    44K ./Network
    21M ./opt
    5.2G ./private
    2.2M ./sbin
    1.6M ./Shared Items
    1.6G ./System
    63M ./Users
    16G ./usr
    975G ./Volumes
    1012G .

    the thing that jumps out at me is /Volumes sitting at the level of /Volumes/disk0/Volumes. Running ls shows:

    truffula:/Volumes root# ls
    .DS_Store HOME disk0 disk1 disk2

    which is what I expect and correct, but

    truffula:/Volumes/disk0/Volumes root# ls
    .DS_Store HOME disk0 disk1 disk2

    makes no sense. It is like there is a second copy the directory “Volumes” at the level of /Volumes/disk0/. However, there should not be room for a second copy of /Volumes there anyway since the entire disk0 is 234 G in size. and according to du -h, the directory Volumes is 975 G.

    Anyone have an idea as what is going on?

    Thanks in advance

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.

Comments are closed