public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Piotr Kandziora <piotr.kandziora@open-e.com>
Cc: Janusz@oss.sgi.com, Artur Piechocki <artur.piechocki@open-e.com>,
	lukasz.wittig@open-e.com, Bak <jb@open-e.com>,
	xfs@oss.sgi.com
Subject: Re: XFS: I/O Error Detected / 2.6.27.39
Date: Wed, 17 Nov 2010 12:35:17 +0100	[thread overview]
Message-ID: <20101117123517.6964c335@harpe.intellique.com> (raw)
In-Reply-To: <4CE3B1C0.3060308@open-e.com>

Le Wed, 17 Nov 2010 11:43:12 +0100
Piotr Kandziora <piotr.kandziora@open-e.com> écrivait:

> - debian based distribution with a lot of modification,
> - architecture x86_64,

So this isn't a case of 32 bits rsync running out of memory (case
seen...)

> - xfs tools version 2.10.1
> - mount options for this LV: 
> rw,noatime,nodiratime,attr2,nobarrier,usrquota,prjquota,grpquota
> - NFS share is exported with following options: 
> rw,no_root_squash,insecure,insecure_locks,async,anonuid=65534,anongid=65534,subtree_check
> 
> >> Unfortunately our system is freezing unexpectedly without reason.
> >>      
> > What are the symptoms ? does the whole system freeze up? Or does it
> > crash with kernel panic, or otherwise "Oops" messages?
> >    
> 
> Symptoms are different. One time we've got a few oom-killers:

This is abnormal, but kernel disk cache shouldn't interfere anyway.

> [kern.warning] kernel: load_average invoked oom-killer:

> [kern.warning] kernel: 3dm2 invoked oom-killer: gfp_mask=0xd0,

> 2010/11/11 10:56:21|Pid: 4324, comm: nfsd Not tainted 

> Filesystem "dm-37": xfs_log_force: error 5 returned.

This looks like an IO error, as Eric Sandeen said. 

> We've checked temperature on each disk using LSI/3ware CLI (tw_cli)
> and average is 35C.

It's the card itself that's overheating and fails, not the disks. I had
to replace quite a number of these on field after a year of use or two;
they work well for a while, but crash when heavily sollicited.

However this should cause a complete IO freeze. Did you try to run
something like "tw_cli alarms" right after the failure?

If tw_cli can't communicate with the controller anymore, than that's a
case of a fried card.

> This problem occurred two times in the past, we repaired fs using 
> xfs_repair (and it showed errors). We simulated it using dumping
> cache yesterday ...

I don't understand how or why dumping cache would cause the system to
fail... except that it may augment actual disk IOs.

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

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

  reply	other threads:[~2010-11-17 11:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 13:10 XFS: I/O Error Detected / 2.6.27.39 Piotr Kandziora
2010-11-16 20:44 ` Emmanuel Florac
2010-11-17 10:43   ` Piotr Kandziora
2010-11-17 11:35     ` Emmanuel Florac [this message]
2010-11-17 21:17     ` Michael Monnerie
2010-11-16 21:54 ` Eric Sandeen

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=20101117123517.6964c335@harpe.intellique.com \
    --to=eflorac@intellique.com \
    --cc=Janusz@oss.sgi.com \
    --cc=artur.piechocki@open-e.com \
    --cc=jb@open-e.com \
    --cc=lukasz.wittig@open-e.com \
    --cc=piotr.kandziora@open-e.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