xfs
[Top] [All Lists]

Re: Debugging file truncation problem

To: Ling Ho <ling@xxxxxxxxxxxxxxxxx>
Subject: Re: Debugging file truncation problem
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Thu, 21 Jun 2012 19:01:11 +1000
Cc: "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>
In-reply-to: <4FE2BF74.9010406@xxxxxxxxxxxxxxxxx>
References: <4FE27E2B.2060705@xxxxxxxxxxxxxxxxx> <20120621060249.GR30705@dastard> <4FE2BF74.9010406@xxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Wed, Jun 20, 2012 at 11:30:12PM -0700, Ling Ho wrote:
> On 6/20/12 11:02 PM, Dave Chinner wrote:
> >On Wed, Jun 20, 2012 at 06:51:39PM -0700, Ling Ho wrote:
> >>Hello,
> >>
> >>I am trying to debug a problem that has bugged us for the last few months.
> >>
> >>We have set up a large storage system using GlusterFS, and XFS
> >>underneath it. We have 5 RHEL6.2 servers (running
> >>2.6.32-220.7.1.el6.x86_64 when problem last occurred), with LSI
> >>9285-8e Raid Controller with Battery Backup Unit. System memory is
> >>48GB.
> >Perhaps you should report the problem to your RedHat support
> >engineer and tell them to raise a bug - it's entire possible that
> >the RH kernel needs this fix:
> >
> >be4f1ac xfs: log all dirty inodes in xfs_fs_sync_fs
> >
> >Cheers,
> >
> >Dave.
> >
> Ok. Is there a bug reference number or thread I can point to?

The above commit is all that is needed - I'll be the person who
fixes the bug in the RH kernel, anyway, so not much else is needed
;)

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

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