Hi Folks, We were smitten by a rather subtle change in how 12.3-64 mounts XFS files systems. The first indication was a failure of acroread to start for a particular user. Other users on the same system weren't affected. It turns out it's an old problem talked about here: http://forums.adobe.com/message/4721987 We then encountered another problem with an old cross-compiler that was caused by the same issue. It seems that when an XFS file system is mounted with the inode64 option, and the file system exceeds 1-TB, inode numbers exceeding 32-bits can be created. Without the inode64 mount option, inodes are clustered to be addressable by 32-bits. 12.2 and earlier mounted XFS without the inode64 option, as shown here: (12.2 mount command) /dev/sda7 on /export/home type xfs (rw,relatime,attr2,delaylog,noquota) While on 12.3: /dev/sda7 on /export/home type xfs (rw,relatime,attr2,inode64,noquota) Our workaround is to stop using XFS for home directories. We'll continue to use XFS for huge RAID arrays handling lots of large files. This isn't a bug in openSuSE, IHMO, just a change that illuminates bugs in other 32-bit packages. My thanks to Dan L. who "found" the solution. (Dan isn't on this list) Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org