From: "Toralf Förster" <toralf.foerster@gmx.de>
To: linux-ext4@vger.kernel.org
Subject: ext4 fs errors - immediately reboot needed ?
Date: Mon, 19 Nov 2012 19:45:41 +0100 [thread overview]
Message-ID: <50AA7E55.2090707@gmx.de> (raw)
/me wonders, whether the following messages should force me to *immediately*
reboot the system of whether I should schedule a reboot in the near future :
2012-11-19T19:23:53.099+01:00 n22 kernel: EXT4-fs error (device sdb3) in ext4_new_inode:933: IO failure
2012-11-19T19:24:04.971+01:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 409, 11806 clusters in bitmap, 11805 in gd
2012-11-19T19:24:04.971+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-19T19:37:20.188+01:00 n22 kernel: EXT4-fs error (device sdb3) in ext4_new_inode:933: IO failure
2012-11-19T19:44:28.552+01:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 424, 27235 clusters in bitmap, 27234 in gd
2012-11-19T19:44:28.552+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-19T19:44:33.734+01:00 n22 kernel: EXT4-fs error (device sdb3): mb_free_blocks:1300: group 424, block 13916749:freeing already freed block (bit 23117)
2012-11-19T19:44:33.734+01:00 n22 kernel: EXT4-fs error (device sdb3): mb_free_blocks:1300: group 409, block 13431904:freeing already freed block (bit 29792)
--
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
next reply other threads:[~2012-11-19 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 18:45 Toralf Förster [this message]
2012-11-19 19:31 ` ext4 fs errors - immediately reboot needed ? Theodore Ts'o
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=50AA7E55.2090707@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.