From: Christian Kujau <lists@nerdbynature.de>
To: linux-ext4@vger.kernel.org
Subject: Group descriptor 0 checksum is invalid
Date: Sat, 14 Nov 2009 14:00:15 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.01.0911141349050.27639@bogon.housecafe.de> (raw)
Hi,
when trying to convert an ext3 filesystem to ext4, I'm getting these
"Group descriptor 0 checksum is invalid" messages. I've seen them before
and the net is full of them, but I still wonder if they're expected to
show up at all during the filesystem's first fsck. See below for the
script log.
Thanks,
Christian.
sid:~# cat /proc/version
Linux version 2.6.32-rc7 (dummy@sid) (gcc version 4.4.2 (Debian 4.4.2-2) ) #1 SMP Sat Nov 14 22:00:51 CET 2009
sid:~# mkfs.ext3 -q /dev/xvdc
sid:~# mount -t ext3 /dev/xvdc /mnt/d2
sid:~# grep /dev/xvdc /proc/mounts
/dev/xvdc /mnt/d2 ext3 rw,relatime,errors=continue,data=writeback 0 0
sid:~# df -h /dev/xvdc
Filesystem Size Used Avail Use% Mounted on
/dev/xvdc 16G 173M 15G 2% /mnt/d2
sid:~# umount /dev/xvdc
sid:~# tune2fs -O extents,uninit_bg /dev/xvdc
tune2fs 1.41.9 (22-Aug-2009)
Please run e2fsck on the filesystem.
sid:~# tune2fs -l /dev/xvdc | grep -i feat
Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent sparse_super large_file uninit_bg
sid:~# e2fsck -fpDC0 /dev/xvdc
/dev/xvdc: One or more block group descriptor checksums are invalid. FIXED.
/dev/xvdc: Group descriptor 0 checksum is invalid.
/dev/xvdc: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
sid:~# e2fsck -fDC0 /dev/xvdc
e2fsck 1.41.9 (22-Aug-2009)
One or more block group descriptor checksums are invalid. Fix<y>? yes
Group descriptor 0 checksum is invalid. FIXED.
Group descriptor 1 checksum is invalid. FIXED.
[...]
Group descriptor 126 checksum is invalid. FIXED.
Group descriptor 127 checksum is invalid. FIXED.
Pass 1: Checking inodes, blocks, and sizes
/dev/xvdc: | [...]
Pass 3: Checking directory connectivity
Pass 3A: Optimizing directories
Rebuilding directory: |================ / 50.0% [...]
Pass 5: Checking group summary information
/dev/xvdc: |========================================================| 100.0%
/dev/xvdc: ***** FILE SYSTEM WAS MODIFIED *****
/dev/xvdc: 11/1048576 files (0.0% non-contiguous), 109874/4194304 blocks
sid:~#
sid:~# e2fsck -fC0 /dev/xvdc
/dev/xvdc: | [...]
/dev/xvdc: 11/1048576 files (0.0% non-contiguous), 109874/4194304 blocks
--
BOFH excuse #389:
/dev/clue was linked to /dev/null
next reply other threads:[~2009-11-14 22:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 22:00 Christian Kujau [this message]
2009-11-16 3:11 ` Group descriptor 0 checksum is invalid Theodore Tso
2009-11-16 7:27 ` Christian Kujau
2009-11-16 16:36 ` Andreas Dilger
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=alpine.DEB.2.01.0911141349050.27639@bogon.housecafe.de \
--to=lists@nerdbynature.de \
--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