xfs
[Top] [All Lists]

Re: XFS Filesystem is broken and cant repair and mount!

To: Dragon <Sunghost@xxxxxx>, xfs@xxxxxxxxxxx
Subject: Re: XFS Filesystem is broken and cant repair and mount!
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Sun, 12 Oct 2014 15:39:04 -0500
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <trinity-79914db3-a491-4219-a68e-72c1d21f16cc-1413145560730@3capp-gmx-bs13>
References: <trinity-79914db3-a491-4219-a68e-72c1d21f16cc-1413145560730@3capp-gmx-bs13>
On 10/12/14 3:26 PM, Dragon wrote:
> 
> Hello,
> i changed the sata cable and upgrade kernel to latest. If i now copy files i 
> got a new failure:
>  XFS: Internal error XFS_WANT_CORRUPTED_RETURN at line 348 of file 
> /build/linux-nBoDV9/linux-3.16.3/fs/xfs/xfs_alloc.c.  Caller 
> xfs_alloc_ag_vextent_size+0x569/0x6c0 [xfs]
> --------------
>  
> I found a forum thread in which another solved the problem and i am not sure, 
> but perhaps i have the same problem. My initial raid was aprox. 6TB and rised 
> step by step to 20TB.
> my xfs_info:
> Metadaten =/dev/md2               isize=256    agcount=112, agsize=45598848 
> blks
>           =                       sectsz=4096  attr=2
> Daten     =                       bsize=4096   BlÃcke=5107057536, imaxpct=5
>           =                       sunit=128    swidth=256 blks
> Benennung =Version 2              bsize=4096   ascii-ci=0
> Protokoll =Intern                 bsize=4096   BlÃcke=521728, Version=2
>           =                       sectsz=4096  sunit=1 blks, lazy-count=1
> Echtzeit  =keine                  extsz=4096   BlÃcke=0, rtextents=0
>  
> Could i have a problem with the group_size?

no.



You changed the cable & upgraded your kernel.  Did you run xfs_repair to fix 
the previous problem which existed on disk?

-Eric

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