Recently I went through the trouble of getting SAMBA to build with
support for XFS ACLs. I've a few questions regarding the combination
Linux-2.4, XFS-1.1 and SAMBA-2.2.
1. the current kernel I am using is the
kernel-2.4.18-SGI_XFS_1.1.i686.rpm found on oss.sgi.com. However,
there are several important patches for other things I'm doing which
are found in later kernels, especially important NFS patches (which
do affect us), but some other stuff as well. I would like to use a
2.4.20pre kernel but I have read in list archives that porting
XFS-1.1 (or current CVS) to this is difficult because of some aio and
other changes. Will SGI or anyone else be rolling up a recent kernel
any time soon which properly merges their XFS tree with recent
2.4-tree changes? I would attempt this myself but would probably
break something in some subtle fashion that I would only find out
when files become corrupted.
2. Does anyone have any idea how close the next release of XFS is (i.e.,
1.2 or what have you)?
3. am I better off using XFS from CVS or the XFS-1.1 release? I assume
XFS-1.1 has been regressed and there is some known list of bugs
somewhere perhaps? It looks to me like several important changes are
in CVS version when compared to the release-1.1.
4. does anyone currently use SAMBA with ACL support on Linux-2.4 with
XFS, in production use, that can relate how stable this combination
is? In particular for Windows clients, and with oplock support?
5. There have in the past (several months ago anyways) been
lockup/uptime problems with Linux-2.4 NFSv3 exports of XFS volumes.
Is anyone using this combination in production presently, and if so
do they have any problems?
6. Am I correct that XFS filesystems do not work off a Linux-2.4 native
software RAID volume, correct?
Thank you for any answers to these questions.