| 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
| ||
|
Message-ID: <CAO9zADzpVeeQqcm78GK-Y562ieS6i5wnan7roCCwm0KLY0vdUA@mail.gmail.com> Date: Sun, 12 Aug 2012 09:52:43 -0400 From: Justin Piszcz <jpiszcz@...idpixels.com> To: Daniel Mack <zonque@...il.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 Sun, Aug 12, 2012 at 9:31 AM, Daniel Mack <zonque@...il.com> wrote: > 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 > Hi, Thanks, will save this for the future-- would of done this but Eric Sandeen found the offending patch, I reverted it and I can mount the filesystem now. The bad commit was 8aeb00ff85ad25453765dd339b408c0087db1527 (per sandeen) Justin. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists