Netatalk, samba + osx file ownership problem

I am having a few problems with file permissions.
We a file server serving nfs v4 - and an ubuntu server which mounts it that runs netatalk v3.0.1
Seems that when a file is created via a NFS client, then modified by the
afp server, the perms go a bit screwy.
for example....
fred creates test.doc in the 'store' share, on a client with nfs it has these permissions
-rw-rw----   1 fred     testgroup       12 Dec 12 11:30 test.doc
When John edits it with a mac mounted via afp or smb it changes it to:
-rw-rw----   1 john    testgroup      12 Dec 12 11:32 test.doc
So test.doc when modified by a client with an afp or smb mount now belongs to john
Why does this happen?
here is a copy of my afp.conf
### Netatalk 3.0.1 config param's
# Global Parameters
[Global]
        log file = /var/log/netatalk/netatalk.log
        #log level = default:debug
        mimic model = RackMac
        #uam list = uams_dhx.so, uams_dhx2.so, uams_randum.so, uams_gss.so
        uam list = uams_dhx2.so, uams_gss.so
        k5 keytab = /etc/krb5.keytab
        k5 service = afpserver
        k5 realm = sumat.blah
# Volume default parameters
[default_for_all_vol]
        #file perm = 0664
        directory perm = 0774
        unix priv = yes
        convert appledouble = yes
        cnid scheme = dbd
        dircachesize = 131072
# File system mounts
[Homes]
        basedir regex = /home
       home name = home/$u
        valid users = @blah
        cnid scheme = tdb
        ea = none
[store]
        name = store
        path= /store
        file perm = 0640
        directory perm = 0755
        valid users = @blah
        cnid scheme = tdb
        ea = auto
This also happens to macs connect to a samba share so I'm wondering if I have to modify something in osx (10.8.2) ??

Similar Messages

Glibc update refusing to proceed. File ownership problem

So, I'm attempting to update glibc, and everything has been cleared out of /lib except the glibc libraries. According to "find /lib -exec pacman -Qo -- {} +" everything inside /lib is owned by glibc, but /lib is unowned. When I attempt to update, I receive the error: "glibc: /lib exists in filesystem"
How can I fix this?

