From: Thorsten Hufnagel <Mondsuechtig@quantentunnel.de>
To: linux-xfs@vger.kernel.org
Subject: Re: Strange XFS problem
Date: Sun, 03 Jun 2018 04:32:24 +0200 [thread overview]
Message-ID: <0ae6d0d5984dcd9c703720bdf41b6da1333267b0.camel@quantentunnel.de> (raw)
In-Reply-To: <e462d333d2089a7c3c59e7584fa83f720365fa46.camel@quantentunnel.de>
I just Got it.
The issue seemed to got fixed with 4.16.0-rc1.
Downloading / compiling / using the 4.16.1 version solved my issue.
Sorry for bothering,
Thorsten
Am Sonntag, den 03.06.2018, 03:51 +0200 schrieb Thorsten Hufnagel:
> Hi there,
>
> I've just a big problem with my XFS file system used on a mdraid raid
> 5
> array.
>
> It started with the situation that the mount of my device was not
> possible any more (don't know why, hdd's are OK).
>
> "xfs_repair" results in
>
> "
> ERROR: The log head and/or tail cannot be discovered. Attempt to
> mount
> the
> filesystem to replay the log or use the -L option to destroy the log
> and
> attempt a repair.
> "
>
> "xfs_repair -L " ran, but unfortunately it was interrupted by an
> automatic server shutdown after it stuck after stage 7.
>
> Now, "xfs_repair" results in
>
> "
> Phase 1 - Superblock finden und überprüfen...
> - Berichts-Prozess in Abständen von 15 Minutes
> Phase 2 - ein internes Protokoll benutzen
> - Null-Protokoll...
> Log inconsistent or not a log (last==0, first!=1)
> empty log check failed
> zero_log: cannot find log head/tail (xlog_find_tail=22)
> ERROR: The log head and/or tail cannot be discovered. Attempt to
> mount
> the
> filesystem to replay the log or use the -L option to destroy the log
> and
> attempt a repair.
> "
>
> A mount attemp results in
>
> "
> mount: /mnt/test: Falscher Dateisystemtyp, ungültige Optionen, der
> Superblock von /dev/md2 ist beschädigt, fehlende Kodierungsseite oder
> ein anderer Fehler.
> "
>
> And "xfs_repair -L" results in
>
> "
> Phase 1 - Superblock finden und überprüfen...
> - Berichts-Prozess in Abständen von 15 Minutes
> Phase 2 - ein internes Protokoll benutzen
> - Null-Protokoll...
> Log inconsistent or not a log (last==0, first!=1)
> empty log check failed
> zero_log: cannot find log head/tail (xlog_find_tail=22)
> "
>
> Sounds linke some kind of "Hen-egg" problem.
>
> Is there any change to get the XFS file sytem back running without
> recreating the filesystem?
>
> Kernel:
>
> "
> uname -r
> 4.16.12-1-default
> "
>
> Distribution: "Opensuse - Tumbleween"
>
> XFS tools: "xfs_repair Version 4.15.1"
>
> Thank you in advance,
> Kind regards,
>
> Thorsten Hufnagel
>
next prev parent reply other threads:[~2018-06-03 2:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 1:51 Strange XFS problem Thorsten Hufnagel
2018-06-03 2:32 ` Thorsten Hufnagel [this message]
2018-06-05 8:29 ` Carlos Maiolino
2018-06-05 13:46 ` Stefan Ring
2018-06-05 14:19 ` Eric Sandeen
2018-06-05 14:46 ` Stefan Ring
2018-06-05 17:34 ` Chris Murphy
2018-06-12 18:53 ` Stefan Ring
2018-06-12 18:56 ` Eric Sandeen
2018-06-13 22:02 ` Dave Chinner
2018-06-14 2:11 ` Eric Sandeen
2018-06-14 15:47 ` Stefan Ring
-- strict thread matches above, loose matches on Subject: below --
2018-09-12 8:07 Troels Hansen
2018-09-12 10:59 ` Carlos Maiolino
2018-09-12 11:39 ` Troels Hansen
[not found] ` <notmuch-sha1-960c954e5404b5b2f083d150633af0b7848ec14c>
2018-09-12 16:39 ` Carlos Maiolino
2018-09-13 4:19 ` Dave Chinner
2018-09-13 5:21 ` Troels Hansen
2018-09-13 6:18 ` Dave Chinner
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=0ae6d0d5984dcd9c703720bdf41b6da1333267b0.camel@quantentunnel.de \
--to=mondsuechtig@quantentunnel.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).