xfs
[Top] [All Lists]

Re: Subject : Happened again, 20140811 -- Got "Internal error XFS_WANT_C

To: XFS mailing list <xfs@xxxxxxxxxxx>
Subject: Re: Subject : Happened again, 20140811 -- Got "Internal error XFS_WANT_CORRUPTED_GOTO". Filesystem needs reformatting to correct issue.
From: "Carlos E. R." <carlos.e.r@xxxxxxxxxxxx>
Date: Mon, 11 Aug 2014 19:05:00 +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=Q96VhsAFi2kT6RZU/CyBW4V/obSq7vOAbDhNwj/SEFQ=; b=vZltelNfXQo+PoJdUpC6y2yKbtmW5X3uwkw9Ag6X3CHbtruI4P3apHES8aXLOBqJA6 CNDaDfzkLAARuVkRZzIpCjS60sHaa+IUmZ3Uz9C9QEahLsEsTTgU/cLQ0QP9I6fb43VF 0IqAcSzKmDCOK62oUg2O8oNnPP9E2kQgveTxUySx7qjDofWx0GTMt86blrvfc3jddYPr DUg0X18upNkQO7Lh9CmsguL5E5KePmpW2aW319go467s413QPwmNr5xbeXFKthi3iSFe 83JecYOPg4iE9CkzDHGkKbKQTS0nMdKz0XO62gCjyt+sZFGiu9vMtKCjkr19oUtMfFQM 3kjw==
In-reply-to: <alpine.LSU.2.11.1408111657160.7326@xxxxxxxxxxxxxxxxxxxx>
References: <alpine.LSU.2.11.1407021104480.9881@xxxxxxxxxxxxxxxxx> <alpine.LSU.2.11.1408111559280.2447@xxxxxxxxxxxxxxxxxxxx> <20140811144359.GA10217@xxxxxxxxxxxxxx> <alpine.LSU.2.11.1408111657160.7326@xxxxxxxxxxxxxxxxxxxx>
Sender: Carlos Robinson <robin.listas@xxxxxxxxx>
User-agent: Alpine 2.11 (LSU 23 2013-08-11)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



El 2014-08-11 a las 16:58 +0200, Carlos E. R. escribiÃ:

Ok, will do.

I will create a backup of my partition, with xfsdump, after attempting
repair of the partition, and reboot, and see (without the reformat cycle).

At this instant I'm doing a full dd of the partition, just in case it
becomes useful.

linux:/run/media/linux/d_storage/xfs_disaster_home/20140811 # xfs_repair -V
xfs_repair version 3.1.11

It is a live system, so I acan't update it. If I boot from the main system, that has a more modern xfs_repair, systemd will attempt mount and automated repair, and we will not get any logs.

linux:/run/media/linux/d_storage/xfs_disaster_home/20140811 # xfs_repair -v 
/dev/sdd5
Phase 1 - find and verify superblock...
        - block cache size set to 753952 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 65662 tail block 65607
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_repair.  If you are unable to mount the filesystem, then use
the -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.
linux:/run/media/linux/d_storage/xfs_disaster_home/20140811 #


linux:/run/media/linux/d_storage/xfs_disaster_home/20140811 # mount -v 
/dev/sdd5 mnt/
mount: /dev/sdd5 mounted on 
/run/media/linux/d_storage/xfs_disaster_home/20140811/mnt.
linux:/run/media/linux/d_storage/xfs_disaster_home/20140811 # umount mnt
linux:/run/media/linux/d_storage/xfs_disaster_home/20140811 #

dmesg:

[10266.034290] XFS (sdd5): Mounting Filesystem
[10266.073739] XFS (sdd5): Starting recovery (logdev: internal)
[10266.690325] XFS (sdd5): Ending recovery (logdev: internal)
linux@linux:~>

dmesg --ctime

[Mon Aug 11 16:47:12 2014] XFS (sdd5): Mounting Filesystem
[Mon Aug 11 16:47:12 2014] XFS (sdd5): Starting recovery (logdev: internal)
[Mon Aug 11 16:47:12 2014] XFS (sdd5): Ending recovery (logdev: internal)
linux@linux:~>



linux:/run/media/linux/d_storage/xfs_disaster_home/20140811 # xfs_repair -v 
/dev/sdd5
Phase 1 - find and verify superblock...
        - block cache size set to 753952 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 65700 tail block 65700
        - scan filesystem freespace and inode maps...
block (1,12608397-12608397) multiply claimed by cnt space tree, state - 2
agf_freeblks 27745492, counted 27745496 in ag 1
sb_fdblocks 115565042, counted 115565046
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 2
        - agno = 1
        - agno = 3
        - agno = 0
Phase 5 - rebuild AG headers and trees...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...

        XFS_REPAIR Summary    Mon Aug 11 16:48:08 2014

Phase           Start           End             Duration
Phase 1: 08/11 16:47:49 08/11 16:47:49 Phase 2: 08/11 16:47:49 08/11 16:47:52 3 seconds
Phase 3:        08/11 16:47:52  08/11 16:48:07  15 seconds
Phase 4: 08/11 16:48:07 08/11 16:48:07 Phase 5: 08/11 16:48:07 08/11 16:48:07 Phase 6: 08/11 16:48:07 08/11 16:48:07 Phase 7: 08/11 16:48:07 08/11 16:48:07

Total run time: 18 seconds
done
linux:/run/media/linux/d_storage/xfs_disaster_home/20140811 #


I don't understand all it says, but aparently it does not detect any problem.

dmesg doesn't have any more entries.


Now I'm going to create an xfsdump of it, and reboot, without rebuilding. Then I'll upload the metadata to google drive.

- -- Cheers
       Carlos E. R.

       (from 13.1 x86_64 "Bottle" (Minas Tirith))

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iF4EAREIAAYFAlPo98kACgkQja8UbcUWM1y78wD+MznL/4Ht53XAOw+CN/4ThhqQ
P4cN85akyVugU+T6zusA/313Z3PHezJe2oUTx1dFpQpV8Lf+LSgtlHVZ0M4xL+sz
=/iid
-----END PGP SIGNATURE-----
<Prev in Thread] Current Thread [Next in Thread>