All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Libor Klepáč" <libor.klepac@bcom.cz>
Cc: Brian Foster <bfoster@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: BUG: Metadata corruption detected at xfs_attr3_leaf_read_verify
Date: Mon, 31 Oct 2016 23:02:26 +1100	[thread overview]
Message-ID: <20161031120226.GT14023@dastard> (raw)
In-Reply-To: <3301912.kAxTXXYXM8@libor-nb>

On Mon, Oct 31, 2016 at 09:54:00AM +0100, Libor Klepáč wrote:
> Hello,
> i have upgrade VM called vps1 in original email (the one on bottom of email)
> to debian kernel 4.7.8-1~bpo8+1 and compiled xfsprogs 4.8.0.
> 
> Here is output of xfs_repair -n and xfs_repair. Is it supposed to write if/
> what is being repaired, when i forgot -v option?

repair will always tell you if there are errors. The logs you have
posted indicate a clean filesystem with no errors.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  parent reply	other threads:[~2016-10-31 12:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21 17:09 BUG: Metadata corruption detected at xfs_attr3_leaf_read_verify Libor Klepáč
2016-10-21 17:59 ` Brian Foster
2016-10-21 22:20   ` Dave Chinner
2016-10-23  6:48   ` Libor Klepáč
2016-10-24  2:40     ` Dave Chinner
2016-10-25  6:52       ` Libor Klepáč
2016-10-31  8:54       ` Libor Klepáč
2016-10-31 11:57         ` Brian Foster
2016-10-31 12:02         ` Dave Chinner [this message]
2016-10-31 15:36           ` Libor Klepáč
2016-11-08 11:09           ` Libor Klepáč
2016-11-08 11:28             ` Libor Klepáč
2016-11-10  5:29               ` Dave Chinner
     [not found]                 ` <2152865.L3K5Xz7SXO@libor-nb>
2016-11-10 21:30                   ` Dave Chinner
2016-11-23 11:40                     ` Libor Klepáč
2016-11-26  6:05                       ` Eric Sandeen
2016-12-06  9:08                     ` Libor Klepáč
  -- strict thread matches above, loose matches on Subject: below --
2016-10-21 12:46 Libor Klepáč

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=20161031120226.GT14023@dastard \
    --to=david@fromorbit.com \
    --cc=bfoster@redhat.com \
    --cc=libor.klepac@bcom.cz \
    --cc=linux-xfs@vger.kernel.org \
    /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.