On Sun, Jun 03, 2018 at 04:32:24AM +0200, Thorsten Hufnagel wrote: > 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 > > Good it worked out, but: > > " > > 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... Please at least translate the message to english before posting it to the list Me and several other developers on the list doesn't speak a single word in German, and going to the .po files to find the translation is too time consuming. Cheers. > > 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 > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Carlos -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
