From: Tomasz Chmielewski <mangoo@wpkg.org>
To: linux-ext4@vger.kernel.org
Subject: ext4 errors not going away after fsck
Date: Thu, 25 Nov 2010 15:57:57 +0100 [thread overview]
Message-ID: <4CEE7975.10809@wpkg.org> (raw)
I have a system which had bad memory.
Bad memory was replaced, but filesystem corruption caused by it (and related crashes) is still there:
[104472.909769] EXT4-fs (vdb1): mounted filesystem with ordered data mode. Opts: errors=remount-ro
[104773.600088] EXT4-fs (vdb1): error count: 2
[104773.600093] EXT4-fs (vdb1): initial error at 1290468286: htree_dirblock_to_tree:586: inode 30204507: block 120625971
[104773.600097] EXT4-fs (vdb1): last error at 1290468334: ext4_put_super:726: inode 30204507: block 120625971
Unfortunately, repeated fsck checks do not make the error go away (using 2.6.37-rc3 and e2fsprogs 1.41.12):
# e2fsck -f -v -y /dev/vdb1
e2fsck 1.41.12 (17-May-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
16281559 inodes used (35.49%)
4484 non-contiguous files (0.0%)
29082 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 16273127/8421
152806601 blocks used (83.27%)
0 bad blocks
27 large files
7931312 regular files
8350237 directories
0 character device files
0 block device files
0 fifos
95162835 links
0 symbolic links (0 fast symbolic links)
1 socket
--------
111444385 files
# mount -a
# dmesg -c
[108692.626550] EXT4-fs (vdb1): mounted filesystem with ordered data mode. Opts: errors=remount-ro
# ls -lR /mount/point
(...)
# dmesg -c
[108993.760041] EXT4-fs (vdb1): error count: 2
[108993.760051] EXT4-fs (vdb1): initial error at 1290468286: htree_dirblock_to_tree:586: inode 30204507: block 120625971
[108993.760058] EXT4-fs (vdb1): last error at 1290468334: ext4_put_super:726: inode 30204507: block 120625971
The error is exactly the same as the first one I pasted (multiple umount, fsck, mount runs without reboot).
Is this all something to be worry about?
--
Tomasz Chmielewski
http://wpkg.org
next reply other threads:[~2010-11-25 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 14:57 Tomasz Chmielewski [this message]
2010-11-25 19:09 ` ext4 errors not going away after fsck 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=4CEE7975.10809@wpkg.org \
--to=mangoo@wpkg.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.