So I read the wiki about the upgrade with /lib and glibc conflicting and I ran into such confliction during the second step.
pacman -Su
After running the first command listed, I get back:
error: cannot determine ownership of directory '/lib'
error: cannot determine ownership of directory '/lib/modules'
error: cannot determine ownership of directory '/lib/modules/extramodules-3.4-ARCH'
error: No package owns /lib/modules/extramodules-3.4-ARCH/fglrx.ko.gz
error: cannot determine ownership of directory '/lib/modules/extramodules-2.6.32-lts'
error: No package owns /lib/modules/extramodules-2.6.32-lts/fglrx.ko
error: cannot determine ownership of directory '/lib/modules/extramodules-3.2-ARCH'
error: No package owns /lib/modules/extramodules-3.2-ARCH/fglrx.ko
error: cannot determine ownership of directory '/lib/modules/3.0-ARCH'
error: No package owns /lib/modules/3.0-ARCH/modules.seriomap
error: No package owns /lib/modules/3.0-ARCH/modules.softdep
error: No package owns /lib/modules/3.0-ARCH/modules.alias.bin
error: No package owns /lib/modules/3.0-ARCH/modules.symbols
error: No package owns /lib/modules/3.0-ARCH/modules.alias
error: No package owns /lib/modules/3.0-ARCH/modules.symbols.bin
error: No package owns /lib/modules/3.0-ARCH/modules.dep
error: No package owns /lib/modules/3.0-ARCH/modules.pcimap
error: No package owns /lib/modules/3.0-ARCH/modules.inputmap
error: No package owns /lib/modules/3.0-ARCH/modules.isapnpmap
error: cannot determine ownership of directory '/lib/modules/3.0-ARCH/misc'
error: No package owns /lib/modules/3.0-ARCH/misc/vboxdrv.ko
error: No package owns /lib/modules/3.0-ARCH/misc/vboxnetadp.ko
error: No package owns /lib/modules/3.0-ARCH/misc/vboxnetflt.ko
error: No package owns /lib/modules/3.0-ARCH/misc/vboxpci.ko
error: No package owns /lib/modules/3.0-ARCH/modules.devname
error: No package owns /lib/modules/3.0-ARCH/modules.dep.bin
error: No package owns /lib/modules/3.0-ARCH/modules.ccwmap
error: No package owns /lib/modules/3.0-ARCH/modules.usbmap
error: No package owns /lib/modules/3.0-ARCH/modules.ieee1394map
error: No package owns /lib/modules/3.0-ARCH/modules.ofmap
error: cannot determine ownership of directory '/lib/modules/extramodules-3.3-ARCH'
error: No package owns /lib/modules/extramodules-3.3-ARCH/fglrx.ko
error: cannot determine ownership of directory '/lib/modules/3.2.6-2-ARCH'
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.softdep
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.alias.bin
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.symbols
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.alias
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.symbols.bin
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.dep
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.builtin.bin
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.devname
error: No package owns /lib/modules/3.2.6-2-ARCH/modules.dep.bin
error: cannot determine ownership of directory '/lib/modules/extramodules-3.1-ARCH'
error: No package owns /lib/modules/extramodules-3.1-ARCH/fglrx.ko
error: cannot determine ownership of directory '/lib/modules/3.0.21-1-lts'
error: No package owns /lib/modules/3.0.21-1-lts/modules.softdep
error: No package owns /lib/modules/3.0.21-1-lts/modules.alias.bin
error: No package owns /lib/modules/3.0.21-1-lts/modules.symbols
error: No package owns /lib/modules/3.0.21-1-lts/modules.alias
error: No package owns /lib/modules/3.0.21-1-lts/modules.symbols.bin
error: No package owns /lib/modules/3.0.21-1-lts/modules.dep
error: No package owns /lib/modules/3.0.21-1-lts/modules.builtin.bin
error: No package owns /lib/modules/3.0.21-1-lts/modules.devname
error: No package owns /lib/modules/3.0.21-1-lts/modules.dep.bin
error: cannot determine ownership of directory '/lib/modules/3.1.9-2-ARCH'
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.seriomap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.pcimap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.inputmap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.isapnpmap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.ccwmap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.usbmap
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.ieee1394map
error: No package owns /lib/modules/3.1.9-2-ARCH/modules.ofmap
/lib/libnsl-2.16.so is owned by glibc 2.16.0-1
/lib/librt-2.16.so is owned by glibc 2.16.0-1
/lib/libthread_db.so.1 is owned by glibc 2.16.0-1
/lib/libnss_dns.so.2 is owned by glibc 2.16.0-1
/lib/libcrypt.so.1 is owned by glibc 2.16.0-1
/lib/libnss_nis.so.2 is owned by glibc 2.16.0-1
/lib/libanl.so.1 is owned by glibc 2.16.0-1
/lib/ld-2.16.so is owned by glibc 2.16.0-1
/lib/libBrokenLocale-2.16.so is owned by glibc 2.16.0-1
/lib/librt.so.1 is owned by glibc 2.16.0-1
/lib/libcrypt-2.16.so is owned by glibc 2.16.0-1
/lib/libpcprofile.so is owned by glibc 2.16.0-1
/lib/libnss_hesiod.so.2 is owned by glibc 2.16.0-1
/lib/libnss_db-2.16.so is owned by glibc 2.16.0-1
/lib/libthread_db-1.0.so is owned by glibc 2.16.0-1
/lib/libnss_hesiod-2.16.so is owned by glibc 2.16.0-1
/lib/libc-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_compat-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nis-2.16.so is owned by glibc 2.16.0-1
/lib/libc.so.6 is owned by glibc 2.16.0-1
/lib/libnsl.so.1 is owned by glibc 2.16.0-1
/lib/libnss_files-2.16.so is owned by glibc 2.16.0-1
/lib/libcidn-2.16.so is owned by glibc 2.16.0-1
/lib/libm-2.16.so is owned by glibc 2.16.0-1
/lib/libresolv-2.16.so is owned by glibc 2.16.0-1
/lib/libutil-2.16.so is owned by glibc 2.16.0-1
/lib/libpthread-2.16.so is owned by glibc 2.16.0-1
/lib/libdl-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_dns-2.16.so is owned by glibc 2.16.0-1
/lib/libSegFault.so is owned by glibc 2.16.0-1
/lib/libpthread.so.0 is owned by glibc 2.16.0-1
/lib/libnss_files.so.2 is owned by glibc 2.16.0-1
/lib/libnss_nisplus-2.16.so is owned by glibc 2.16.0-1
/lib/libm.so.6 is owned by glibc 2.16.0-1
/lib/libanl-2.16.so is owned by glibc 2.16.0-1
/lib/libnss_nisplus.so.2 is owned by glibc 2.16.0-1
/lib/libBrokenLocale.so.1 is owned by glibc 2.16.0-1
/lib/libresolv.so.2 is owned by glibc 2.16.0-1
/lib/libnss_db.so.2 is owned by glibc 2.16.0-1
/lib/libutil.so.1 is owned by glibc 2.16.0-1
/lib/libdl.so.2 is owned by glibc 2.16.0-1
/lib/libnss_compat.so.2 is owned by glibc 2.16.0-1
/lib/libmemusage.so is owned by glibc 2.16.0-1
/lib/libcidn.so.1 is owned by glibc 2.16.0-1
/lib/ld-linux-x86-64.so.2 is owned by glibc 2.16.0-1
If I understand the wiki correctly. I can just move the files owned by glibck to /usr/lib and ignore the other files or delete them manually (which appears to primarily be the modules folder), right?

