| To: | Christoph Hellwig <hch@xxxxxx> |
|---|---|
| Subject: | Re: [PATCH 2/2] allow inode64 mount option on 32 bit systems |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Mon, 27 Oct 2008 12:21:25 +1100 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20081026203440.GC4173@xxxxxxxxxxxxx> |
| Mail-followup-to: | Christoph Hellwig <hch@xxxxxx>, xfs@xxxxxxxxxxx |
| References: | <20081026203440.GC4173@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Sun, Oct 26, 2008 at 04:34:40PM -0400, Christoph Hellwig wrote: > Now that we've stopped using the Linux inode cache when can trivally > support the inode64 mount option on 32bit architectures. As far as the > kernel and most userspace is concerned this works perfectly, but > applications still using really old stat and readdir interfaces will get > an EOVERFLOW error when hitting an inode number not fitting into 32 > bits (that problem of course also exists when using these applications > on a 64bit kernel). > > Note that because inode64 is simply a mount option we can currently > mount a filesystem having > 32 bit inode numbers and cause a variety of > problems, all this is solved but this patch which enables XFS_BIG_INUMS, > even when inode64 is not used. Looks ok. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 1/2] wire up ->open for directories, Dave Chinner |
|---|---|
| Next by Date: | Re: deadlock with latest xfs, Timothy Shimmin |
| Previous by Thread: | [PATCH 2/2] allow inode64 mount option on 32 bit systems, Christoph Hellwig |
| Next by Thread: | [PATCH 2/2] allow inode64 mount option on 32 bit systems, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |