From: Bill Kendall <wkendall@sgi.com>
To: juergen.sauer@automatix.de
Cc: linux-xfs@oss.sgi.com
Subject: Re: Bug in xfsrestore or NFS+XFS Filesystem on NFS Server ? Can anyone confirm ?
Date: Tue, 15 Aug 2006 08:20:41 -0500 [thread overview]
Message-ID: <44E1CA29.7080406@sgi.com> (raw)
In-Reply-To: <200608120956.47466.juergen.sauer@automatix.de>
On 08/12/06 02:56, Juergen Sauer wrote:
> Since that the last restore works, I think there is a bug in xfsrestore or xfs/nfs in the kernel 2.6.17.
> Backupserver, Server, Knoppix are bugfixed 2.6.17(.7). Restoring the dump via nfs failed due "too much open files".
>
> Does xfsrestore opens really 512k files ? I do not belive that.
> So It could a problem in Kernel or NFS Stack be the problem.
Not intentionally, but there could be a file descriptor leak somewhere
in xfsrestore or one of the libraries it uses. Take a look at
/proc/<xfsrestore pid>/fd while the restore is going on and see if the
file descriptor list is growing. If so, it should indicate what files
are being opened but not closed.
Bill
prev parent reply other threads:[~2006-08-15 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-12 7:56 Bug in xfsrestore or NFS+XFS Filesystem on NFS Server ? Can anyone confirm ? Juergen Sauer
2006-08-12 22:57 ` Justin Piszcz
2006-08-15 13:20 ` Bill Kendall [this message]
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=44E1CA29.7080406@sgi.com \
--to=wkendall@sgi.com \
--cc=juergen.sauer@automatix.de \
--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