From: Dave Chinner <david@fromorbit.com>
To: Pavol Gono <Pavol.Gono@siemens.com>
Cc: xfs@oss.sgi.com
Subject: Re: "Invalid block length" warning with small blocksize
Date: Sat, 2 Apr 2011 09:19:21 +1100 [thread overview]
Message-ID: <20110401221921.GF6957@dastard> (raw)
In-Reply-To: <4D95A563.3050804@siemens.com>
On Fri, Apr 01, 2011 at 12:13:55PM +0200, Pavol Gono wrote:
> Hi
>
> I am getting this warning in kernel log:
> XFS: Invalid block length (0x2000) given for buffer
> during mount, and I don't know if this can be safely ignored or not.
Yes, it can be ignored - it's just a warning that the code fell back
to using a smaller-than-optimal block size for reading the log
during recovery. I see it quite often when running xfstests on 512
byte block sіze filesystems.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-04-01 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 10:13 "Invalid block length" warning with small blocksize Pavol Gono
2011-04-01 22:19 ` Dave Chinner [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=20110401221921.GF6957@dastard \
--to=david@fromorbit.com \
--cc=Pavol.Gono@siemens.com \
--cc=xfs@oss.sgi.com \
/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