On Aug 08, 2008 21:50 -0400, Brian J. Murrell wrote:
> On Fri, 2008-08-08 at 18:44 -0700, SoVo Le wrote:
> > Would I have any problem running Lustre 1.6.5.1 on Kernel 2.6.5.11 ?
> > Please advise.
>
> Yes, Lustre does not yet support that kernel.
Well, Lustre supports 2.6.5 SLES9 kernels, though
On Aug 08, 2008 13:27 -0300, Balagopal Pillai wrote:
> The storage server that served Lustre had a drive
> failure on the 3ware 9650 raid6 array and it seemed to
> rebuild fine. But almost all volumes in that array seems to have
> filesystem corruption. The partitions with OS
>
On Aug 17, 2008 09:08 -0500, Troy Benjegerdes wrote:
> There seem to be a couple of assumptions here that would be worth
> examining further.
>
> My first thought is that running Lustre under something like Xen might
> be very usefull for virtualization, failover, and load balancing.
>
> If ther
On Aug 18, 2008 17:18 -0700, Klaus Steden wrote:
> Hrm. Who should I contact to find out more, then?
Nathan is working on the Changelog code, but I think the main issue
is that neither of us know what "compliant with Trusted Computing standards"
really means.
> On 8/18/08 4:44 PM, "Andreas Dilge
On Aug 18, 2008 17:30 -0500, Troy Benjegerdes wrote:
> Where's the right place to report that the debian lenny packages have a
> broken llmount.sh?
>
> It would be nice if debconf could be used to automagically configure
> lustre in the same way that the Debian openafs packages will do some of
>
Something appeared to be messed up. We rebuilt the filesystem and
now we cant reproduce the problem.
Thanks for looking into it.
I am doing some failover testing right now, see my other emails. Now
that I have the MGS seen as two hosts, failover is quite snappy for a
known failover, IE re
On Aug 07, 2008 12:06 -0400, Brock Palen wrote:
> When the MDS came up on the new server by heartbeat it went into
> recovery as expected. The MDS now has been in recovery for 1.5
> hours. I don't think this is normal.
>
> What would cause this? I know by having a client go down (the reset
On Aug 06, 2008 10:29 +0200, Karsten Weiss wrote:
> regarding the Lustre interoperability between the various 1.6.x releases
> the manual currently says this:
>
> 13.1 Lustre Interoperability
>
> For Lustre 1.6.4, the following upgrades are supported:
> [...]
> * One minor version to the next (
Ignore,
After days of banging head against the wall and trying to use
tunefs.lustre which appears to maybe suffer from the same bug. I
found the alternative that specifying --mgsnode= more than once was
valid. This mixed with the wonderful --print option to mkfs.lustre
I think I have
Hi Andreas,
Hrm. Who should I contact to find out more, then?
thanks,
Klaus
On 8/18/08 4:44 PM, "Andreas Dilger" <[EMAIL PROTECTED]>did etch on stone
tablets:
> On Aug 18, 2008 12:53 -0700, Klaus Steden wrote:
>> Will this be compliant with Trusted Computing standards? i.e. will it be
>> poss
Hi,
I never did get a reply for this. We are faced with planned
production on Monday, so we could really use some guidance.
What is the quickest work around for working around bug 15912, there
are patches now but they are for unreleased versions. We need a
solution for the current 1.6.5.1
On Aug 18, 2008 15:46 +0200, Heiko Schroeter wrote:
> from time to time we see these messages on our MDS 1.6.5.1 during
> copying data onto lustre.
>
> Is this just informational or an indicator of a broken setup ? Network load
> problems ?
>
> We checked the group rights and they look ok to us
On Aug 18, 2008 12:53 -0700, Klaus Steden wrote:
> Will this be compliant with Trusted Computing standards? i.e. will it be
> possible to use this information for auditing purposes?
I don't know enough about that to make a useful answer, sorry.
> On 8/18/08 3:43 AM, "Andreas Dilger" <[EMAIL PROT
Where's the right place to report that the debian lenny packages have a
broken llmount.sh?
It would be nice if debconf could be used to automagically configure
lustre in the same way that the Debian openafs packages will do some of
the afs cell setup work.
_
I am trying to run the Code:
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char *argv[])
{
struct if_quotactl qctl;
char szpath[FILENAME_MAX];
struct passwd *pw;
uid_t uid;
gid_t gid;
int rc;
pw = getpwuid(geteuid());
if
Hi Andreas,
Will this be compliant with Trusted Computing standards? i.e. will it be
possible to use this information for auditing purposes?
thanks,
Klaus
On 8/18/08 3:43 AM, "Andreas Dilger" <[EMAIL PROTECTED]>did etch on stone
tablets:
> On Aug 09, 2008 05:06 -0700, daledude wrote:
>> Is th
On Mon, Aug 18, 2008 at 09:21:16AM -0700, David Brown wrote:
> Lustre developers only support vanilla 2.6.22.x ish (iirc). I don't
> think they've tried pushing forward the support to newer vanilla
> kernels. I think its about time for them to push forward their support
> for newer kernels. I'm sur
Lustre developers only support vanilla 2.6.22.x ish (iirc). I don't
think they've tried pushing forward the support to newer vanilla
kernels. I think its about time for them to push forward their support
for newer kernels. I'm sure the lustre package maintainers for debian
would appreciate the effo
Hi,
we want to test this 'lustre' product. so
Is there any automated test scripts are written already and available
for test this product features and functionalities,
plz guide us.
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
htt
I was wondering what kernel works.. it looks like you are using 2.6.18,
correct?
What needs to happen to get 2.6.25 to work? I'd really like to have
lustre and PVFS coexist on the same box.
On Fri, Aug 15, 2008 at 02:33:40PM -0700, David Brown wrote:
> On Fri, Aug 15, 2008 at 9:48 AM, Robert LeBl
Hello,
from time to time we see these messages on our MDS 1.6.5.1 during copying data
onto lustre.
Is this just informational or an indicator of a broken setup ? Network load
problems ?
We checked the group rights and they look ok to us. The lustre MDS system
including clients runs with YP se
Hi,
We want to test the Lustre product, is their any automated scripts already
written to test this product.
We need information, please guide us.
Thanks,
Praveen.
___
Lustre-discuss mailing list
Lustre-discuss@lists.lustre.org
http://lists.lustre.org/m
On Aug 09, 2008 05:06 -0700, daledude wrote:
> Is there is a tool that shows what files are being accessed? Sort of
> like inotify, but not inotify? I'd like to compile file access
> statistics to try and balance the most accessed files across the OST's
> better.
There is a feature being worked o
Hello list,
does anyone has more background infos of what happened there ?
Regards
Heiko
HLRN News
-
Since Mon Aug 18, 2008 12:00 HLRN-II complex Berlin is open for users,
again.
During the maintenance it turned out that the Lustre file system holding
the users $WORK and $TMPDIR wa
On Aug 08, 2008 14:19 -0700, Herb Wartens wrote:
> We have a rudimentary tool that I developed here at LLNL that
> does what I think you want here.
> You asked for getting an OST inode from an ost object. All you have
> to do is stat the file using debugfs to get at that information.
> What I thi
On Aug 15, 2008 00:00 -0600, Chris Worley wrote:
> In adding info to bugzilla, you clarified that this is actually bug #16237.
>
> This bug is "fixed" and in Lustre 1.6.6... but 1.6.6 isn't released.
>
> Is there a work-around for the 1.6.5.1 client (short of rebooting)?
If you are up to rebuil
On Aug 05, 2008 16:56 +0200, S�bastien Buisson wrote:
> We run a cluster with Lustre 1.4.12, and we can see various Lustre
> messages in the syslog for which we did not find any explanation (and
> that are not self explanatory for us :) ).
>
> Here they are:
> - "cancel n llog-records failed"
>
27 matches
Mail list logo
