From: Brian J. Murrell <Brian.Murrell@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Centos 5.2 with Lustre 1.6.5.1
Date: Wed, 30 Jul 2008 10:41:20 -0400 [thread overview]
Message-ID: <1217428880.13569.247.camel@pc.ilinx> (raw)
In-Reply-To: <52ce537f0807291125r5d27fcf1m5710838a8e27e93c@mail.gmail.com>
On Tue, 2008-07-29 at 11:25 -0700, SoVo Le wrote:
> Hi,
>
> If someone could help me out on this: Why can't I mount lustre ?
This list is for discussions of lustre development only. Please use
lustre-discuss for questions such as this.
I have an answer for your question but in order to prevent any further
follow-up to this list of this topic I will hold off answering it until
you post your question to lustre-discuss.
Cheers,
b.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20080730/02f0b13e/attachment.pgp>
prev parent reply other threads:[~2008-07-30 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 18:25 [Lustre-devel] Centos 5.2 with Lustre 1.6.5.1 SoVo Le
2008-07-30 14:41 ` Brian J. Murrell [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=1217428880.13569.247.camel@pc.ilinx \
--to=brian.murrell@sun.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.