xfs
[Top] [All Lists]

Re: Got "Internal error XFS_WANT_CORRUPTED_GOTO". Filesystem needs refor

To: XFS mailing list <xfs@xxxxxxxxxxx>
Subject: Re: Got "Internal error XFS_WANT_CORRUPTED_GOTO". Filesystem needs reformatting to correct issue.
From: "Carlos E. R." <carlos.e.r@xxxxxxxxxxxx>
Date: Sat, 12 Jul 2014 03:30:17 +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=zx+UaK7+mPOmczNMUrPwQT7QevdFqu3f9jxak/cZNQQ=; b=nXP9HWCpoPmkIuQ8mhfuX8RGkxm+g47Wyy/oeMbFzpTMJVUrH0EGNX7dK5sDnvUtgX IJCjv1KQahwSEwTMwrpgp9x+sK+/fn8Y2+XBBOa39eGwzWJoaas/hag0QtvL/VoKeQc5 0YfWijwx+4fxg7E+7mp6n00y0eRgYv/Kh7/ztvB98rsxcbi1uCM08FSHSi3tSD2O/es+ 8NccFUhRGee915qzl5+BLsD8vm10CiFy3UU2TGEAU7vZBHn2uPjqiOLVtJq6RmvcAIiV 538RdRaAMpPkdh/Zm34uv1fsxfc3qdMVVyHKo2uqcAU6LEDuZfue02DojSKcQw/K+xVB ET5A==
In-reply-to: <alpine.LSU.2.11.1407120150220.15907@xxxxxxxxxxxxxxxxx>
References: <alpine.LSU.2.11.1407021104480.9881@xxxxxxxxxxxxxxxxx> <20140702120441.GA51757@xxxxxxxxxxxxxxx> <alpine.LSU.2.11.1407030057310.9881@xxxxxxxxxxxxxxxxx> <20140703173916.GB3452@xxxxxxxxxxxxxx> <alpine.LSU.2.11.1407040135140.9881@xxxxxxxxxxxxxxxxx> <20140705122833.GA3573@xxxxxxxxxxxxxxx> <alpine.LSU.2.11.1407120150220.15907@xxxxxxxxxxxxxxxxx>
Sender: Carlos Robinson <robin.listas@xxxxxxxxx>
User-agent: Alpine 2.11 (LSU 23 2013-08-11)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On Saturday, 2014-07-12 at 02:30 +0200, Carlos E. R. wrote:
On Saturday, 2014-07-05 at 08:28 -0400, Brian Foster wrote:

[xfs_metadump]

It's here:

<https://drive.google.com/file/d/0Bx2OgfTa-XC9UDBnQzZIMTVyN0k/edit?usp=sharing>

Whoever wants to read it, has to tell me the address to add to it, access
is not public.

Wait.

I just found out that I did something very wrong. That xfs_metadump file is very wrong, it is not look to be the correct one.


The info on it says:


Telcontar:/data/storage_d/old_backup # xfs_info tgtfile
meta-data=/dev/sdf2 isize=256 agcount=4, agsize=122341568 blks
         =                       sectsz=512   attr=2, projid32bit=0
         =                       crc=0
data     =                       bsize=4096   blocks=489366272, imaxpct=5
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
log      =internal               bsize=4096   blocks=238948, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0


while the currently mounted home says:


elcontar:~ # mount | grep home
/dev/sde5 on /home type xfs (rw,noatime,attr2,inode64,noquota)

Telcontar:~ # xfs_info /dev/sde5
meta-data=/dev/sde5 isize=256 agcount=4, agsize=32000000 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=0
data     =                       bsize=4096   blocks=128000000, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=0
log      =internal               bsize=4096   blocks=62500, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
Telcontar:~ # mount | grep /home




So, please wait till I verify things again. Tomorrow, it is 3 AM here. Sorry :-(


Unless "xfs_info tgtfile" gives the information about the device where "tgtfile" is stored (/dev/sdf2), not on the image file itself :-?


I'm very confused.


- -- Cheers,
       Carlos E. R.
       (from 13.1 x86_64 "Bottle" at Telcontar)

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

iEYEARECAAYFAlPAj6kACgkQtTMYHG2NR9X+IwCeJtpsS6XJJ1xNeLPmb6PlXA8D
C9IAn1hn1g/ty/41dG5h4ijQoXqs1N7G
=Xtcq
-----END PGP SIGNATURE-----

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