From: Daniel Mack <zonque@gmail.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
ap@solarrain.com
Subject: Re: 3.4->(3.5.1 || 3.6-rc1) => can no longer mount 60TB ext4 filesystem
Date: Sun, 12 Aug 2012 15:31:57 +0200 [thread overview]
Message-ID: <5027B04D.3090703@gmail.com> (raw)
In-Reply-To: <005501cd77e7$d222d020$76687060$@lucidpixels.com>
On 11.08.2012 19:36, Justin Piszcz wrote:
> Hello,
>
> I upgrade to each new kernel release and with 3.5.1 (from 3.4) I can no
> longer mount my 60TB ext4 volume.
> If I boot back to 3.4, it works fine.
>
> Details here:
> https://lkml.org/lkml/2012/8/10/205
>
> Anything I can do besides testing each 3.5-rcX to find where the regression
> lies?
I'm not at all familiar with ext4 internals, but as always, an wasy way
is to bisect such a problem. Any change you can do that?
http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
Daniel
next prev parent reply other threads:[~2012-08-12 13:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-11 17:36 3.4->(3.5.1 || 3.6-rc1) => can no longer mount 60TB ext4 filesystem Justin Piszcz
2012-08-12 13:31 ` Daniel Mack [this message]
2012-08-12 13:52 ` Justin Piszcz
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=5027B04D.3090703@gmail.com \
--to=zonque@gmail.com \
--cc=ap@solarrain.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.