Directory/file ownership problem - restore Arch defaults?

A recent screw-up while changing from ext3 to reiser left everything on my system owned by tomk:users. (Clever me - if anyone needs a HOWNOTTO on this, I'll be glad to provide the embarrassing details :oops: ) Anyway, I chown'ed everything except $HOME to root:root, and it all seems to be running fine. However, I am of course aware that there are various other users and groups on the system, presumably for good reason. Where can I find out what should be owned by these users/groups? I reckon leaving everything root:root is probably not a good idea, right?

Thanks bardo (and cactus in the other thread). I ended up using cactus' suggestion, but in three stages, to solve the local package issue. First
pacman -Q | cut -f1 -d " " | tr "n" " " > install.list
then edit my own package names out of install.list, then
pacman -Sy `cat install.list`
Clunkier, certainly, but I felt happier that way - and that's what it's all about, isn't it?

Unable to download from AppStore, updates,etc.Messages 'the installer is damaged' to 'there might be a problem with file ownership and permissions.' I am the owner and only user of a new MBP. What could be going on?

Is anyone having the same type of problems I'm having with Lion. I have a new MacBook Pro, received 7 weeks ago, preinstalled with Leopard 10.6.7. I didn't migrate anything from my old iMac, wanted a clean install from the Apple Store. While there, I asked for the upgrade to Lion 10.7, however their system was down.
I installed it myself, wirelessly about a week later, and Apple emailed me a receipt. Now, I've had to call support directly last week when I lost Mail, Address Book, was unable to open Preview or iTunes, among other problems. Seemed fixed after a session that baffled even the store tech. Now I am unable to download or install the recent Mac updates for Lion, from the App Store, could not install Adobe Reader, etc. Messages range from 'A network error has occured - Check your Internet connection and try again' to 'The Installer is damaged and cannot open the package. There may be a problem with file ownership or permissions.' All fail and I'll probably have to call Apple again. I am frustrated beyond words. Logs 'Install's runner tool is not properly configured as a setuid tool', domain errors, 'attempt to write a readonly database, and on and on. I have barely done a thing on this computer except search online for help with these problems. Safari gives me a 'You are not connected to the internet' too often. Diagnostics disagrees. I do see wi-fi problems in the forum. Disk and permissions were fine at the beginning of the earlier problems, checked first by support tech. I'm not sure if support tech even knew. I was just happy they were fixed. Anyone have these download and/or install problems after a 'clean bill of health' so to speak, only a week ago?

Let's try the following user tip with that one:
"There is a problem with this Windows Installer package ..." error messages when installing iTunes for Windows

Why would an error pop up saying the installer is damaged. The Installer can't open the package. There may be a problem with file ownership or permissions. when trying to install java 7?

why would an error pop up saying the installer is damaged. The Installer can’t open the package. There may be a problem with file ownership or permissions. when trying to install java 7?

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Select
/var/log ▹ install.log
from the hierarchical list on the left. If you don't see that list, select
View ▹ Show Log List
from the menu bar. Then select the messages from the last installation or update attempt, starting from the time when you initiated it. If you're not sure when that was, click the Clear Display button in the toolbar of the Console window and then try the installation again.
Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).
If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting.

Mac OS 10.7.4, installing Microsoft Office 14.2.7, error "The Installer can't open the package. There may be a problem with file ownership or permissions."

