xfs
[Top] [All Lists]

Re: Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1

To: xfs@xxxxxxxxxxx
Subject: Re: Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1
From: Stefan Priebe - Profihost AG <s.priebe@xxxxxxxxxxxx>
Date: Mon, 01 Nov 2010 14:48:14 +0100
In-reply-to: <20101101142933.4911a30c@xxxxxxxxxxxxxx>
References: <4CC67450.9020602@xxxxxxxxxxxx> <20101026092205.086c0d89@xxxxxxxxxxxxxx> <4CC68249.7050409@xxxxxxxxxxxx> <4CCE73C8.8070705@xxxxxxxxxxxx> <20101101122751.GL2715@dastard> <4CCEB27E.1000605@xxxxxxxxxxxx> <20101101142933.4911a30c@xxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Thunderbird/3.0.10

Did you run the "verify" round on the array after the upgrade? That
would rebuild all checksum and insure that the RAID is fully coherent.
If the verify comes out with any message, there is a sloght chance that
the data on disk wasn't entirely coherent or clean.

shure i have - was done without any problems.


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