Other Yet another / partition is full...

I am running ZFS on this machine but the OS is actually installed on a 120GB SSD. I am new to FreeBSD so bear with me. System working fine then went to install program and the package installer said no more room on disk and sure enough:

Code:
root@sls-nas4:/ # df -h
Filesystem          Size    Used   Avail Capacity  Mounted on
/dev/ada0s1a        111G    101G    1.3G    99%    /

I simply cannot find where the space is being used:

Code:
root@sls-nas4:/ # du -d1 -h -x /
4.0K    /.snap
512B    /dev
1.7G    /usr
4.0K    /media
 52K    /root
4.0K    /proc
 11M    /lib
139M    /boot
1.3M    /bin
2.9M    /etc
9.2M    /rescue
345M    /var
6.8M    /sbin
292K    /libexec
 80K    /tmp
 42K    /mnt
512B    /zfspool
2.3G    /

None of the utilities I use show where the over 95GB of data are being used? I have rebooted the machine and the used space was not released. I did read where someone suggested going into single user mode and running fsck which I will do shortly.

Does anyone have any further advice on how to track down where the space is getting used?
 
I did read where someone suggested going into single user mode and running fsck which I will do shortly.
This is the first thing I would do.

Theorethically you could have mounted a tmpfs over a /tmp (thus hiding the original /tmp content) but I have difficult to think a 95 GB of temp files ....
 
I am still not having much luck. Here are the results from fsck in single user mode:

upload_2017-1-6_9-32-37.png


Not sure if the UNEXPECTED SOFT UPDATE INCONSISTENCY is a critical issue. Too many hits on topic to really decipher with my limited knowledge.

Any further advice would be appreciated.
 
it appears your filesystem is mounted in READ-WRITE mode, you need to remount it READ-ONLY before running fsck -y /dev/ada0s1a:

Code:
mount -u -r /
fsck -y /dev/ada0s1a
 
I thought I did but apparently not. I have found the real issue and blame this on my ignorance somewhere.

I have my ZFS filesystems mounted under /mnt. I then checked under the /mnt location and somehow there were still files there. So apparently I somehow copied files directly to this mount point without it actually being mounted to the ZFS filesystem. Truly don't know how that happened, but I essentially had two copies of the data...one in the ZFS dataset and one at the mount location off of root.

Sorry for wasting everyone's time and thanks for help on this ASX.
 
Glad you found the culprit. Mistakes just happens.
As a side note, remember that /mnt conventionally is a temporary mount point and should not be used for a permanent setup.
 
As a side note, remember that /mnt conventionally is a temporary mount point and should not be used for a permanent setup.

You are right, but got so consumed in getting ZFS working I most likely did follow best procedure. Not to hijack my own thread but do you have general recommendation or mounting ZFS filesystems. Do you usually created a dedicated mount point for it on a dedicated partition or something similar?
 
Do you usually created a dedicated mount point for it on a dedicated partition or something similar?

Yes I do (and apply to any filesystem type), something like:
/music if I want to mount a filesystem containing music files available to all users
/vbox ... a container of virtual machines that can be mounted from a different OS when dual booting and thus require a filesystem type supported from both systems.
or
/usr/home/<user>/personal if I need something user specific.

Choice may vary, depending on filesystem content and intended use, there are no particular restrictions other than to not use mountpoints already intended for a some different use, like /mnt (temporary, for admin tasks) and /media (filesystem automounters).
 
Back
Top