All of lore.kernel.org
 help / color / mirror / Atom feed
From: White, Cliff <cliff.white@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Kernel crash from "mkfs.lustre --index" setting
Date: Fri, 11 Oct 2013 18:30:56 +0000	[thread overview]
Message-ID: <CE7D90F6.722B%cliff.white@intel.com> (raw)
In-Reply-To: <CABgxfbE1LruxE8Uc-Vb_JnEyRnJcC8FUa0Q-kPjNNgT6zR7oCg@mail.gmail.com>

On 10/11/13 10:59 AM, "Wendy Cheng" <s.wendy.cheng@gmail.com> wrote:

>On Fri, Oct 11, 2013 at 10:41 AM, White, Cliff <cliff.white@intel.com>
>wrote:
>
>> 1.
>> --index is used to enumerate OSTs and MDT, when using DNE.
>> The index MUST be unique, and indexes must not have gaps.
>
>I see ... index must not have gaps. However, a user error could crash
>the kernelr . Does that sound right ? .

Well, creating the filesystem is normally done by admins, not users, but
yes, it shouldn't crash.
Lustre-devel is the place for your patch, sorry I wasn't clear. -discuss
is more for the 'why are their indexes' type of questions. :)
>
>>
>> 3. Surprise you how?
>>
>> HPDD-discuss is likely a better list for these sorts of questions,
>> lustre-devel is for code development.
>
>Thanks .. I'll move the discuss there sometime next week. It looks to
>me Lustre is doing sync to the disks all the time vs. other network
>filesystem (e.g. NFS) that does caching quite aggressively.

Yes, Lustre by design does direct IO to disk, and does not cache data on
the servers. 
Some caching can be enabled, but in general no, you should not see the
servers caching.

However, the clients should be using the normal Linux block cache, if the
clients are not caching
There may be an issue with your setup.
Cliffw

>
>-- Wendy
>

  reply	other threads:[~2013-10-11 18:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-11 17:11 [Lustre-devel] Kernel crash from "mkfs.lustre --index" setting Wendy Cheng
2013-10-11 17:41 ` White, Cliff
2013-10-11 17:59   ` Wendy Cheng
2013-10-11 18:30     ` White, Cliff [this message]
2013-10-12  0:47       ` Wendy Cheng

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=CE7D90F6.722B%cliff.white@intel.com \
    --to=cliff.white@intel.com \
    --cc=lustre-devel@lists.lustre.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.