On Thu, 7 Feb 2008, M. Warner Losh wrote:Not picking on anyone in particular, but let's keep in mind that this was an enquiry not a real proposal to axe it right away. I suggested Attilio find out if there were users and clearly there are. So there is value in keeping this thing working and fuse isn't a sure bet. We just wanted to understand the situation before acting. However, this is open source. Some one needs to step up to the plate and fix these bugs. It's only 4,700 lines of code. It shouldn't be insurmountable for someone who has a passing understanding of VFS. Some of the bugs were exposed by better asserts and witness support by Attilio. I don't think his effort to fix lockmgr should be hung up trying to understand ntfs however unless he directly broke it. It's going to have to continue firing asserts until someone fixes it. Also, ntfs is a strange bird compared to other filesystems. Briefly looking at it, there may be some subtle architectural problems with it. For example, it creates 'ntnode' inodes that aren't associated with vnodes and so have their own lifecycle management. It is likely that this is the source of the panics that I have heard of. An eager volunteer might also consider making it MPSAFE to further reduce the number of filesystems which require Giant so we can eventually drop the hideous giant wrappers. Cheers, Jeff _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to "firstname.lastname@example.org"