From: Michael Weissenbacher <mw@dermichi.com>
To: Olaf Weber <olaf@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Eric Sandeen <sandeen@sandeen.net>,
xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH, RFC] default to inode64 on 64-bit systems
Date: Tue, 07 Jul 2009 12:12:59 +0200 [thread overview]
Message-ID: <4A531FAB.3050406@dermichi.com> (raw)
In-Reply-To: <bzyhbxoc1hi.fsf@fransum.emea.sgi.com>
Hi!
> Making inode64 the default on 64 bit systems seems like a good idea to
> me. But would it not be advisable to have a mount option that forces
> the old behaviour, just in case? Something like "broken32bituserspace"
> (or maybe "inode32").
>
I think such a mount option would be a must. There is lots of 32-bit Software that cannot cope with 64-bit inodes. Unfortunately there are closed-source 32-bit apps (which can be run on 64 bit systems) where nothing can be done for 64-bit inode compatiblity in the short term. Had this problem very recently with the Zmanda Enterprise Backup Software, which forced me to remove the inode64 option.
regards,
Michael
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-07 10:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 18:25 [PATCH, RFC] default to inode64 on 64-bit systems Eric Sandeen
2009-07-06 18:42 ` Christoph Hellwig
2009-07-07 8:59 ` Olaf Weber
2009-07-07 10:12 ` Michael Weissenbacher [this message]
2009-07-07 9:38 ` Matthias Schniedermeyer
2009-07-07 14:06 ` Eric Sandeen
2009-07-07 18:13 ` Matthias Schniedermeyer
2009-07-07 18:17 ` 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=4A531FAB.3050406@dermichi.com \
--to=mw@dermichi.com \
--cc=hch@infradead.org \
--cc=olaf@sgi.com \
--cc=sandeen@sandeen.net \
--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