From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Theodore Ts'o <tytso@mit.edu>,
linux-ext4@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: EXT4-fs error w/ external USB drive
Date: Mon, 22 Oct 2012 20:36:47 +0200 [thread overview]
Message-ID: <5085923F.9050801@gmx.de> (raw)
In-Reply-To: <20121019210723.GA4721@thunk.org>
On 10/19/2012 11:07 PM, Theodore Ts'o wrote:
> On Mon, Oct 15, 2012 at 07:46:02PM +0200, Toralf Förster wrote:
>> Even with current stable kernel 3.6.2 I sometimes get those syslog messages :
>>
>>
>> 2012-10-15T19:37:58.401+02:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 436, 22902 clusters in bitmap, 22901 in gd
>
> Have you run e2fsck to clean up the file system corruption? If you
> have, do you continually get these errors afterwards?
Well, I got it yesterday too :
n22 ~ # zgrep ext4_mb_generate_buddy /var/log/messages-201210*
/var/log/messages-20121021.gz:2012-10-15T19:05:39.189+02:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 774, 27157 clusters in bitmap, 27052 in gd
/var/log/messages-20121021.gz:2012-10-15T19:37:58.401+02:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 436, 22902 clusters in bitmap, 22901 in gd
/var/log/messages-20121021.gz:2012-10-15T19:56:05.301+02:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 1233, 11981 clusters in bitmap, 11974 in gd
/var/log/messages-20121021.gz:2012-10-15T19:56:18.601+02:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 484, 28817 clusters in bitmap, 28101 in gd
I rebooted the system and forced a run of fsck after these lines too.
I'll check periodically whether it happens again.
> You say this is an external USB disk; is there any possibility of the
> disk getting unmounted uncleanly due to the cable getting pulled out
> while the disk is still mounted, and then the disk getting remounted
> w/o having e2fsck run on the disk?
For the first occurrence probably yes (better : I dunno), but yesterday definitely not.
--
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
WARNING: multiple messages have this Message-ID (diff)
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: "Theodore Ts'o" <tytso@mit.edu>,
linux-ext4@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: EXT4-fs error w/ external USB drive
Date: Mon, 22 Oct 2012 20:36:47 +0200 [thread overview]
Message-ID: <5085923F.9050801@gmx.de> (raw)
In-Reply-To: <20121019210723.GA4721@thunk.org>
On 10/19/2012 11:07 PM, Theodore Ts'o wrote:
> On Mon, Oct 15, 2012 at 07:46:02PM +0200, Toralf Förster wrote:
>> Even with current stable kernel 3.6.2 I sometimes get those syslog messages :
>>
>>
>> 2012-10-15T19:37:58.401+02:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 436, 22902 clusters in bitmap, 22901 in gd
>
> Have you run e2fsck to clean up the file system corruption? If you
> have, do you continually get these errors afterwards?
Well, I got it yesterday too :
n22 ~ # zgrep ext4_mb_generate_buddy /var/log/messages-201210*
/var/log/messages-20121021.gz:2012-10-15T19:05:39.189+02:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 774, 27157 clusters in bitmap, 27052 in gd
/var/log/messages-20121021.gz:2012-10-15T19:37:58.401+02:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 436, 22902 clusters in bitmap, 22901 in gd
/var/log/messages-20121021.gz:2012-10-15T19:56:05.301+02:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 1233, 11981 clusters in bitmap, 11974 in gd
/var/log/messages-20121021.gz:2012-10-15T19:56:18.601+02:00 n22 kernel: EXT4-fs error (device sdb3): ext4_mb_generate_buddy:741: group 484, 28817 clusters in bitmap, 28101 in gd
I rebooted the system and forced a run of fsck after these lines too.
I'll check periodically whether it happens again.
> You say this is an external USB disk; is there any possibility of the
> disk getting unmounted uncleanly due to the cable getting pulled out
> while the disk is still mounted, and then the disk getting remounted
> w/o having e2fsck run on the disk?
For the first occurrence probably yes (better : I dunno), but yesterday definitely not.
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
next prev parent reply other threads:[~2012-10-22 18:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 17:46 EXT4-fs error w/ external USB drive Toralf Förster
2012-10-19 21:07 ` Theodore Ts'o
2012-10-22 18:36 ` Toralf Förster [this message]
2012-10-22 18:36 ` Toralf Förster
2012-10-24 1:11 ` Theodore Ts'o
2012-10-24 17:31 ` Toralf Förster
2012-10-24 17:31 ` Toralf Förster
2012-10-24 18:35 ` Theodore Ts'o
2012-10-25 16:39 ` Toralf Förster
2012-10-25 18:20 ` Theodore Ts'o
2012-10-25 18:20 ` Theodore Ts'o
2012-10-25 18:27 ` Eric Sandeen
2012-10-25 18:27 ` Eric Sandeen
2012-10-26 14:30 ` Toralf Förster
2012-10-26 14:30 ` Toralf Förster
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=5085923F.9050801@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.