Hello,
> If you are very interested to start working on this, then you can get the
> lustre-e2fsprogs CVS module (put it in a directory called "patches" in
> the e2fsprogs tree) and then run "quilt push -a" to try and apply patches,
> fixing each one as you go.
Where is this module located? I didn
Hello Alex,
On Thursday 28 August 2008 05:20:47 Alex Lee wrote:
> Hello Folks,
>
> I have few client nodes that are getting soft lockup errors. These are
> patchless clients running Lustre 1.6.5.1 with kernel
> 2.6.18-53.1.6.el5-PAPI. More or less stock RHEL 5.1 with PAPI patch added
> on it. The
On Thursday 28 August 2008 05:41:24 Alex Lee wrote:
> Is there any documentation on how to decode the error messages? I feel
> bad keep posting on the list for every single error message I dont
> understand.
I don't think so, you have the source ;) Nathaniel Rutman posted a quite
useful bash errn
Bernd Schubert wrote:
> Hello Alex,
>
> On Thursday 28 August 2008 05:20:47 Alex Lee wrote:
>
>> Hello Folks,
>>
>> I have few client nodes that are getting soft lockup errors. These are
>> patchless clients running Lustre 1.6.5.1 with kernel
>> 2.6.18-53.1.6.el5-PAPI. More or less stock RHEL 5.
Well, I guess I was intrigued by the replication portion of HAMMER. I
suppose SNS will take care of this for us...
On Sat, Aug 23, 2008 at 10:28 AM, Troy Benjegerdes <[EMAIL PROTECTED]> wrote:
> On Sat, Aug 23, 2008 at 05:51:36PM +0400, Nikita Danilov wrote:
>> Mag Gam writes:
>> > Looks like t
for completeness, here are the logs from 172.16.4.93
Aug 27 07:49:55 clus093 kernel: LustreError: 132-0: BAD WRITE
CHECKSUM: changed on the client after we checksummed it - likely false
positive due to mmap IO (bug 11742): from [EMAIL PROTECTED] inum
24522277/1605841060 object 12021/0 extent
Hi All,
Just wondering if someone can give us some insight into the logic that
ksocklnd uses to decide which connections to make.
There's not so much in the Lustre operations manual about it, but the
impression I get from reading around is that if we have:
options lnet networks=tcp0(eth0,eth1)
In my lustre 1.6 config, I have two MSA2000 and two DL380G5 servers. The
servers sfs1 and sfs2 are the internal network Ethernet names for my two
servers. The system interconnect names, ic-sfs1 and ic-sfs2, correspond to the
servers.
I've successfully (I think) run both "lctl ping [EMAIL PROT
On Aug 27, 2008 20:57 +0300, Ender G�ler wrote:
> I'm new to lustre community and lustre software as well. I have question
> regarding to patchless lustre client installation. The OS is Redhat EL 5.1.
> I'm using voltaire gridstack v5.1.3 for infiniband software stack. I
> installed the lustre-1.6
Hi Alex,
On Thursday 28 August 2008 14:52:22 Alex Lee wrote:
> Someone found this bug for me that looks very similar.
>
> https://bugzilla.lustre.org/show_bug.cgi?id=15975
>
> Does this look anything close? I'm pretty clueless about debugging
> kernel traces.
yeah, looks like this is your issue.
Bernd Schubert wrote:
> Hi Alex,
>
> On Thursday 28 August 2008 14:52:22 Alex Lee wrote:
>
>> Someone found this bug for me that looks very similar.
>>
>> https://bugzilla.lustre.org/show_bug.cgi?id=15975
>>
>> Does this look anything close? I'm pretty clueless about debugging
>> kernel traces.
On Aug 28, 2008 12:41 +0900, Alex Lee wrote:
> Andreas Dilger wrote:
>>> Aug 23 12:27:52 lustre-oss-0-0 kernel: LustreError:
>>> 2918:0:(ldlm_lib.c:1536:target_send_reply_msg()) @@
>>> @ processing error (-19) [EMAIL PROTECTED] x52/t0 o8->@:0/0 lens
>>> 240/0 e 0 to 0 dl 1219462372
>>> ref 1 f
On Aug 28, 2008 21:49 +0800, Stuart Midgley wrote:
> for completeness, here are the logs from 172.16.4.93
>
> Aug 27 07:49:55 clus093 kernel: LustreError: 132-0: BAD WRITE
> CHECKSUM: changed on the client after we checksummed it - likely false
> positive due to mmap IO (bug 11742): from [EMA
On Aug 28, 2008 09:12 +0200, Patrick Winnertz wrote:
> > If you are very interested to start working on this, then you can get the
> > lustre-e2fsprogs CVS module (put it in a directory called "patches" in
> > the e2fsprogs tree) and then run "quilt push -a" to try and apply patches,
> > fixing ea
On Aug 28, 2008 22:11 +0800, Tim Burgess wrote:
> - all dual connected hosts are connected to both LeftSwitch and RightSwitch
> - clients network interfaces are 172.16.4.x/16 (eth0,leftswitch) and
> 172.16.5.x/16 (eth1,rightswitch)
> - OSS/MDS network interfaces are 172.16.0.x/16 (eth0,leftswitch)
Thanks for the information, greatly appreciated.
We are keeping an eye on the client causing these errors and doing a
few tests. The mmap issue is interesting. The code producing these
errors is running across the entire cluster, so I assume if it was
mmap-ing we would be seeing these sort
16 matches
Mail list logo
