Orbi WiFi 7 RBE973
Reply

Re: Cleaning off old time machine shares

jhannah
Aspirant

Cleaning off old time machine shares

Hi! Thanks everyone on this great forum -- today I was able to upgrade to beta firmware, get Lion to work, run migration assistant via time machine, etc -- all stuff I could only do with this forum.

Anyway, my question:

I clearly have sparsebundles stored on the readynas time machine share taking up space, I would like to remove.

I'm not technical enough to do it via terminal, sorry.

I have been trying to access the "c" share via the Connect to Server option on Finder.
I connect to: smb://admin@19x.x.x.x/c/.timemachine

I enter my admin password, and it comes back to say:

When I do, it gives me this error:

"There was a problem connecting to the server "19X.16X.X.X. The share does not exist on the server. Please check the share name and try again."


Time machine backups are set up using the standard method on the ReadyNAS (just enabling time machine from frontview) so I would assume the sparsebundles are stored in the c directory as people say.

Any ideas for me?

Thanks!
Message 1 of 11
mdgm-ntgr
NETGEAR Employee Retired

Re: Cleaning off old time machine shares

Do you have the CIFS (aka SMB) service enabled under Services > Standard File Protocols on the NAS?
Message 2 of 11
jhannah
Aspirant

Re: Cleaning off old time machine shares

Yes I do have CIFS/SMB enabled
Message 3 of 11
jhannah
Aspirant

Re: Cleaning off old time machine shares

I'm not sure if this is relevant, but it was brought up in another thread: I currently have the Share security mode enabled. Apparently that's not best practice. Not sure what's involved with changing to user, but throwing that out in case it's relevant.
Message 4 of 11
mdgm-ntgr
NETGEAR Employee Retired

Re: Cleaning off old time machine shares

That would explain why you can't access the share using SMB.

Take a look at http://sphardy.com/web/usermode
Message 5 of 11
jhannah
Aspirant

Re: Cleaning off old time machine shares

thanks will try it!
Message 6 of 11
jhannah
Aspirant

Re: Cleaning off old time machine shares

Yes, this was the problem. Changing to user mode, and following the super helpful link provided above by mdgm, was easy and fixed the problem. Thanks guys.

Any suggestions of an easier way to delete these big sparsebundles? I left it overnight but it was still trying to kill it in finder and had to cancel to take my laptop. I read mention that finder is slow for this. Is there an easy alternative for a non-technical guy, or can someone give me quick and very explicit instructions on doing it using terminal? if it's complicated, no worries, I will just leave my computer doing it for a weekend or something at some point.

It seems like, in time, this would be a good feature to build into frontview, as I'm sure it's a fairly common issue of users (a) backing up timemachine to the NAS and (b) getting a new computer
Message 7 of 11
akaman
Aspirant

Re: Cleaning off old time machine shares

Any luck finding a fast way to delete a sparse bundle? I'm having a similar very slow (unresponsive?) process. Would love to a quicker way, like ssh in or something.

TIA, aka
Message 8 of 11
mdgm-ntgr
NETGEAR Employee Retired

Re: Cleaning off old time machine shares

Yes, the fastest method is using SSH:

cd /c/.timemachine
ls -la
rm -rf NAMEOFSPARSEBUNDLE.sparsebundle
Message 9 of 11
jhannah
Aspirant

Re: Cleaning off old time machine shares

fyi, I just let the finder delete run, killing two out of date computer files, maybe 200GB each.

ran for ~3 days but did successfully delete them.
Message 10 of 11
mdgm-ntgr
NETGEAR Employee Retired

Re: Cleaning off old time machine shares

Whilst SSH is fastest the next quickest would probably be to mount the share using CIFS, but then use the Terminal to do the deleting changing the work directory to /Volumes/c/.timemachine and delete it that way.

The advantage of SSH is that the deletions are done directly on the NAS but it does require that you know what you're doing when you use the command line. Also note that if problems are caused through use of SSH access support may be denied or a fee charged to attempt to resolve a problem.
Message 11 of 11
Top Contributors
Discussion stats
  • 10 replies
  • 3975 views
  • 0 kudos
  • 3 in conversation
Announcements