From: Jan Kara <jack@suse.cz>
To: Oscar Megia <megia.oscar@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: BUG EXT3-fs: fragsize 1024 != blocksize 4096 (unsupported)
Date: Wed, 17 Mar 2010 17:24:40 +0100 [thread overview]
Message-ID: <20100317162439.GC5799@quack.suse.cz> (raw)
In-Reply-To: <d2be449a1003160605p7d8d9f5cof0e6f32cfa0c5dfb@mail.gmail.com>
Hi,
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.
>
> I started to change the BIOS configuration and one of this changes leaved
> the screen black. Unfortunately, I pressed the reset button thinking that
> didn't boot but the next time (after leave the BIOS configuration like
> before) the system didn't boot.
I'd check your HW - memory, power supply, ... Obviously something got
wrong.
> It showed me this message: "EXT3-fs: fragsize 1024 != blocksize 4096
> (unsupported)" (you can see two pictures booting with this error at
> http://forums.fedoraforum.org/attachment.php?attachmentid=19240&d=1268739264
> and http://forums.fedoraforum.org/attachment.php?attachmentid=19239&d=1268739254).
>
> Researching I could get info from the root fs with dumpe2fs:
...
>
> hda1 is for boot and hda2/lvm/ext3 with the OS and data. If the ext3
> has journal, is this a bug in the ext3 journal filesystem?
I'd say it is a faulty HW, not a software bug.
> My question is how can repair this lvm/ext3 volume without loose data?
I would first try to identify faulty HW (run memtest from a rescue 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.
Honza
--
Jan Kara <jack@suse.cz>
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
next prev parent reply other threads:[~2010-03-17 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d2be449a1003160554w2309064dj5c9e5dd5994ce23d@mail.gmail.com>
2010-03-16 13:05 ` BUG EXT3-fs: fragsize 1024 != blocksize 4096 (unsupported) Oscar Megia
2010-03-17 16:24 ` Jan Kara [this message]
2010-04-06 19:35 ` Oscar Megia
2010-04-06 20:05 ` Jan Kara
2010-04-06 20:16 ` Oscar Megia
2010-04-06 21:07 ` tytso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100317162439.GC5799@quack.suse.cz \
--to=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=megia.oscar@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).