Before I retired I had a samba server running using xfs so get the acl's to work. This machine was server docs to a few hundred employees without any problems. Think about it, if it was such a hugh issue SUSE -would not- allow it in the distribution since SUSE is about quality (that's why I use SUSE).
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
I just searched the xfs mailing list to see if the issue had been addressed. I found a full thread discussing it from a year ago: http://oss.sgi.com/archives/linux-xfs/2005-02/msg00086.html If you read it, you will see that the XFS team basically say the performance of XFS would be greatly degraded if they eliminated the window of opportunity. They describe the window as possibly being minutes long between a Meta-Data update that increases the filesize and the actual data being flushed to disk. A common activity that does this is saving a file in vim. When vim does a save the file will either be truncated to zero length and rewritten or ithe original will be renamed and a new file created and written to. Either way you have a multi-minute opportunity to have the file null filled. There was also a off the cuff reference to it last month, so I'm convinced it is still there and not significantly changed from the 2.4 kernel code I still use. Greg