I was trying to get Time Machine working again on my OS X 10.7 (Lion) powered iMac, and a remote drive on airport base station, and the only solution that worked was the rename my .sparsebundle file on the hard drive to "INVALID.sparsebundle", so that it would start afresh on that volume.
The backup is a .sparsebundle (which is really a folder full of files) is about 400 gb in size. I tried this command this morning at 8 AM and at 6:30 PM it still has not completed:
sudo rm -rf INVALID.sparsebundle
Is there any way to know why it's hanging or what it's doing? There are all kinds of cool tricks possible in Mac OS X command lines and even using some of OS X's nice graphical tools, possibly involving the use of the GCC debugger, or dtrace, or maybe even some kind of kernel-monitoring process that can tell me what function call or syscall is currently executing.
I can locate the PID for the rm command:
$ ps aux |grep "rm -rf" root 392 0.0 0.3 2454248 20232 s001 U+ 9:08am 0:12.04 rm -rf /Volumes/Backup3tb/INVALID.sparsebundle
Is there anything I can do to find out what PID 392 is doing right now and whether it's truly hung or not? (I'm going to leave it overnight, and after 24 solid hours of not responding, I will consider aborting it, and if I do, I'm just going to format this volume.)
I tried iosnoop, like this:
$ sudo iosnoop -p 392 UID PID D BLOCK SIZE COMM PATHNAME
It's not showing me anything. I suspect that means that the process is well and truly Hung Up on something?