| To: | Olaf Weber <olaf@xxxxxxx> |
|---|---|
| Subject: | Re: [PATCH, RFC] default to inode64 on 64-bit systems |
| From: | Michael Weissenbacher <mw@xxxxxxxxxxxx> |
| Date: | Tue, 07 Jul 2009 12:12:59 +0200 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs mailing list <xfs@xxxxxxxxxxx> |
| In-reply-to: | <bzyhbxoc1hi.fsf@xxxxxxxxxxxxxxxxxxxx> |
| References: | <4A52419E.5020301@xxxxxxxxxxx> <20090706184257.GA18107@xxxxxxxxxxxxx> <bzyhbxoc1hi.fsf@xxxxxxxxxxxxxxxxxxxx> |
| User-agent: | Thunderbird 2.0.0.22 (X11/20090608) |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH, RFC] default to inode64 on 64-bit systems, Matthias Schniedermeyer |
|---|---|
| Next by Date: | Re: [PATCH] xfstests: add test 215: c/mtime updates through mapped writes, Christoph Hellwig |
| Previous by Thread: | Re: [PATCH, RFC] default to inode64 on 64-bit systems, Olaf Weber |
| Next by Thread: | Re: [PATCH, RFC] default to inode64 on 64-bit systems, Matthias Schniedermeyer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |