All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Timofey Titovets <nefelim4ag@gmail.com>, xfs@oss.sgi.com
Subject: Re: Q: xfs_db: invalid numrecs (*) in bmapbtd block
Date: Sun, 28 Jun 2015 17:12:24 -0500	[thread overview]
Message-ID: <55907148.1050509@sandeen.net> (raw)
In-Reply-To: <CAGqmi75jFGjWvFFT5HTwyO1tv4-d4J=aVJ83L2zqNyWMDOz1RQ@mail.gmail.com>

On 6/28/15 1:44 PM, Timofey Titovets wrote:
> Good time of day list,
> i do regular check fragmentation on my servers and xfs_db show strange erros:

No need, really.

http://xfs.org/index.php/XFS_FAQ#Q:_The_xfs_db_.22frag.22_command_says_I.27m_over_50.25._Is_that_bad.3F

> # xfs_db -c frag -r /dev/sdc1
> invalid numrecs (51914) in bmapbtd block
> invalid numrecs (2827) in bmapbtd block

...

> actual 504454, ideal 126776, fragmentation factor 74.87%


 
> I already google error, and can't find any answer or explanation what
> is it, how danger it or something like.
> It's a production servers with several TB of data and this output make
> me unhappy. =.=

does xfs_repair find any errors?

> And i can't do fast stop it, unmount and check file system.
> (this is nfs server for virtual machines images)

Oh.  So you're doing it with an online/mounted filesystem?

The on-disk filesystem isn't necessarily consistent when mounted,
some of that consistency lives in the log.

You're likely just seeing that inconsitency because you're reading
it while it's mounted; possibly even while it's being modified.

-Eric

> Thanks for any help, anyway.
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-06-28 22:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-28 18:44 Q: xfs_db: invalid numrecs (*) in bmapbtd block Timofey Titovets
2015-06-28 22:12 ` Eric Sandeen [this message]
2015-06-28 22:29   ` Timofey Titovets
2015-06-29  1:17     ` Eric Sandeen
2015-06-29  0:24 ` Dave Chinner
2015-06-29  0:48   ` Timofey Titovets

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=55907148.1050509@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=nefelim4ag@gmail.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 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.