[Top] [All Lists]

Happened again, 20140930 -- Got "Internal error XFS_WANT_CORRUPTED_GOTO"

To: XFS mailing list <xfs@xxxxxxxxxxx>
Subject: Happened again, 20140930 -- Got "Internal error XFS_WANT_CORRUPTED_GOTO". Filesystem needs reformatting to correct issue.
From: "Carlos E. R." <carlos.e.r@xxxxxxxxxxxx>
Date: Wed, 1 Oct 2014 00:27:20 +0200 (CEST)
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:subject:in-reply-to:message-id:references :user-agent:mime-version:content-type; bh=zauITOLEHszyYZrab+Y8tFiYDNkaXJHLvxckV/Vp0OM=; b=W6M5uNjvnONvv0CNOMf++DvbshrDrsM2I16bQKwKyYVRFEim1snpfljQ07hyK2/wGK tFFse4O59toY0/fRGjoEw0wQhwS0rJBXYM6OiFmEcH7jv208EyScNy+SZJAfI4B2Eidl uI8Jod0as8k3z5jTFw0uaOiu2D3wcvyVlNqVgnCCxsXrV33CeCh8nh3tMZHQd7DFNrPp qZUjEGroqY6Jy67r57uNofTpr+jvJ7r12VfvM1HKNy3MZNgaHL7D4cPpK/cbzYYZ7lXk 23ca43J7t64OyBJOR9AIEQtKFZ7kIVhPHFo68Zp5j+cTajjQrtCeTtqDH5JHiwqJKK3t px8g==
In-reply-to: <alpine.LSU.2.11.1408111559280.2447@xxxxxxxxxxxxxxxxxxxx>
References: <alpine.LSU.2.11.1407021104480.9881@xxxxxxxxxxxxxxxxx> <alpine.LSU.2.11.1408111559280.2447@xxxxxxxxxxxxxxxxxxxx>
Sender: Carlos Robinson <robin.listas@xxxxxxxxx>
User-agent: Alpine 2.11 (LSU 23 2013-08-11)
Hash: SHA256

Subject: Subject : Happened again,
    20140811 -- Got "Internal error XFS_WANT_CORRUPTED_GOTO". Filesystem needs
     reformatting to correct issue.
Date: Mon, 11 Aug 2014 16:23:01 +0200 (CEST)

Happened again, I'm on middle of recovery procedures, and using my laptop
to post.

And again.

Well, after I recover the system I'm going to migrate my /home to a small ext4 partition, leaving Documents and the big directories in the current xfs home, renamed to something else. I hope this way to avoid the crashes and corruption on restore from hibernation.

SUSE and openSUSE (12 and 13.2) are switching to use, on new installs by default, btrfs for their root filesystem, and xfs for home. I hope that this will cause more crashes on laptops on return from hibernation, producing more reports, and finally solving the root cause of this.

Or perhaps it does not happen on 13.2, and I'm the only one left having the issue...

Anyway, as I'm using 13.1, and will be for some time, the solution for me is to move the core of /home to ext4, at least temporarily.

If someone wants me to get some data from the partition, I'm willing. I made a full 'dd' of it before attempting mount or repair on it (still pending), it will be possible for some days or more. Time permitting. :-)

- -- Cheers
       Carlos E. R.

       (from 13.1 x86_64 "Bottle" (Minas Tirith))
Version: GnuPG v2.0.22 (GNU/Linux)


<Prev in Thread] Current Thread [Next in Thread>