Mac OS 10.7.4, updating new version Microsoft Office 14.2.7, ERROR "The Installer can’t open the package. There may be a problem with file ownership or permissions."
The Apple Installer version is Version 5.0.1 (537).
When I check the Installer Log, I find only these two messages that I do not understand.
Jul 12 09:29:13 Bruces-MacBook-Pro Installer[423]: Install's runner tool is not properly configured as a setuid tool.
Jul 12 09:29:13 Bruces-MacBook-Pro Installer[423]: Unable to create InstallController
I changed all the permissions for all the Microsoft Office Folder users to Read and Write.
Restart, same error

See:
https://discussions.apple.com/thread/1948155?threadID=1948155&tstart=1
I had identical Installer Log failure notices: I used Houdini to view the invisible files and per Limnos' suggestion cautiously dragged
user > library > preferences > com.apple.installer.plist out of that folder onto my desktop and double-clicked on the .pkg file again and it opened and installed properly.
My Installer now works properly on all .pkg files.

File permission and ownership problem

I am trying to resolve some file permission and ownership problems that are left over from using Migration Assistant to set up my iMac from an older iMac. In a terminal session when I use the ls -l command I'm getting a file/directory owner of 504. Sometimes the group is admin and sometimes the group is also 504. I think this is because the owner of the file on the old computer is not present in the new one but I want to be sure before I just change the owner and group.

The following should give you an indication->
id -un 504
or you could try->
dscl . list /Users UniqueID | grep 504 && echo "User exists" || echo "User does not exist"

Undetectable / Irreparable File corruption problems lead to OSX hanging

Hi,
I have a Samsung 500Gb 5400rp disk in my MBP17 ( 2007 ).
Certain files appear to be corrupted.. ie. you try to open them and the whole Mac freezes for 30-40 seconds.
Disk Utility cannot detect a problem, nor can Diskwarrior. I've tried repairing permissions, repair disk, rebuild HFS directory, scan files for problems.. these erroneous files don't get detected at all.
Just try to open one and Finder/OSX hangs for ages. File copy programs just hang for ages including Migration Assistant, Finder Copy.
So migrating from my MBP17 to my new i7 MBP17 doesn't work at all due to these "ghost" file.
Appreciate any suggestions for how to get my files across to my new MBP.

Delete the corrupt files before migrating.

Task or script to monitor file ownership, permissions and change as needed

I'm using a Mac OS X Tiger (10.4.9) computer as a file server for a group of people who are (1) individually non-administrative users and (2) members of Groups. The hard drive is partitioned into 2 volumes: Vol1 has no non-admin access, Vol2 has a Shared folder containing folders with files intended for either Public or Private access. I'm admin with UID=501 and trying not to be a danger. Each other user has a unique UID. Each Group has a unique GID. The folder that all users have access to is named Pub_shares. Every user allowed to access Pub_shares is a member of PubGroup (GID=505).
Now when a user accesses a file nested in Pub_shares, that file usually becomes owned by that user and the group membership may change from PubGroup and may undergo a change to "Read only" or "No Access." Since all members of PubGroup should have Read & Write access to files in Pub_shares, this is a problem. All files in Pub_shares, regardless of who last touched them, should remain:
Owner = chris / Access Read & Write
Group = PubGroup / Access Read & Write
Others = No Access
I've read some about Ownership & Permissions. I've seen it suggested that an admin set up an automated task, say to run every 3 minutes; that task checks file ownership and permissions and, if different, changes the values recursively to those shown above, such that:
Owner = 501 / Access = rwx
Group = 505 / Access = rwx
What do I need here? An Automator workflow? A shell script? AppleScript? Cron? launchd? How do I put this together? I don't know the syntax or the expressions to use. Any help is much much appreciated. [Note again: My "server" runs Tiger 10.4.9.] Thanks.

..."I have some Windows users (trying) to access shared files. Will the afp inheritance options stand up to a Windows user?"...
No the afp inherit settings won't apply to windows sharing, but I think there are equivalent settings that can be applied to smb.
..."I thought, too, I'd read somewhere that inheritance options use the topmost volume folder to set inheritance patterns."...
I am not able to double-check this for Tiger, but I don't think that is the case. As far as I know, with those settings enabled (and it doesn't work reliably if only one is enabled) permissions and ownership should be inherited from the folder that the items are added to.
..."My topmost folder on vol2 is "Shared" but it contains both Pub_shares (accessible by members of PubGroup) and a few Private_shares (folders accessible by members of various private groups)."...
Sorry I missed that point in your earlier post. The above would cause complications if a user were to move items from the private area to the public area. The inheritance only applies to when files are created, so something moved from the private area to the public area would retain its original permissions. To make it work, the public and private areas would have to be set up as separate shares, rather sharing the whole volume.

File Info problem

I have just recently upgraded from a Windows XP Pro desktop to a Vista Premium Laptop. I store all my MP3's (200GB+) on an external hard drive which is backed up on a second.
I used the following programs on XP:
CD Grabber
MediaTagger
iTunes
Now when I come to access my mp3's on Vista using these programs I have the following problems:
* When I try to edit the file info in iTunes the fields are grayed out and I cannot edit them.
* When I open Media Tagger manually and edit the files I get a message saying I cannot access this file.
All the MP3's play fine and I can edit any new files I have ripped or downloaded.
I believe the problem may be something to do with file ownership. Can anybody advise?

Yes, this is most likely a folder permission issue, Vista is very fussy about that.
Your account needs to have full control of your iTunes Music folder.
There is help on permissions here:
http://windowshelp.microsoft.com/Windows/en-US/Help/2464a180-e5dc-45d1-a2b8-3c8a 2b571e9d1033.mspx
http://www.mydigitallife.info/2007/05/25/how-to-take-ownership-and-grant-permiss ions-in-windows-vista/

CS1 and CS2 InDesign file type problems and Tiger

Dual 2.7GHrz G5, 2GB RAM, OSX 10.4.5
Previously, InDesign 3 (CS1 version) was installed on this Mac. I needed to install the full CS2 package. Everything installed just fine. The problem I am having is the file type associations. The Mac now sees CS1 InDesign files as Indesign CS2 files. I got info on a file I knew to have been created and saved in InDesign CS1. I changed the "open with:" to InDesign CS and it worked until I hit "Change all". It then reverts back to a CS2 file type. On other sites I found some different things to try like rebuilding or deleting the LaunchServices pref files, checking to see if their was a CFBundleIdentifier, etc. Anyway, what I seem to have found is that Tiger gets confused when the Type and Creator are the same in the info.plist files. Panther, however, does not seem to have this same problem. We have 10+ other G5's of similar hardware specs as the one listed above, running Panther 10.3.9, have CS1 and CS2 installed, and we are not having the same file type problems.
As a test, I modified the CFBundleIdentifier to be different than the one found in the CS1 info.plist, and it let me "change all" the CS1 files to CS1. Of course, CS2 files could not be associated with CS2 now.
Is there a fix for this? Or, is there a patch being worked on that will fix this problem? We really need to keep both versions of the software installed, and I don't want to have to rely on users making the decision about what version they are working in.
Tom

If Get Info shows both app versions (& it should) as "Open with:" choices, you can at least still set individual docs to open with the preferred version. Instead of having to open Get Info windows, you can do the same thing a bit more easily with the contextual menu that pops up when you right (or CMD) click & hold on a Finder document icon.
Normally, the "Open with >" choice in this menu is a one time thing, but if you hold down the option key, it changes to "Always Open With >" & makes the new app choice permanent as it opens the doc, all in one step.

Wireless/airdrop/file sharing problems

Wireless/airdrop/file sharing problems
I operate an IMac 3.06GHz and an Airbook 1.4 GHz
I frequently need to transfer files between the two, and in OSX 10.6, did so by setting the iMac to share the wireless connection and using drop box
This no longer functions in Lion (1.7.1).
Symptoms are:
1. Air drop simply does not function. Neither computer recognizes the other, even if they are adjacent.
2. The Airbook will recognize the wireless connection, and is able to connect with some programs, but not all.
3. For example, Safari is able to load news sites, but not gmail and a google search freezes, although a Bing search for the succeeds.
4. Turning both Firewalls off has no effect
5. Restarting both computers with new settings has no effect
6. Neither machine shows in the sidebar of finder, therefore I am unable to access one from the other directly.
Any ideas or back to Snow Leopard?

