linux-ext4 - [Bug 25352] resizing ext4 will corrupt 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <201103311924.p2VJOAkM028050@demeter1.kernel.org>
Date:	Thu, 31 Mar 2011 19:24:10 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 25352] resizing ext4 will corrupt filesystem

https://bugzilla.kernel.org/show_bug.cgi?id=25352

--- Comment #17 from Martin Steigerwald <Martin@...htvoll.de>  2011-03-31 19:24:08 ---
Well I pretty much think that it was the same resize bug, but then it might as
well have been the BIOS thing (although I doubt it).

FWIW it was one machine, that ThinkPad T42, but different fsck.ext4 runs. When
the fsck.ext4 ran till the out of memory error the filesystem was unmountable
afterwards. When I quitted it before I was able to mount it.

Sorry for not using LANG=C with fsck.ext4, but at that time all I wanted is to
have my data back - nothing else mattered.

Anyway should I face an issue like that again, I will open a reparate bug
report and only hint that it might be the same problem as some other bug. I
also try to remember to use LANG=C.

So leave closed - I believe I hit that resize bug and all is well again.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
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