From: Oscar Megia <megia.oscar@gmail.com>
To: linux-fsdevel@vger.kernel.org
Subject: BUG EXT3-fs: fragsize 1024 != blocksize 4096 (unsupported)
Date: Tue, 16 Mar 2010 13:05:09 +0000 [thread overview]
Message-ID: <d2be449a1003160605p7d8d9f5cof0e6f32cfa0c5dfb@mail.gmail.com> (raw)
In-Reply-To: <d2be449a1003160554w2309064dj5c9e5dd5994ce23d@mail.gmail.com>
Hi everyone!
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.
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:
# losetup -r -o 196608 /dev/loop0 /dev/hda2
# dumpe2fs /dev/loop0
Filesystem volume name: Fedoraiv-Live-i6
Last mounted on: <not available>
Filesystem UUID: 15035e8e-1503-7c55-ba46-bfdd46659fa5
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: imagic_inodes filetype sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 4808704
Block count: 19210240
Reserved block count: 1507328
Free blocks: 1539180
Free inodes: 4390912
First block: 0
Block size: 4096
Fragment size: 1024
Reserved GDT blocks: 251
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 56884
Inode blocks per group: 3556
Filesystem created: Thu Jan 1 06:23:12 1970
Last mount time: Sat Mar 13 18:49:24 2010
Last write time: Sat Mar 13 19:55:08 2010
Mount count: 59152
Maximum mount count: -1
Last checked: Thu May 8 01:48:09 2008
Check interval: 0 (<none>)
Reserved blocks uid: 11 (user unknown)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 1
Journal UUID: 00000000-0000-0000-0000-000008000000
Journal inode: 8
First orphan inode: 52113
Default directory hash: tea
Directory Hash Seed: 91cb4d10-e684-4c10-5e73-e3e95e737bdc
Journal backup: inode blocks
...
The disk has two partitions:
kdemar@kademar:~$ fdisk -l
Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb838b838
Device Boot Start End Blocks Id System
/dev/hda1 * 1 25 200781 83 Linux
/dev/hda2 26 9729 77947380 8e Linux LVM
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?
My question is how can repair this lvm/ext3 volume without loose data?
Regards
Oscar
next parent reply other threads:[~2010-03-16 13:05 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 ` Oscar Megia [this message]
2010-03-17 16:24 ` BUG EXT3-fs: fragsize 1024 != blocksize 4096 (unsupported) Jan Kara
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=d2be449a1003160605p7d8d9f5cof0e6f32cfa0c5dfb@mail.gmail.com \
--to=megia.oscar@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
/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).