public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans-Peter Jansen <hpj@urpla.net>
To: Jan Beulich <JBeulich@suse.com>
Cc: Eric Sandeen <sandeen@sandeen.net>, linux-xfs@vger.kernel.org
Subject: Re: permanent XFS volume corruption
Date: Fri, 12 May 2017 18:23:48 +0200	[thread overview]
Message-ID: <1734059.x4Ie82qtds@xrated> (raw)
In-Reply-To: <5915EEA7020000780015958E@prv-mh.provo.novell.com>

On Freitag, 12. Mai 2017 09:19:35 Jan Beulich wrote:
> >>> On 12.05.17 at 17:04, <sandeen@sandeen.net> wrote:
> > However:
> > 
> > With further testing I see that xfs_repair v3.1.8 /does not/
> > entirely fix the fs; if I run 3.1.8 and then run upstream repair, it
> > finds and fixes more bad flags on inode 764 (lib/xenstored/tdb) that 3.1.8
> > didn't touch.  The verifiers in an upstream kernel may keep tripping
> > over that until newer repair fixes it...
> 
> Well, I can see if I can build those newer tools for myself (would
> largely depend on how easy/difficult they are to configure/make,
> and whether there's a testsuite that I can run them over before
> allowing them to touch live data); I don't expect newer tools to
> be available for the distro I'm running.

Pretty sure, you're running some SuSE derivative. Building the xfstools 
usually is pretty simple with OBS, I do that all the time for unsupported 
distros:

	https://build.opensuse.org/project/show/home:frispete:tools

If BS wouldn't be down at the moment, I could look, if xfstests run as well, 
but since you have a backup of course, the risk of damaging your system with  
newer xfstools is pretty low. It saved my ass a couple of times...

Good luck,
Pete

who notoriously runs outphased SuSE versions (e.g. 9.3 on my PBX)


      reply	other threads:[~2017-05-12 16:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-11 14:39 permanent XFS volume corruption Jan Beulich
2017-05-11 14:58 ` Eric Sandeen
2017-05-11 15:12   ` Jan Beulich
2017-05-11 15:16     ` Eric Sandeen
2017-05-11 15:40       ` Jan Beulich
2017-05-11 16:39 ` Eric Sandeen
2017-05-12  6:26   ` Jan Beulich
2017-05-12 13:56     ` Eric Sandeen
2017-05-12 14:09       ` Jan Beulich
2017-05-12 15:04         ` Eric Sandeen
2017-05-12 15:11           ` Eric Sandeen
2017-05-15  9:22             ` Jan Beulich
2017-05-15 16:52               ` Eric Sandeen
2017-05-16 10:06                 ` Jan Beulich
2017-05-16 17:38                   ` Eric Sandeen
2017-05-17  5:27                     ` Jan Beulich
2017-05-12 15:19           ` Jan Beulich
2017-05-12 16:23             ` Hans-Peter Jansen [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=1734059.x4Ie82qtds@xrated \
    --to=hpj@urpla.net \
    --cc=JBeulich@suse.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@sandeen.net \
    /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