xfs
[Top] [All Lists]

Re: Crash with 3.8.3 and TuxOnIce

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: Crash with 3.8.3 and TuxOnIce
From: Pedro Ribeiro <pedrib@xxxxxxxxx>
Date: Thu, 21 Mar 2013 17:45:25 +0000
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Al/qm3Np3phbtL7ed4PEPPiQzMiDKAisKs6ZaAEqpTk=; b=t1aJUbthS5kod3D+ocOpFN0uV4yPDtmyWnZIjrkQ6aiBpRiQA10ZqtZ5esK9mXuIew tD5taj90v7vXy4i0LNRLZUrVT9eFPVL6u1WPZ5yODvPimBMh8zCGr9UwUcpqX8QoDQB4 k7Evgj6Y19mvp61oaGcX3Yncxc645dg4l5IVRjogvHDC03kq8kpuS6FM+ORInN0odurP PNHY4zJU89Rkh4qQpIipqR+Z53fDX+Y8k7hGJBDDBfxzSMbtTaYGTKIj3PTKiIiI0SE0 FBAYtrA/zV/WeQIPWH1hmH5cPNHrAqcOyQfMPYXqPEPOTfzubc1rmXInUICePBqPa9A9 rR8Q==
In-reply-to: <20130321010149.GF17758@dastard>
References: <CAEDdjHeo3Giv3Y8pLfYHSbJi07_dv7ywzinCSSkxUwBQe-1fsw@xxxxxxxxxxxxxx> <20130320004405.GC17758@dastard> <CAEDdjHc139n-FFrW34FLyfKsqFHBy0_LVcVT24aLyCpb4DC9dA@xxxxxxxxxxxxxx> <20130321010149.GF17758@dastard>



On 21 March 2013 01:01, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
On Wed, Mar 20, 2013 at 06:01:35PM +0000, Pedro Ribeiro wrote:
> Thanks for the answer Dave.
>
> Yes I would definitely say it's a ToI bug that perhaps has been dormant so
> far. Unfortunately the ToI developer is very busy at the moment, so I will
> have to debug and fix it myself.
> This problem did not occur with 3.7 and the ToI code did not change.
>
> Do you have any idea where I can start looking for the XFS change in 3.8
> that triggered this behaviour in ToI? Or maybe it was a VFS change?

It's almost certainly an XFS change that triggered it, but it
indicates (once again) that the hibernate code is simply not
quiescing filesystems properly (i.e. by freezing them). The work
that caused this problem is stopped by the filesystem when it
is frozen, and started again when it is thawed...

> PS: the email definitely bounced back, most likely because imageshack is
> blocked on the sgi server:
>
> Technical details of permanent failure:
> Google tried to deliver your message, but it was rejected by the server for
> the recipient domain oss.sgi.com by cuda-allmx.sgi.com. [192.48.176.16].
>
> The error that the other server returned was:
> 554 rejecting banned content

IOWs, a stupid spam filter.

I'll see if I can get this fixed.

Cheers,

Dave.
--
Dave Chinner
david@xxxxxxxxxxxxx

Actually I've nailed it down to a commit between 3.7.1 and 3.7.10. I'll do some git bisection and come back with the results.

Regarding ToI and filesystem freezing, I guess I need to start delving into the code to see if I can fix it - long but fun journey ahead I guess.

Regards,
Pedro 

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