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:08:53 +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:content-id; bh=567PNAHofymfooHot3kW2wopKyBAZAToiyHWKFtkWC8=; b=KhUAOV9OyEDDh/zdBVe0mh4zKi/L4xylaoJmDDOp60r0ss+igIkKppoESXqnUD8+VR UD3S94e56gvMSqXMnH23vikiyDphzcXHzw713zPHfqovMsACqlT6rsWyE/0uiFlQBmfl YZLGgJF74XxyWznzKcWX9KTH3XR/aA0vJSj2B/KcX6FyLsp9SwND2xgb8k1LFgLGbvhp k0htlFQLXSkA2TBylm5r+72SamLkwySf01MXIJG2CZUjKW93ZUsL8Hk1hx/0XdDAauh6 z88JFEdS076mPlQL0XiELGyE7+74mtZZax7FtPMv0S6fPr9rgXIhXJIdPHSFkH6XrPb4 qpQQ==
In-reply-to: <20140811161445.GA7696@xxxxxxxxxxxxxxx>
References: <alpine.LSU.2.11.1407021104480.9881@xxxxxxxxxxxxxxxxx> <alpine.LSU.2.11.1408111559280.2447@xxxxxxxxxxxxxxxxxxxx> <53E8D9F6.7080704@xxxxxxx> <alpine.LSU.2.11.1408111720170.7326@xxxxxxxxxxxxxxxxxxxx> <20140811161445.GA7696@xxxxxxxxxxxxxxx>
Sender: Carlos Robinson <robin.listas@xxxxxxxxx>
User-agent: Alpine 2.11 (LSU 23 2013-08-11)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Content-ID: <alpine.LSU.2.11.1408111908330.7326@xxxxxxxxxxxxxxxxxxxx>


El 2014-08-11 a las 12:14 -0400, Brian Foster escribiÃ:
On Mon, Aug 11, 2014 at 05:34:46PM +0200, Carlos E. R. wrote:


This reminds me that it might be interesting to tune the eofblocks
scanner to be more aggressive and see if that helps reproduce. This
thread that's running here normally runs every 5 minutes by default, but
it can be tuned to run at a user-defined interval via the following
/proc file:

# cat /proc/sys/fs/xfs/speculative_prealloc_lifetime
300

I wonder if setting it to 30s or so ('echo 30 > /proc/...') and running
some hibernation cycles would help...

Ok, I can try that.

- -- Cheers
       Carlos E. R.

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

iF4EAREIAAYFAlPo+K0ACgkQja8UbcUWM1zxVgD+LFcJ3OBRJhn9LVrwFxf98H1u
n7ubtexF8XXKWcUdjv0A/Ail1kzWxIgQkevunUQ/3UnbthtWqnyniHP4qKVUWv8m
=AauB
-----END PGP SIGNATURE-----
<Prev in Thread] Current Thread [Next in Thread>