public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Weber <chaweber@gmail.com>
To: linux-xfs@oss.sgi.com
Subject: Re: xfs partial dismount issue
Date: Mon, 5 Mar 2007 18:25:03 +0000 (UTC)	[thread overview]
Message-ID: <loom.20070305T190248-708@post.gmane.org> (raw)
In-Reply-To: 45EC3DEA.3000105@sandeen.net

Eric Sandeen <sandeen <at> sandeen.net> writes:

> 
> Chuck Weber wrote:
> > Hi everyone, I have a long running problem perhaps you can help with. I
> > will include as much detail as I can. I can set up a spare server-disk
> > set for testing if you have any bright ideas.
> > 
> > We use XFS for samba and nfs on x86_64 Fedora Proliant DL585/385
> > servers. Our busiest server has disk partitions go away. 
> 
> What do you mean by this, exactly?  The partitions themselves go away,
> or are you talking about the problem described below where processes
> start hanging?
> 
Here is an example partition (1 of 6 or more xfs storage only).
/share/store3 with samba shares on /share/store3/lls, lds, lxs and so on.
I will get a call saying my groups share (lxs) is no longer accessable. I ssh
into server and can ls /share/store3 but ls will hang when I ls
/share/store3/lxs. Shortly there after ls will hang for the root or any
directory on the partition. Other partitions will be fine and other samba shares
will be fine until the queued up process load bogs the server down.

> > The other
> > servers do not show this behavior ever. The partitions show as mounted,
> > but access to the partition just hangs. Open file count, process count
> > and load average rise until the server becomes very unresponsive. Even
> > if we catch it before the high load average, because it cannot unmount
> > the partition, it must be powered off and back on to restart. Upon
> > restart all partitions mount properly and everything is fine for days or
> > months. There is nothing in log files that I have noticed. With sar, I
> > can track the files open and process count rise. 
> 
> Maybe try sysrq-t, to capture all backtraces when it's in this state,
> and see where the various threads are at.
> 

OK I'll look over sysrq
> -Eric
> 
> 

  reply	other threads:[~2007-03-05 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05 13:13 xfs partial dismount issue Chuck Weber
2007-03-05 15:57 ` Eric Sandeen
2007-03-05 18:25   ` Charles Weber [this message]
2007-03-05 21:07     ` Roger Heflin
2007-04-02 21:18       ` Charles Weber

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=loom.20070305T190248-708@post.gmane.org \
    --to=chaweber@gmail.com \
    --cc=linux-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