OK long shot asking here but here goes.

One of my many scripts here uses vsdbutil to make sure owners are enabled on volumes before rsyncing. To do this it does a vsdbutil -c to check for owners enabled. If not, it uses vsdbutil -a to adopt them. (and then -c to check for success)

Problem. As of 10.6, apparently with server only, vsdbutil -c doesn't work. It says it can't find a database on that volume. The -a is working, it's just that the script thinks that all the volumes are disowned.

Just me? Workaround? tough luck?

apple:~ virtual1 $ vsdbutil -c /Volumes/Macintosh\ HD
No entry found for '/Volumes/Macintosh HD'.
apple:~ virtual1 $ echo $?
1

(this is the boot volume, obviously owners are enabled)

apple:~ virtual1 $ sudo vsdbutil -a /Volumes/Macintosh\ HD
Password:
apple:~ virtual1 $ echo $?
0

apple:~ virtual1 $ vsdbutil -c /Volumes/Macintosh\ HD
No entry found for '/Volumes/Macintosh HD'.

*sigh*

(affects all volumes, not just boot)

It's not having problems with the path. That produces different results

apple:~ virtual1 $ vsdbutil -c /Volumes/Macintosh\ HD123
vsdbutil: Couldn't get volume information for '/Volumes/Macintosh HD123': No such file or directory
vsdbutil: couldn't read volume UUID on '/Volumes/Macintosh HD123': No such file or directory



I work for the Department of Redundancy Department