From: Ron Johnson <ron.l.johnson@cox.net>
To: Linux-Ext4 <linux-ext4@vger.kernel.org>
Subject: EXT4-fs: group descriptors corrupted!
Date: Wed, 25 Feb 2009 14:39:31 -0600 [thread overview]
Message-ID: <49A5AC83.1020009@cox.net> (raw)
Hi,
I get an error that seems to be the same as in this thread:
http://kerneltrap.org/mailarchive/linux-ext4/2009/1/5/4598534
Below is the link to a dumpe2fs.
$ dmesg | grep EXT4
[ 45.995261] EXT4-fs: barriers enabled
[ 46.014833] EXT4 FS on hda1, internal journal on hda1:8
[ 46.014873] EXT4-fs: delayed allocation enabled
[ 46.014912] EXT4-fs: file extents enabled
[ 46.015883] EXT4-fs: mballoc enabled
[ 46.015926] EXT4-fs: mounted filesystem with ordered data mode.
[ 1392.640482] EXT4-fs: ext4_check_descriptors: Block bitmap for
group 0 not in group (block 3120627712)!
[ 1392.640490] EXT4-fs: group descriptors corrupted!
These are the relevant Debian Sid package versions:
e2fsprogs 1.41.3-1
linux-source-2.6.28 2.6.28-2~snapshot.12850
Since I built the fs with extents enabled, I am hesitant to run fsck
on it because I've read that it doesn't yet support extents.
As you can see from the dmesg snippets, one of my ext4 file systems
mounted perfectly. The one that didn't is an lvm2 "array", which
seems to be consistent.
# lvdisplay
Logging initialised at Wed Feb 25 14:31:23 2009
Set umask to 0077
lvdisplay Finding all logical volumes
lvdisplay --- Logical volume ---
lvdisplay LV Name /dev/main_huge_vg/main_huge_lv
lvdisplay VG Name main_huge_vg
lvdisplay LV UUID Pgrlks-mtmc-GuYh-kvPU-Mr78-w9b6-uykW8A
lvdisplay LV Write Access read/write
lvdisplay LV Status available
lvdisplay # open 0
lvdisplay LV Size 2.69 TB
lvdisplay Current LE 22023
lvdisplay Segments 9
lvdisplay Allocation inherit
lvdisplay Read ahead sectors auto
lvdisplay - currently set to 256
lvdisplay Block device 254:0
lvdisplay
lvdisplay Wiping internal VG cache
# dumpe2fs -f/dev/main_huge_vg/main_huge_lv | head -n800 >
main_huge_lv.dump.txt
dumpe2fs 1.41.3 (12-Oct-2008)
ext2fs_read_bb_inode: Invalid argument
http://members.cox.net/ron.l.johnson/main_huge_lv.dump.txt
TIA
--
Ron Johnson, Jr.
Jefferson LA USA
next reply other threads:[~2009-02-25 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 20:39 Ron Johnson [this message]
2009-02-25 21:30 ` EXT4-fs: group descriptors corrupted! Theodore Tso
2009-02-25 21:47 ` Ron Johnson
2009-02-25 23:18 ` Theodore Tso
2009-02-25 23:41 ` Greg Freemyer
2009-02-25 23:42 ` Ron Johnson
2009-02-26 0:05 ` Andreas Dilger
2009-02-26 0:23 ` Ron Johnson
-- strict thread matches above, loose matches on Subject: below --
2009-03-07 6:55 Christian
2009-03-09 16:13 ` Christian
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=49A5AC83.1020009@cox.net \
--to=ron.l.johnson@cox.net \
--cc=linux-ext4@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).