Here's a bit of a puzzler.
I've got Ross's 9.2.2 v9 build ticking away nicely on both of my G4 Minis in a dual-boot setup - 120GB SSD, triple partition prepped with Drive Setup 1.9.2, 10GB for OS9, 16GB for 10.4.11 (the 9 partition is mounted read-only under X via fstab so no interference) & 80GB of HFS Extended (no journalling) as a workplace for both OSes. Other than the standard quirks associated with 9 on the Mini, everything has been working perfectly for many months ... except for this little problem.
Occasionally, a sub-folder on the shared-space will become locked, and once locked, there's absolutely no way to unlock it from OS9 - it and its immediate contents are immutable, un-trashable, although any deeper sub-folders are fine (see the attached image). If I boot into Tiger, there's absolutely nothing wrong with the 'locked' folder, it behaves like any other r/w item, with Disk Futility and DiskWarrior 4 both giving the workspace volume a clean bill of health, no b-tree hiccups, no broken custom icon alerts, nothing. (Yes, I know full well never to use an OS9 disk-fixer utility on a drive also used by OSX. The workspace behaves well under both 9 & X except for this odd locked-folder issue.)
So far, my only recourse is to make a note of the folder path so that the next time I boot Tiger I can make a new folder next to the locked-in-OS9 one, drag over the contents & trash the offender, and the next time I'm in OS9 things are back to normal, even if I give the made-in-OSX replacement folder the exact same name as its locked-in-OS9 predecessor.
I've examined the locked folder with DiskTop, can't see anything odd, no locked flag no shared bit set, et cetera (not that I expected it to, considering XATTRs are in play). I've used TinkerTool System to remove & disable ACLs on the workspace volume, ignored ownership, force-propagated permissions, none of which unlocks a 9-locked folder nor stop it from reoccuring when in 9.
It isn't a life-shattering problem, but it's one that happens once a day or so, and it's always a different folder somewhere else in the tree. I just work around it until the next OS-switcheroo.
But I am absolutely perplexed as to WHY this is happening. It is undoubtedly something screwy with the extended attributes stuff Tiger's got going on that's making OS9 unhappy, but I'm not that clued in on the innards of file-system mechanics.
If there's a fix it would certainly make me happy, but I'd just really like to know what's going on - any light that can be shed and improve my understanding will be extremely appreciated.
H