From: Martin Subject: Re: Apparent serious progressive ext4 data corruption bug in 3.6.3 (and other stable branches?) Date: Wed, 24 Oct 2012 19:38:15 +0200 Message-ID: <50882787.3030504@onlinehome.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Nix , linux-ext4@vger.kernel.org, tytso@mit.edu, stable@vger.kernel.org, gregkh@linuxfoundation.org To: Linux Kernel Mailing List Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On 10/24/2012 01:40 AM, Nix wrote: > It's true that in less than a week > probably not all that many people have rebooted often enough to trip > over this. > > I hope. > Fwiw, i got a fried root filesystem (ext4) on one machine last week. It was on 3.5.3 or 3.5.5. Since there was nothing in the logs and the kernel was modified (CK, BFQ) and tainted (nvidia) I did not notify any maintainers. I have not had the time yet to rebuild the machine (unfortunately that will be laboursome), so the users cannot do their homework or attend to their social life for the time being... The pattern was indeed characterized by a sequence of reboots (I am told), and in a weird fashion files started to disappear from the root filesystem (I first noticed /etc/groups missing, and after further fscks and reboots login became impossible (I assume that /etc/passwd and or /etc/shadow are buggered). I haven't assessed the extent of the damage yet. Still not sure whether it is related to the bug in question, of course. Martin