From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kara Subject: Re: BUG EXT3-fs: fragsize 1024 != blocksize 4096 (unsupported) Date: Tue, 6 Apr 2010 22:05:52 +0200 Message-ID: <20100406200552.GF4420@quack.suse.cz> References: <20100317162439.GC5799@quack.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Jan Kara , linux-fsdevel@vger.kernel.org To: Oscar Megia Return-path: Received: from cantor2.suse.de ([195.135.220.15]:58945 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755842Ab0DFUFo (ORCPT ); Tue, 6 Apr 2010 16:05:44 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue 06-04-10 21:35:09, Oscar Megia wrote: > Yes, it was a problem with the ATX power supply. I replaced it and no= w > is working fine. >=20 > I did what you told and I recover my important data but not all fs. >=20 > The matter is if you have a hardware fault the ext3 journal fs don't > preserve your data. >=20 > 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. Ext3 journal prevents filesystem corruption only in case the power fails suddently. Also cases like kernel crashes are usually solved by t= he journal quite fine. But in situations like flaky power supply where mem= ory can provide wrong data to disk or disk writes only some data because of weak voltage, journaling does not help at all. Generally, only good bac= kups are a solution to bugs in HW... Honza > 2010/3/17 Jan Kara : > > =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 rese= ts. > >> > >> I started to change the BIOS configuration and one of this changes= leaved > >> the screen black. Unfortunately, I pressed the reset button thinki= ng that > >> didn't boot but the next time (after leave the BIOS configuration = like > >> before) the system didn't boot. > > =A0I'd check your HW - memory, power supply, ... Obviously somethin= g got > > wrong. > > > >> It showed me this message: "EXT3-fs: fragsize 1024 !=3D blocksize = 4096 > >> (unsupported)" (you can see two pictures booting with this error a= t > >> http://forums.fedoraforum.org/attachment.php?attachmentid=3D19240&= d=3D1268739264 > >> and http://forums.fedoraforum.org/attachment.php?attachmentid=3D19= 239&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=A0 data. If the= ext3 > >> has journal, is this a bug in the ext3 journal filesystem? > > =A0I'd say it is a faulty HW, not a software bug. > > > >> My question is how can repair this lvm/ext3 volume without loose d= ata? > > =A0I would first try to identify faulty HW (run memtest from a resc= ue CD > > for example). When HW gets fixed, I'd copy the filesystem with 'dd'= to a > > different disk as a backup. Then run e2fsck to fix /dev/hda2. > > > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Honza > > -- > > Jan Kara > > SUSE Labs, CR > > --=20 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