LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Projects > LinuxQuestions.org > Bug
User Name
Password

Notices


BUG in EXT3-fs: fragsize 1024 != blocksize 4096 (unsupported) Issue Tools
issueid=81 03-16-2010 12:08 PM
LQ Newbie
BUG in EXT3-fs: fragsize 1024 != blocksize 4096 (unsupported)
Accidentaly I press the reset button during booting and the ext3 fs broken!!

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 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)". http://forums.fedoraforum.org/attach...0&d=1268739264

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. ext3 is a ournal filesystem, so i think this is a BUG.

My BIG question is how can I repair this lvm/ext3 volume without loose data?

Regards
Oscar
Issue Details
Project LinuxQuestions.org
Category Other
Status Not a Bug
Priority 2
Affected Version Unknown
Fixed Version (none)
Users able to reproduce bug 0
Users unable to reproduce bug 0
Assigned Users (none)
Tags (none)

03-16-2010 12:51 PM
root
 
This issue tracker is only for items pertaining to LinuxQuestions.org. Please post in the forums, or alternatively post a bug to the EXT3 folks.

--jeremy
Reply
03-17-2010 12:36 AM
LQ Newbie
 
Ok
Reply
Reply

  



All times are GMT -5. The time now is 04:04 AM.

Main Menu
Advertisement
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration