From: "Toralf Förster" <toralf.foerster@gmx.de>
To: linux-ext4@vger.kernel.org
Subject: still got few EXT4-fs errors
Date: Tue, 06 Nov 2012 22:13:49 +0100 [thread overview]
Message-ID: <50997D8D.40509@gmx.de> (raw)
With kernel 3.6.6-rc1 I got :
n22 ~ # zgrep -e 'EXT4-fs error' -e JBD2 /var/log/messages
2012-11-05T13:40:44.460+01:00 n22 kernel: EXT4-fs error (device sdb3) in ext4_new_inode:933: IO failure
2012-11-05T13:41:25.982+01:00 n22 kernel: EXT4-fs error (device sdb3) in ext4_new_inode:933: IO failure
2012-11-05T13:41:26.543+01:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 771, 31096 clusters in bitmap, 31095 in gd
2012-11-05T13:41:26.543+01:00 n22 kernel: JBD2: Spotted dirty metadata buffer (dev = sdb3, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
2012-11-05T13:45:02.077+01:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 1123, 31721 clusters in bitmap, 31720 in gd
2012-11-05T13:45:02.077+01:00 n22 kernel: JBD2: Spotted dirty metadata buffer (dev = sdb3, blocknr = 0). There's a risk of filesystem corruption in case of system crash.
2012-11-05T13:54:41.729+01:00 n22 kernel: EXT4-fs error (device sdb3): mb_free_blocks:1300: group 1123, block 36808224:freeing already freed block (bit 9760)
2012-11-05T13:54:41.729+01:00 n22 kernel: EXT4-fs error (device sdb3): mb_free_blocks:1300: group 771, block 25264846:freeing already freed block (bit 718)
It is an almost stable Gentoo Linux 32 bit, booted from an external USB disk.
What I did at that time was to compile the 3.6.6 final stable kernel.
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
reply other threads:[~2012-11-06 21:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50997D8D.40509@gmx.de \
--to=toralf.foerster@gmx.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 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.