From mboxrd@z Thu Jan 1 00:00:00 1970 From: Oscar Megia Subject: Re: BUG EXT3-fs: fragsize 1024 != blocksize 4096 (unsupported) Date: Tue, 6 Apr 2010 21:35:09 +0200 Message-ID: References: <20100317162439.GC5799@quack.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-fsdevel@vger.kernel.org To: Jan Kara Return-path: Received: from mail-bw0-f209.google.com ([209.85.218.209]:60608 "EHLO mail-bw0-f209.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756736Ab0DFTfl convert rfc822-to-8bit (ORCPT ); Tue, 6 Apr 2010 15:35:41 -0400 Received: by bwz1 with SMTP id 1so221503bwz.21 for ; Tue, 06 Apr 2010 12:35:39 -0700 (PDT) In-Reply-To: <20100317162439.GC5799@quack.suse.cz> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Yes, it was a problem with the ATX power supply. I replaced it and now is working fine. I did what you told and I recover my important data but not all fs. The matter is if you have a hardware fault the ext3 journal fs don't preserve your data. I'm not an expert about the journal ext3 fs but I though is designed to preserve data so if the HD has a fault, ext3 must preserve your data. If the fault is during updating the main fs it must go to the previous main fs. This could happen when there is a power cut. Regards Oscar. 2010/3/17 Jan Kara : > =C2=A0Hi, > > On Tue 16-03-10 13:05:09, Oscar Megia wrote: >> Since three days ago mi PC with Fedora 9 started to do random resets= =2E >> >> I started to change the BIOS configuration and one of this changes l= eaved >> the screen black. Unfortunately, I pressed the reset button thinking= that >> didn't boot but the next time (after leave the BIOS configuration li= ke >> before) the system didn't boot. > =C2=A0I'd check your HW - memory, power supply, ... Obviously somethi= ng got > wrong. > >> It showed me this message: "EXT3-fs: fragsize 1024 !=3D blocksize 40= 96 >> (unsupported)" (you can see two pictures booting with this error at >> http://forums.fedoraforum.org/attachment.php?attachmentid=3D19240&d=3D= 1268739264 >> and http://forums.fedoraforum.org/attachment.php?attachmentid=3D1923= 9&d=3D1268739254). >> >> Researching I could get info from the root fs with dumpe2fs: > ... >> >> hda1 is for boot and hda2/lvm/ext3 with the OS and=C2=A0 data. If th= e ext3 >> has journal, is this a bug in the ext3 journal filesystem? > =C2=A0I'd say it is a faulty HW, not a software bug. > >> My question is how can repair this lvm/ext3 volume without loose dat= a? > =C2=A0I would first try to identify faulty HW (run memtest from a res= cue CD > for example). When HW gets fixed, I'd copy the filesystem with 'dd' t= o a > different disk as a backup. Then run e2fsck to fix /dev/hda2. > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0Honza > -- > Jan Kara > SUSE Labs, CR > -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html