On Sep 23, 2008 17:55 -0400, Heald, Nathan T. wrote:
> When I try to start it I get an error (Same error for an upgrade or fresh
> install):
>
> [EMAIL PROTECTED] lustre]# mount -t lustre /dev/mpath/mpath2 /mnt/test/mdt
> mount.lustre: mount /dev/mpath/mpath2 at /mnt/test/mdt failed: No such dev
I was wondering if we should implement quotas for our students but is
there a downside such as performance? Previously, we implemented
quotes using vxfs and we noticed a significant performance hit and the
users were not happy. So, are there any downsides such as performance
loss when using quotas?
Yes it is a symlink. I just now tried mounting the actual block device and am
getting the same error unfortunately. Thanks for the suggestion though.
-Nathan
On 9/24/08 2:59 AM, "Andreas Dilger" <[EMAIL PROTECTED]> wrote:
On Sep 23, 2008 17:55 -0400, Heald, Nathan T. wrote:
> When I try to st
Hello,
I have some difficulties to setup a server acting as metadata server and OST
server. The box has two interfaces, eth0 and eth2. eth0 is the primary
interface and has the ip which is associated with the hostname.
However, I would like to use the eth2 interface for Lustre.
In an ideal case,
On Wed, 2008-09-24 at 21:41 +0200, Lukas Hejtmanek wrote:
> Hello,
Hi,
> I have some difficulties to setup a server acting as metadata server and OST
> server.
Let's start by saying putting an MDS and OSS on the same box is not good
from both a performance and recovery point of view. If that bo
On Sep 24, 2008 06:11 -0400, Mag Gam wrote:
> I was wondering if we should implement quotas for our students but is
> there a downside such as performance? Previously, we implemented
> quotes using vxfs and we noticed a significant performance hit and the
> users were not happy. So, are there any
Hi Lukas,
Do you want to use these interfaces together as a logical unit? The syntax
below would construct two separate LNET networks.
Additionally, you would need to qualify the mount path on the client side to
bind Lustre to a specific LNET instance, i.e. 'mount /mnt/lustre
[EMAIL PROTECTED]:/
On Wed, Sep 24, 2008 at 03:58:36PM -0400, Brian J. Murrell wrote:
> Let's start by saying putting an MDS and OSS on the same box is not good
> from both a performance and recovery point of view. If that box fails,
> recovery can fail.
Well, I guess that for the first tests it could be ok :)
>
>
Greetings,
We have 4 OSS nodes and 2 MDS nodes configured in HA pairs, running
2.6.18-53.1.14.el5_lustre.1.6.5smp, and using the o2ib network
transport. We had multiple failovers recently (possibly due to hardware
problems, but no root cause yet) and managed to get things back again to
what I _th
Found my initial problem, my network interface that was being used for lustre
communication (myrinet) didn't come up after the kernel upgrade this time. I
resolved that, rebuilt everything from scratch, and have have an upgraded
lustre 1.6.4.3 running on my MGS and OSS nodes. However, I'm gettin
10 matches
Mail list logo
