|
#1
|
|||
|
|||
sparse bundle slowness
I have a clone of my main hard drive stored on a NAS as a sparse bundle.
I use a different volume (just a bootable FW drive with my utilities on board) to boot from when performing a smart update. The sparse image has the same name as my main volume (hdd). The problem - if I mount the sparse image while booted from my main drive (clones of each other), the mounting takes about 3 minutes, then navigation of the image is very slow, then unmounting takes about 3 minutes again. Mounting/unmounting of the clone, when system booted from the external maintenance volume is near instantaneous. Is this expected? Would this be due to the volume/clone having the same volume name?? I restored the sparse image to a spare drive last night, and it seems to be fully intact.... |
#2
|
||||
|
||||
I don't have any idea why that would be - perhaps you're running some software that's interfering with networking, file access, etc?
Try starting up in, say, Safe Boot to see if that makes a difference.
__________________
--Dave Nanian |
#3
|
|||
|
|||
I'll try that, last night I deleted the old sparsebundle, and made a new one, with a name different to its parent volume.... still had trouble (slow) opening when booted from the volume it was cloned from.....
|
#4
|
|||
|
|||
Safe boot - can't connect to the NAS at all....
So a basic lion install on a FW drive can open/close these large sparsebundles without delay, and my main account on internal drive takes 2-3 minutes to do either.... An error I noted in console, which appeared at the end of the pause, as the image mounted: Apr 12 21:51:56 xxx-MacBook-Pro fseventsd[40]: event logs in /Volumes/FW800-backup/.fseventsd out of sync with volume. destroying old logs. (560 1 850) Apr 12 21:52:00 xxx-MacBook-Pro fseventsd[40]: log dir: /Volumes/FW800-backup/.fseventsd getting new uuid: 04C3AC65-EF65-4F4E-8EE9-62FED2737EEA Any ideas? I've also disabled time machine and spotlight with no change..... |
#5
|
||||
|
||||
The implication to the above is that the drive was incorrectly ejected, and that it needed a new fsevent database. That also likely means the delay in mounting is because it's doing an fsck on the volume.
__________________
--Dave Nanian |
#6
|
|||
|
|||
Possibly - I think I restarted the sucker while waiting for it to eject before - but this behaviour is every time I try and mount from my main account. Every time I try and mount from a different user on my main drive its perfect, as it is from a different boot drive....
Are there any preference files you think I should delete? - seems like a problem with this user account.... (I realise this isn't a SD! fault, but really do appreciate your help!) |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
sparse bundle error | jmwilder | General | 31 | 11-28-2010 04:17 PM |
sparse image vs. sparse bundle | johncarn | General | 1 | 05-06-2010 09:14 AM |
sparse images, sparse bundle images, and encryption | nephdoc | General | 3 | 01-20-2010 03:04 PM |
SD not unmounting sparse image volumes | acronce | General | 1 | 09-14-2008 11:22 AM |