xfs
[Top] [All Lists]

Re: XFS File system in trouble

To: lrhorer@xxxxxxxxxxxx
Subject: Re: XFS File system in trouble
From: Martin Papik <mp6058@xxxxxxxxx>
Date: Mon, 20 Jul 2015 11:05:43 +0300
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=nilNZEkGvHw8SqG87YHaHbq0QygqP5vsrxF98wYtHHI=; b=obV8mJ2zF8QsVgIc2LEXf79p1tXMPniM2gM+IRoLoJ1Tw7j3pZKipzy+pos1OMzTix TyGmf+rQt7IIUYXXu5ENgJQhjuyqXPg2n58sCaC8ppmpOATZAEF85dOKyqreG2wC4EzA ObFjp5tjjbbobFUfm6txweYTHP2n6Cy8oIbNhzt9JDCUQM6OI2iCFu9yp7bvPeD9S/XI 1VMAqTP0Qs38K4HgwKpAlFvq9II5RiiUergPH0JTE9qPIj9xek2qxTnXXtTvBEWU26rf 1u+TqYqV3VH0cbkFZ3iZ/CQa4swtQ+Lg9YXE1FCjhRx7bDRxxJtrcst9P/O9nlB/5puI pPTg==
In-reply-to: <55ACA615.10501@xxxxxxxxxxxx>
References: <03864DDC681E664EBF5D47682BE7D7CF0D3574DF@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <55AA5FCE.4080702@xxxxxxxxxxx> <03864DDC681E664EBF5D47682BE7D7CF0D358740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <CAN3tLtJuk3LKHtxvbXATBR7bjr2e=GTX-fgs-jQniuxqRXjeoA@xxxxxxxxxxxxxx> <55AAF73A.4040903@xxxxxxxxxxxx> <20150719232754.GS7943@dastard> <55ACA615.10501@xxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512


Since you've already found one HW related fault, would you consider
booting into memtest for a couple of passes just to be on the safe
side. And did you by any chance look at SMART if applicable and
possibly running a test on the drives. Another test I sometimes do
when I'm unsure about disks is "cat /dev/sda > /dev/null" (i.e. a
whole disk read test) and see (dmesg) if any errors show up, unless
you're willing to run badblocks in a read-write nondestructive mode.
In my experience the read test or badblocks can be run simultaneously
with smartctl -t long. But as a start I'd look at smartctl --all
/dev/sd? and see if there are any bad signs. I hope this helps. Good luck


On 07/20/2015 10:41 AM, Leslie Rhorer wrote:
> On 7/19/2015 6:27 PM, Dave Chinner wrote:
>> On Sat, Jul 18, 2015 at 08:02:50PM -0500, Leslie Rhorer wrote:
>>> 
>>> I found the problem with md5sum (and probably nfs, as well).
>>> One of the memory modules in the server was bad.  The problem
>>> with XFS persists.  Every time tar tried to create the
>>> directory:
>> 
>> Now you need to run xfs_repair.
> 
> I do that every time the array implodes.  It makes no difference. 
> It never mentions cleaning the structure tar says needs cleaning,
> and the next time I run tar on that file, the filesystem craters.
> 
> _______________________________________________ xfs mailing list 
> xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJVrKuzAAoJELsEaSRwbVYrdjoP/3n1W9YtcpdiDoylp6tDYcjF
vEVz7IWLv2cOky8Lp+0WAZ4Z0WMhcutFzT571H1Vc+jT/UgO25pQHa3yLYTboPuZ
+tBidVUycs7ZIr9QCZFs2uPQ/7YstamB+F7paCTMKtOJJr5CZLiYX4iyJ9sFmWVY
UFPAIhyoqD5CFgoaAkwCmk50kNiT0aPM7egizIUVEt14cWuxZxMN0NIJ5b0WJfAk
qtNQjstVI/xYDgsImm2ZAm19SfOG9ltm2G9zafRr6lR6rRtXjtZX8zEg0l/o9XUw
OifghjoSup8OCzvX6+4+Soj/3mCKZv4rkBm3exf4YzfQ9eVG6Ktele2rLIs1sl3O
hUrZUNEl8hYGJeb5gBHFV/TLWDMMwNde/6JiBVy0V8EbDF1lvR4jYpUwThOE0jyL
ZbzZe4N/B0qvB1OpLDkHrMVm9NPtDkfXdTtM2kRmo5955xtkK09yHF/v64kz7IKc
2rM5pOwTR6HWE8RF2j9UujgPjw6nEUuY01TvIMGYzMfkJTI+sVjeDQfwnPG8tzIa
x4uLa4vTrBD5IaICjAmQiY69qqmt5Vg42G4latZVTYQLelvWQ774mXZfgfT/GtbT
RKzVwvYowWr/EBhtp7ix/1rWANTFiX0lxOPnRmUFvu8UJnyZhR0/EYbJYy1+jTt7
O7hZMfAayQBsnVcSK1JC
=3Ubd
-----END PGP SIGNATURE-----

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