From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>, xfs@oss.sgi.com
Subject: Re: inode64 question
Date: Fri, 26 Sep 2008 09:30:22 -0500 [thread overview]
Message-ID: <48DCF1FE.3080305@sandeen.net> (raw)
In-Reply-To: <20080926063050.GA20516@infradead.org>
Christoph Hellwig wrote:
> On Thu, Sep 25, 2008 at 07:44:33PM -0400, Justin Piszcz wrote:
>> If I mount the fs with -o inode64, can I mount it again later say under
>> knoppix 32bit without any options, will the FS still mount? The 64-bit
>> rescue cd/dvds--I have had problems with to say the least.
>
> Not yet. I'll hopefully get a patch for it into 2.6.28.
Actually it *will* at least mount, won't it? But that's dangerous. I
don't think xfs sets any kind of superblock flag saying "I contain
inodes past 2^32, don't mount on 32-bit boxes" does it?
-Eric
next prev parent reply other threads:[~2008-09-26 14:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 23:44 inode64 question Justin Piszcz
2008-09-26 6:30 ` Christoph Hellwig
2008-09-26 14:30 ` Eric Sandeen [this message]
2008-09-27 1:20 ` Dave Chinner
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=48DCF1FE.3080305@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.org \
--cc=jpiszcz@lucidpixels.com \
--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