On Tue, Sep 20, 2016 at 08:20:42PM +0200, Marcin Sura wrote: > Hi Specialists! > > I have a 32bit Java application reading and writing files to NFS share > mounted on Windows 2008R2 server 64bit. The filesystem behind NFS share is > of course XFS, created with default mkfs.xfs and mounted with inode64 > option. > > I don't have access to app source code. That won't help - who knows how windows API calls translate to NFS operations. > Is there a quick and fast way to check if the app can be safely used with > inode64? Can I somehow force the files to be created with 64bit inodes > number, so the app can read then? On the NFS server, create a multi-TB filesystem (>16TB to be sure), make a few hundred sub directories in the root, add a bunch of short files of known contents to each sub directory. Export. Mont it on the client, then check you can list and read all the files from the client, then have the client copy it all to a new set of subdirs, then verify the copy on both client and server. IF that all works, then there's nothing obviously wrong with client side NFS support handling inodes numbers larger than 32 bit. Now do the same thing with your java application, and see if it has problems listing and/or reading all the files... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
