From: Chris Mason <chris.mason@oracle.com>
To: Keith Mannthey <kmannth@us.ibm.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [RFC][PATCH] Sector Size check during Mount
Date: Wed, 30 Nov 2011 10:06:48 -0500 [thread overview]
Message-ID: <20111130150648.GB24338@shiny> (raw)
In-Reply-To: <1322617452.10304.15.camel@keith-laptop>
On Tue, Nov 29, 2011 at 05:44:12PM -0800, Keith Mannthey wrote:
> Gracefully fail when trying to mount a BTRFS file system that has a
> sectorsize smaller than PAGE_SIZE.
>
> On PPC it is possible to build a FS while using a 4k PAGE_SIZE kernel
> then boot into a 64K PAGE_SIZE kernel. Presently open_ctree fails in an
> endless loop and hangs the machine in this situation.
>
> My debugging has show this Sector size < Page size to be a non trivial
> situation and a graceful exit from the situation would be nice for the
> time being.
Thanks. The large block size patches should finally go into 3.3, which
will make a big difference.
-chris
prev parent reply other threads:[~2011-11-30 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 1:44 [RFC][PATCH] Sector Size check during Mount Keith Mannthey
2011-11-30 15:06 ` Chris Mason [this message]
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=20111130150648.GB24338@shiny \
--to=chris.mason@oracle.com \
--cc=kmannth@us.ibm.com \
--cc=linux-btrfs@vger.kernel.org \
/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