From: Eric Sandeen <sandeen@sandeen.net>
To: Timofey Titovets <nefelim4ag@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Q: xfs_db: invalid numrecs (*) in bmapbtd block
Date: Sun, 28 Jun 2015 20:17:53 -0500 [thread overview]
Message-ID: <55909CC1.2020301@sandeen.net> (raw)
In-Reply-To: <CAGqmi75V-DWbJR0LPOqwhg3s501G_kSDpcPjbPi6nuGWOJNrKA@mail.gmail.com>
On 6/28/15 5:29 PM, Timofey Titovets wrote:
> 2015-06-29 1:12 GMT+03:00 Eric Sandeen <sandeen@sandeen.net>:
...
>> You're likely just seeing that inconsitency because you're reading
>> it while it's mounted; possibly even while it's being modified.
>>
>> -Eric
>
> I already thinked about this case, and it seems incredible.
> 1. i can get consistent or very close to consistent fs, by run 'sync'
> 2. Okay, supposing you are right,
> then i must get different errors over time, because fs will change own
> state over time (also after every sync call).
> But its don't happen, i get same errors over long period of time (1
> day+, i think on busy FS server, its enoug to think what data on disk
> has changed)
> Also, i have several others server, and on it i didn't see this
> problem (over 2-3 month).
>
>
> Then I can conclude this is errors in FS, only what matter to me now,
> this type of errors can damage my data and i must move virtual
> machines from it ASAP, or i can continue working and this is just
> "artefact".
>
> Fix me if i'm wrong.
Your other option is to unmount and run xfs_repair, and find out if
you actually have on-disk corruption. It's the only way to know
for sure (or: freeze the fs, snapshot the device, and run repair on that)
-Eric
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-06-29 1:18 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
2015-06-28 22:29 ` Timofey Titovets
2015-06-29 1:17 ` Eric Sandeen [this message]
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=55909CC1.2020301@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.