From: Eric Sandeen <sandeen@sandeen.net>
To: Dragon <Sunghost@gmx.de>, xfs@oss.sgi.com
Subject: Re: XFS Filesystem is broken and cant repair and mount!
Date: Sun, 12 Oct 2014 15:39:04 -0500 [thread overview]
Message-ID: <543AE6E8.3040202@sandeen.net> (raw)
In-Reply-To: <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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-12 20:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 20:26 XFS Filesystem is broken and cant repair and mount! Dragon
2014-10-12 20:39 ` Eric Sandeen [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-10-12 20:54 Dragon
2014-10-12 20:56 ` Eric Sandeen
2014-10-12 22:16 ` Dave Chinner
2014-10-10 10:28 Dragon
2014-10-10 8:47 Dragon
2014-10-10 10:17 ` Emmanuel Florac
2014-10-09 22:42 Dragon
2014-10-10 10:07 ` Emmanuel Florac
2014-10-09 21:37 Dragon
2014-10-09 21:48 ` XFS " Dave Chinner
2014-10-09 13:15 Dragon
2014-10-09 15:09 ` Eric Sandeen
2014-10-09 21:20 ` Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=543AE6E8.3040202@sandeen.net \
--to=sandeen@sandeen.net \
--cc=Sunghost@gmx.de \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox