public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ling Ho <ling@slac.stanford.edu>
To: Dave Chinner <david@fromorbit.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Debugging file truncation problem
Date: Wed, 20 Jun 2012 23:30:12 -0700	[thread overview]
Message-ID: <4FE2BF74.9010406@slac.stanford.edu> (raw)
In-Reply-To: <20120621060249.GR30705@dastard>

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?

I will try to open a ticket with Red Hat.

Thanks,
...
ling

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-06-21  6:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21  1:51 Debugging file truncation problem Ling Ho
2012-06-21  6:02 ` Dave Chinner
2012-06-21  6:30   ` Ling Ho [this message]
2012-06-21  9:01     ` Dave Chinner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FE2BF74.9010406@slac.stanford.edu \
    --to=ling@slac.stanford.edu \
    --cc=david@fromorbit.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox