public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Kukard <nkukard@lbsd.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Bug#328135: kernel-image-2.6.11-1-686-smp: nfs reading process stuck in disk wait
Date: Thu, 15 Sep 2005 18:46:43 +0000	[thread overview]
Message-ID: <4329C193.9070708@lbsd.net> (raw)
In-Reply-To: <4N34g-7De-15@gated-at.bofh.it>

[-- Attachment #1: Type: text/plain, Size: 488 bytes --]

Most interesting thing is that I also had a similar problem, I have a
client with a Samba server and about 500Gb of harddrive space.

The Samba server maintains a large number of locks on files due to
employees not closing the software they using before going home, it is
backed up over NFS to external drives every evening.

About 50% of the backups hang in a D state while trying to access files,
these D states last indefinitly even when locks are dropped on the Samba
server.

-Nigel

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

       reply	other threads:[~2005-09-15 18:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4Mpqc-7h0-23@gated-at.bofh.it>
     [not found] ` <4MxnE-1Z7-5@gated-at.bofh.it>
     [not found]   ` <4MPuc-4iZ-1@gated-at.bofh.it>
     [not found]     ` <4MQzZ-5PL-9@gated-at.bofh.it>
     [not found]       ` <4MXrT-7xn-29@gated-at.bofh.it>
     [not found]         ` <4N34g-7De-15@gated-at.bofh.it>
2005-09-15 18:46           ` Nigel Kukard [this message]
     [not found] <20050913194707.8C8C28E6F0@ayer.connecterra.net>
2005-09-14  2:51 ` Bug#328135: kernel-image-2.6.11-1-686-smp: nfs reading process stuck in disk wait Horms
2005-09-14 23:58   ` Trond Myklebust
2005-09-15  1:10     ` Marc Horowitz
2005-09-15  8:32       ` Trond Myklebust
2005-09-15  9:22         ` Horms
2005-09-15  9:44           ` Trond Myklebust
2005-09-15 14:29         ` Marc Horowitz

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=4329C193.9070708@lbsd.net \
    --to=nkukard@lbsd.net \
    --cc=linux-kernel@vger.kernel.org \
    /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