From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Ted Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: errors in ext4_mb_generate_buddy and ext4_remount
Date: Wed, 01 Jun 2011 12:44:13 +0200 [thread overview]
Message-ID: <1306925053.3304.6.camel@fermat.scientia.net> (raw)
In-Reply-To: <20110601041502.GB4172@thunk.org>
[-- Attachment #1: Type: text/plain, Size: 301 bytes --]
On Wed, 2011-06-01 at 00:15 -0400, Ted Ts'o wrote:
> Um, are you sure? Try forcing an fsck run on the file systems in question.
Of course I did ;-) (fsck.ext4 -f -D /dev/bla)...
And as I had some other fs troubles with that ext4 yesterday, I ran it
also several times ;)
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5677 bytes --]
prev parent reply other threads:[~2011-06-01 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 0:56 errors in ext4_mb_generate_buddy and ext4_remount Christoph Anton Mitterer
2011-05-09 1:01 ` Ted Ts'o
2011-05-09 12:55 ` Christoph Anton Mitterer
2011-05-31 22:38 ` Christoph Anton Mitterer
2011-06-01 4:15 ` Ted Ts'o
2011-06-01 10:44 ` Christoph Anton Mitterer [this message]
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=1306925053.3304.6.camel@fermat.scientia.net \
--to=calestyo@scientia.net \
--cc=linux-ext4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).