I built a kernel with options APPLE_UFS and mounted a filesystem created
on MacOS 10.4.10 (x86).  Mounting read-only worked fine.  Mounting read-write
emitted messages from the FFS snapshot code about "non-snapshot inode 64"
and "non-snapshot inode 16384".

Are these inodes reserved by the snapshot code?  If they are, is it safe
to have the snapshot code in our default kernels, which can mount (much)
older FFS filesystems that may have these inodes in use?

-- 
Thor Lancelot Simon
Coyote Point Systems, Inc.			<tls@coyotepoint.com>
Millerton, NY, USA