Problem reading time machine volume on net being hosted by netatalk from my Lion machine (10.5 has no problem)

I have an OpenIndiana (ie Solaris) based server running Netatalk 2.2.x =
where x is the latest OI distribution as of a month ago.

(pkg list
service/network/netatalk (sfe)                    2.2.3-0.151.1.5        =
    i--
)

It has a bunch of ZFS volumes I use for various things -- media/music, =
data, and Time Machine.  It has been working fine for writing the =
backup.  I set up a user on the Solaris machine called "media" for the =
non Time Machine volumes and one called "timemach" for Time Machine use.

The AppleVolumes.default shares them as follows:

/volumes/TimeMachine/backups allow:timemach options:tm
/volumes/data/movies media allow:media
/volumes/music music allow:media

Each Mac is set to log in as user "timemach" and back up using Time =
Machine.  This works fine.  However, tonight I wanted to restore a file =
I accidentally overwrote.  I tried to enter Time Machine.  My Mac, under =
10.7.4, mounted the time machine backup from the Solaris box but did not =
enter Time Machine.  It did leave the backup file system mounted however =
so I went to it.  It contains one folder, Backups.backupdb and inside =
that is a folder with the name of the Mac.  That folder shows the red =
"do not enter" symbol on it and it says I have no access.  However, I =
can backup to it just fine (which is write access).  I have not tried =
other Lion machines since they are in use by others right now, but I =
tried a 10.5 machine I have that is also backing up to the same server =
through Time Machine.  It can read and write no problem.  It just seems =
to be Lion.  I know there were updates that made Lion Time Machine not =
work with netatalk but netatalk added the "options:tm" and I have that =
enabled to fix this, and I also enabled the dhx2 login stuff.  I CAN =
write the backups OK from Lion but for some reason cannot read.

I have NO PROBLEM reading and writing to the same netatalk server as the =
media user for the media file systems, where the only difference is the =
"options:tm" from the lion machine.

Anyone see this problem or a similar problem?

Thanks
Chad