Closed iJasonWade closed 1 year ago
What is the backing filesystem that is used on /dev/sdb? Are there really not any partitions? The only thing I can immediately think of is that samba is incorrectly interpreting the free space due to the filesystem but it's hard to say.
There is only one partition, it is an ext4
format, maybe I should format it again and create a partition?
Ah! I missed a small but very important detail. You're setting TM_USERNAME=jason
which means that your persistent data path is actually /opt/jason
in the container. Update your volume from:
- '/home/jason/mnt/timemachine:/opt/timemachine'
to:
- '/home/jason/mnt/timemachine:/opt/jason
Otherwise, it's detecting the amount of free space on the disk where Docker is and it will be storing data inside the container, not on a persistent volume.
/opt
. I also just added a check in #145 to output a warning message if the detected filesystem is overlay, which it would in most cases where the volume isn't mounted outside.Example output:
$ docker run -it --rm -e TM_USERNAME=jason mbentley/timemachine:test
...
INFO: xattr test successful - your persistent data store supports xattrs
WARN: Detected filesystem for /opt/jason is overlay! This likely means that your data is being stored inside the container, not in a volume! See https://github.com/mbentley/docker-timemachine#persistent-data-path
INFO: entrypoint complete; executing 's6-svscan /etc/s6'
...
Service "81cbde81ab4e" (/etc/avahi/services/smbd.service) successfully established.
Describe the Bug
I have a 6 TB hard drive I am using for timemachine, but when I connect to it from my Mac it only shows 85.2 GB available.
System Information:
Expected Behavior
Full available space is accessible.
Steps to Reproduce
Run docker-compose Connect to timemachine from Mac Observe available space
How You're Launching the Container
Container Logs
Additional Context
No response