I did not think it was possible to create Time Machine backups for volumes other than the startup volume. Is this something unique to OS X Server?
I would keep re-running it until you start getting the same output. In your examples, the leaf record counts keep changing. To merge the data, you'd probably have to script this with a shell script. A fast but not entirely reliable method is to use diff -qr <directory1> <directory2> which will compare, line by line, each file and traverse subdirectories. It will only tell you that there is a difference, not what the difference is. To do that you'd use diff without -q but it will take a lot longer so first I'd find out which files are different, if any, then find out what the differences are. If you have database files, I would just run md5 on the two copies to see if they are different down to the byte level and if not, then consider the rabbit hole that would be using diff on a database to find out what the differences are, and if it's simple to fix or if your database has a capable repair utility for whatever damage there is. Chris Murphy On Mar 6, 2011, at 9:12 AM, Ashley Aitken wrote: > > Hi Neil, > > Thanks for your post. > > On 06/03/2011, at 10:50 PM, Neil Laubenthal wrote: > >> Sometimes you can't repair the disk if you're booted from it. > > This is not a startup volume, I always have my OS and general user data on > different volumes (and in this case disks). > >> Here are a couple things to try. >> >> 1. Backup the data portion of the drive using Finder Copy or CCC or >> something to a separate physical disk (2 copies if you have enough space). >> Verify the size and number of files in the original and backup drives to >> make sure you got everything. > > Comparing file numbers is a good idea but not sure where I will get that > detail from, seems to pass quickly in most tools. > >> 2. Run a Time Machine backup if possible. > > That failing is what set all this off - unfortunately I continued to use the > disk after TM failed to backup, not knowing if it was a TM problem or a disk > problem. > >> 3. If you're running MacOS Server . . .and are using Open Directory . . >> .export a copy of the database and any configuration files necessary for the >> server. > > I should do that again anyway, thanks for reminding me. > >> 4. Boot from the installation DVD and try running Disk Utility from there. > > Not sure if that will help because its not the boot volume or disk. > >> 5. Try another disk repair utility like DiskWarrior. > > I don't own that but I my data is obviously worth the price - I have heard in > the past though that it takes a lot of time and is not always successful (I > guess that's obvious). > >> What you have is some sort of directory damage . . .there isn't enough >> information to tell if the CCC copy is good . . .it likely is good but one >> or more files (the ones that have bad directory entries on the original >> drive) may be corrupted. > > Yes, this is what I was thinking too. I don't mind losing a small number of > files (I guess). Of course, it may depend on which ones they are ;-) > > Thanks for your suggestions. > > Cheers, > Ashley. > >> >> >> On Mar 6, 2011, at 9:28 AM, Ashley Aitken wrote: >> >>> >>> Hi All, >>> >>> Every summer I have disk problems on our SOHO server (probably because of >>> the excess heat and lack of fans on some external drives). >>> >> >> >> ----------------------------------------------- >> There are only three kinds of stress; your basic nuclear stress, cooking >> stress, and A$$hole stress. The key to their relationship is Jello. >> >> neil >> >> >> >> _______________________________________________ >> MacOSX-admin mailing list >> [email protected] >> http://www.omnigroup.com/mailman/listinfo/macosx-admin > > _______________________________________________ > MacOSX-admin mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/macosx-admin _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