Wireless/airdrop/file sharing problems
I operate an IMac 3.06GHz and an Airbook 1.4 GHz
I frequently need to transfer files between the two, and in OSX 10.6, did so by setting the iMac to share the wireless connection and using drop box
This no longer functions in Lion (1.7.1).
Symptoms are:
1. Air drop simply does not function. Neither computer recognizes the other, even if they are adjacent.
2. The Airbook will recognize the wireless connection, and is able to connect with some programs, but not all.
3. For example, Safari is able to load news sites, but not gmail and a google search freezes, although a Bing search for the succeeds.
4. Turning both Firewalls off has no effect
5. Restarting both computers with new settings has no effect
6. Neither machine shows in the sidebar of finder, therefore I am unable to access one from the other directly.
Any ideas or back to Snow Leopard?

Can't change file ownership.

To be careful, I did a new install of Lion on a freshly formatted disk (by installing SL first, of course). One of the first things I tried was Aperture. My Aperture Library is on a separate (SS) disk. When I tried to launch Aperture, it knew where to look for the file (I used Migration Assistant to transfer preferences) but it said it could not open it because of some ownership problem. (I can not say exactly what, because now it will open - I don't know what changed.) However, I still can't change the ownership. Get Info thinks that the owner is the new dummy user I created when I first set up Lion (before Migration assistant), when I try to change the owner with the gear popup at the bottom of "Aperture Library Info", I get the error message "The operation can't be completed. An unexpected error occurred (error code -8076)."
"Unexpected", of course, is subjective. There is a reason I didn't jump to updating my system disk! I haven't tried repairing permissions, but I'm not optimistic about that.
When an "unexpected" error occurs, why doesn't it trigger an automatic report to Apple?

This program you recommend is fugly and complicated...
You should see the other way to do it!
Most likely...
When the 1st screen comes up, look for the Browse button, select the FAT drive, give it a Share Name, click the Windows (SMB) sharing bar & select Shared , enter your admin PW, click on "Show File System Properties", check Inherit Permissins, give the rights you need...
Any more questions after you Update Share...

Time Machine file owner problem

I have a Firewire drive connected to my iMac. I back up the iMac and a Macbook Pro to it. Due to problems with the MBP's wireless I fell back from 10.6.1 to 10.5.8. That didn't fix my problem so I went back to 10.6 after an erase and install of 10.5 and the upgrade to 10.6.
I just noticed a file owner problem with my Time Machine backups from the MBP. The laptop has one admin and two regular user accounts. The two regular accounts have the owners swapped so that when I enter TM and look through the backups of the home folders, the icons have a red do not enter sign.
I just went to the iMac and looked through the MBP's backup data with the root account. Some of the MBP files list an owner not even on the MBP, but on the iMac.
Long term I'd like to move the two computer's backups to separate partitions, but can I fix the ownership on the TM drive safely?

Steve_6 wrote:
I have a Firewire drive connected to my iMac. I back up the iMac and a Macbook Pro to it. Due to problems with the MBP's wireless I fell back from 10.6.1 to 10.5.8. That didn't fix my problem so I went back to 10.6 after an erase and install of 10.5 and the upgrade to 10.6.
I just noticed a file owner problem with my Time Machine backups from the MBP. The laptop has one admin and two regular user accounts. The two regular accounts have the owners swapped so that when I enter TM and look through the backups of the home folders, the icons have a red do not enter sign.
I just went to the iMac and looked through the MBP's backup data with the root account. Some of the MBP files list an owner not even on the MBP, but on the iMac.
Long term I'd like to move the two computer's backups to separate partitions, but can I fix the ownership on the TM drive safely?
do not change ownership of anything on the TM drive. if I understand you correctly the two standard accounts seem to own each others home directories on the backup, is this right? that can be easily fixed by swapping UIDs of those accounts. but i first want to make sure that I understand the issue correctly.

File ownership incorrect - can't login!

hi
i accidentally did a
chown -R <myaccount> /usr
on my Mac and now i'm unable to login to the system.
i've tried mounting the hard disk on another Mac using Firewire mount but unfortunately the file ownerships are all mapped to user nobody and doing a
chown -R root /usr
does not have any effect.
is it possible to disable the mapping to nobody?
i've also tried looking at the disk through Disk Utility. there's a "Repair Disk Permissions" button there but the button is disabled.
any ideas on how to fix this problem?
can i somehow enable the root account on my system?

i was able to fix this by unchecking the "Ignore ownership on this volume" checkbox which is visible when you choose Get info for the volume in Finder.
the option can be found under Ownership & Permissions / Details section.
after doing this was able to run
chown -R root usr

Netatalk, samba + osx file ownership problem

Similar Messages

Maybe you are looking for