| To: | <xfs@xxxxxxxxxxx> |
|---|---|
| Subject: | clarifications on inode64 mount option |
| From: | <Ivan.Novick@xxxxxxx> |
| Date: | Sun, 21 Nov 2010 19:12:38 -0500 |
| Accept-language: | en-US |
| Acceptlanguage: | en-US |
| Cc: | <Timothy.Heath@xxxxxxx> |
| Thread-index: | AcuJ2c9Z2ZV92l4DSLaqjfLLJM52bw== |
| Thread-topic: | clarifications on inode64 mount option |
| User-agent: | Microsoft-MacOutlook/14.0.0.100825 |
Hi all, My understanding from the documentation is that inode64 allows inode numbers to be 64 bits in size rather than the default of 32. Is this correct? Will the option work fine on 32 bit X86 builds? The documentation also says: "This is provided for backwards compatibility, but causes problems for backup applications that cannot handle large inode numbers." Is this a current issue? Any examples of backup applications that have trouble reading a file system that uses this option? Cheers, Ivan Novick |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] xfs: fix exporting with left over 64-bit inodes, Christoph Hellwig |
|---|---|
| Next by Date: | Re: [PATCH] xfs: fix exporting with left over 64-bit inodes, Dave Chinner |
| Previous by Thread: | [PATCH] xfstests 248: add test for fallocate with hole punching V2, Josef Bacik |
| Next by Thread: | Re: clarifications on inode64 mount option, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |