Navigate to one of those items in the Finder, select it, and then choose Enter Time Machine from the Time Machine menu bar icon. Instead, use a utility like GrandPerspective or OmniDiskSweeper to identify folders or files that are both large and unnecessary. You have no idea what you’ll be deleting, and you’ll likely corrupt the entire Time Machine backup, rendering it useless. You might be tempted to look in the Backups.backupdb folder on your Time Machine drive and delete some of the dated folders inside. One possible solution-albeit likely a short term one-is to delete old backups. You have four options at this point, but two of them may not be all that helpful. When that happens, backups will start failing, and this notification will appear after every backup attempt.Ĭlick the Details button in that notification to open the Time Machine pane of System Preferences, and you’ll learn more. In general, this approach works well, since you probably don’t need all the older versions of changed files as long as Time Machine always retains the most recent version in the backup.Įventually, however, even this technique runs into the wall of hard drives having only so much capacity. It warns you when this starts happening and tells you what your oldest remaining backup is. So the first thing that Time Machine does when your backup drive fills up is start deleting those older versions, beginning with the oldest ones. If you modify the same file multiple times per day, every day, you’ll have numerous versions of it in your backup set so that you can go back to any particular version. After that, Time Machine keeps hourly backups for the past 24 hours, daily backups for the past month, and weekly backups for all previous months. On its first backup, Time Machine copies everything on your startup drive to the backup drive. What happens then?īefore we explain, some background. Time Machine is smart about backing up only files that have changed, but after months or years of usage, the drive will run out of space. 192.168.1.200/nas <- 'nas' is where you put your username because the TC creates that shared folder name when you create the User account via the Disk tab in AirPort utility.Įither change your username to 'nas', or change your destination folder to //192.168.1.200/airp-account-user.It’s inevitable-your Time Machine backup drive is going to fill up. It seems the username and the share in your IP/Destination_folder have to be the same, in your case: Save and reboot to make sure it re-mounts. If you want it to automount each time you reboot your *nix box, add an entry to your /etc/fstab (but I find that confusing), so I just added a cron task to re-mount at reboot using: crontab -eĪdd into your crontab the whole mount command above. Then try to mount it with this: mount -rw -t cifs //IP/username //mnt/timecapsule/ -o username=username,password=password,sec=ntlm,vers=1.0 On your *nix box, create a directory where you'd normally mount stuff, i.e. Once it's restarted, make sure you can ping it from your *nix box. Go to your TC, into Disk, click on Account and create a username and give it a password.

It would be great if I could get this thing up and running! Mount.cifs: permission denied: no match for /home/curruser/airport found in /etc/fstab When I try to use this mounting command without sudo (in an attempt to avoid the changing of ownership), I get the following error: I also tried adding rw as parameter, but this doesn't changes anything.

Sudo mount.cifs //192.168.1.200/nas /home/curruser/airport/ -verbose -o username=airp-account-user,pass=airport-account-passw,sec=ntlm,vers=1.0,gid=$(id -g), uid=$(id -u),forcegid,forceuid, file_mode=0777, dir_mode=0777 After remounting the disk the same thing happens all over again. When I unmount the disk and then change the owner, it works like normal and the owner is back changed to curruser.

I tried changing the owner of the folder, (sudo chown curruser /home/curruser/airptc), although this doesn't generate any errors it doesn't do anything. So after mounting, I can see and access the files in the target folder, but it is only readonly. The problem I have is that when I mount the disk to a local folder, that the owner of the folder always changes to root. I recently got a Apple airport time capsule and I am trying to use the disk as a NAS.