From: Matthias Schniedermeyer <ms@citd.de>
To: xfs@oss.sgi.com
Subject: inode64 and 64bit kernel with 32bit userspace
Date: Mon, 18 Feb 2013 10:43:20 +0100 [thread overview]
Message-ID: <20130218094320.GA24644@citd.de> (raw)
Hi
The more or less simple question is:
Is the requirement for 32bit programs to support 64bit inodes the same
as LFS(Large File Support)?
IOW if a programs was compiled with FILE_OFFSET_BITS=64 (if i remember
that name correctly) should it work?
So that all programs compiled in the last several years in a halfway
recent distribution should be able to cope with 64bit inodes?
The program i care about most is rsync and it appears to work correctly
when i tested it with 2 hard-linked files (with an inode >2^32) and the
option to preserve hard links. And "find" and "stat" also worked,
otherwise i couldn't have found the file to test it with. ;-)
--
Matthias
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2013-02-18 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 9:43 Matthias Schniedermeyer [this message]
2013-02-18 15:12 ` inode64 and 64bit kernel with 32bit userspace Eric Sandeen
2013-02-18 16:20 ` Matthias Schniedermeyer
2013-02-18 16:39 ` Eric Sandeen
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=20130218094320.GA24644@citd.de \
--to=ms@citd.de \
--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