From: Dave Chinner <david@fromorbit.com>
To: Marcin Sura <mailing-lists@sura.pl>
Cc: xfs@oss.sgi.com
Subject: Re: Quick way to check if 32bit app can work with inode64
Date: Wed, 21 Sep 2016 07:57:35 +1000 [thread overview]
Message-ID: <20160920215735.GK340@dastard> (raw)
In-Reply-To: <CACNifpWojiF5XKwNgORqXCyuceRsGNQA+wEDWKpxdoEvJQ6+-w@mail.gmail.com>
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@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2016-09-20 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 18:20 Quick way to check if 32bit app can work with inode64 Marcin Sura
2016-09-20 21:57 ` Dave Chinner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160920215735.GK340@dastard \
--to=david@fromorbit.com \
--cc=mailing-lists@sura.pl \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox