All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fyodor Ustinov <ufm@ufm.su>
To: Sage Weil <sage@newdream.net>
Cc: ceph-devel@vger.kernel.org
Subject: Re: 0.31
Date: Mon, 11 Jul 2011 00:29:16 +0300	[thread overview]
Message-ID: <4E1A19AC.8060304@ufm.su> (raw)
In-Reply-To: <Pine.LNX.4.64.1107101411040.10951@cobra.newdream.net>

On 07/11/2011 12:12 AM, Sage Weil wrote:
> Hmm, yeah the 'loaded dup inode' messages should never happen.  They
> appear to be just files, though, not directories, so you can safely ignore
> them.  The namespace repair will need to clean that up at some point. The
> recursive rstat errors you saw are probably just fallout from that, and
> can also be ignored.
I understand it correctly, that until not  implemented the Feature # 86 
I have no way to fix this?
> I'm curious how you got into that state, though.  Are you running a single
> or clustered mds?  Is the workload purely amanda?
Single mds. I have these clients:
1. Amanda. Used cfuse.
2. Gate. Used cfuse. NFS gate.
3. One experimental server with many different workloads.

WBR,
     Fyodor.

P.S. My friends have always said that I can find a bug in the software, 
even where it can not be. Sometimes it interferes. :)

I will try again to use ceph with BackupPC. Last time it was over "brain 
explosion" in ceph. :)

  reply	other threads:[~2011-07-10 21:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-10 10:48 0.31 Fyodor Ustinov
2011-07-10 13:24 ` 0.31 Fyodor Ustinov
2011-07-10 21:12 ` 0.31 Sage Weil
2011-07-10 21:29   ` Fyodor Ustinov [this message]
2011-07-10 21:36     ` 0.31 Sage Weil
2011-07-10 21:53       ` 0.31 Fyodor Ustinov

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=4E1A19AC.8060304@ufm.su \
    --to=ufm@ufm.su \
    --cc=ceph-devel@vger.kernel.org \
    --cc=sage@newdream.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.