linux-ext4 - Re: 3.4->(3.5.1 || 3.6-rc1) => can no longer mount 60TB ext4 filesystem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 12 Aug 2012 15:31:57 +0200
From:	Daniel Mack <zonque@...il.com>
To:	Justin Piszcz <jpiszcz@...idpixels.com>
CC:	linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org,
	ap@...arrain.com
Subject: Re: 3.4->(3.5.1 || 3.6-rc1) => can no longer mount 60TB ext4 filesystem

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

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html