Are you referring to the know issues with Norton Disk Doctor ?... It has been known to corrupt 9.2.2 volumes and that is why I removed it from the Norton Utilities that is uploaded... never any issues with defrag... anyway...
I won't beat this into the ground... The error I am referring to has happened on various music studio client's G4 also (not just mine) and they did not have Norton defrag loaded. I have seen it happen on a test bed Quicksilver from
10.4 just mounting the drive 1 time. If it never happens to you then that is awesome... I am just reporting what I have seen. I cannot duplicate the step. The data was still accessible, but my client had to bounce 70GB of Nuendo projects... I definitely did not ask him if we could try it a second time (after we got everything up and running) to see if we could "reproduce the error".... nor have I found a pattern... Some of my personal G4s... MDD, QS, TI and Cubes ran for months with no issues whatsoever... and randomly.... BAM.... same Btree error when running disk First Aid under 9.
I did note that the error has only occurred on volumes that were over 50% full... don't know if it is the number of files, custom icon, file name... I honestly do not know what triggers it.
As far as transferring large files & projects from OS 9 and OS X, I don't use Ethernet... I lied, I use a dedicated Lacie FW enclosure that I only use just for transfers... set it up it in 2009 and it has not suffered any ill effects... it never goes above 20% full (again don't know if that matters); at any rate, I never store anything I need on that drive so I am willing to re-initialize as needed. As far as my other macs... i am not looking forward to having to move Sample libraries and archived projects around if the error randomly crops up.
Just to clarify, I have NEVER lost any data, the btree error still leaves the volume assessable and the data can be copied elsewhere... I just gave up a long time ago mixing X since I was dealing with btree errors, custom icon issues, long files names (that now looked like gibberish in OS 9). Back in the day, this was just a personal decision.... I am NOT X-phobic... I use SL and ML on my newer macs, I just avoid mixing X and 9 whenever possible. Over the last 8 years My OS 9 units have never even had the smallest of issues (file system wise) since I used this approach, so I am sticking with it; my days of trying to track down what causes these issues, or reproducing them, are over.... I leave that to the young guys.
Just FYI, this EXACT ERROR has hit the apple forums over the years... check out these posts... hmmm, maybe I'm sane after all
https://discussions.apple.com/thread/118748?tstart=0
https://discussions.apple.com/message/2667224#2667224