From: "Joshua J. Kugler" <joshua@azariah.com>
To: "Alexis GÜNST HORN" <alexis.gunsthorn@outscale.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: CephFS issue
Date: Tue, 15 Jan 2013 00:35:11 -0900 [thread overview]
Message-ID: <13344378.XMpKyabt7g@hosanna> (raw)
In-Reply-To: <CAEqYNSYaMvprh580HNosaQe7ahMmT-iB9irMsgA87tE2fwtCTQ@mail.gmail.com>
On Monday, January 14, 2013 08:51:57 Alexis GÜNST HORN wrote:
> At the end, the client mountpoint become unresponsive, and the only
> way is to force reboot.
I am going to throw this out there as I've seen something similar, but not
with ceph. Back in 2005-ish I was experimenting with ATA over Ethernet.
Running bonnie++ against the targets or some such. During the tests, they
would just hang, and I couldn't kill the process, just had to reboot.
What it ended up being was the I/O (or bonnie++ ?) was using so much memory
Linux wasn't allocating space for network buffers, killing network I/O. Well,
since this was a network block file system, that was kind of crucial, and the
mount points would hang, and they wouldn't recover.
Again, I have no idea if this has anything to do with your issue, but the
"lots of I/O followed by a hang requiring a reboot" rang bells...just maybe
not the right ones. :)
j
--
Joshua J. Kugler - Fairbanks, Alaska
Azariah Enterprises - Programming and Website Design
joshua@azariah.com - Jabber: pedahzur@gmail.com
PGP Key: http://pgp.mit.edu/ ID 0x73B13B6A
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-01-15 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 7:51 CephFS issue Alexis GÜNST HORN
2013-01-14 9:07 ` Wido den Hollander
2013-01-14 9:21 ` Alexis GÜNST HORN
2013-01-15 9:35 ` Joshua J. Kugler [this message]
[not found] ` <CAKMAVE8w-HYuKiLXy3Nt+q3=CgiAzxjqwmJXpv4mUkHGp5bU-Q@mail.gmail.com>
2013-01-16 9:17 ` Alexis GÜNST HORN
2013-01-16 9:52 ` Andrey Korolyov
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=13344378.XMpKyabt7g@hosanna \
--to=joshua@azariah.com \
--cc=alexis.gunsthorn@outscale.com \
--cc=ceph-devel@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 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.