From m_mohammadi_dinani at yahoo.com  Thu Aug  2 09:40:49 2012
From: m_mohammadi_dinani at yahoo.com (mohammad mohammadi)
Date: Thu, 2 Aug 2012 02:40:49 -0700 (PDT)
Subject: [Lustre-devel] Build lustre 1.8 on centos 5.5
Message-ID: <1343900449.20361.YahooMailNeo@web125602.mail.ne1.yahoo.com>

To whom it may concerns,

I want to build Lustre 1.8 (or 2.1 if it's possible) on CentOS 5.5 with kernel version 2.6.18.194.el5
I follow the instructions provided on the wiki.
One of the patches (applied on drivers/scsi/isci/init.c) is ignored, because it can't find the file.
It also fails while running make rpm.
The instructions and outputs are:

# wget http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
# rpm -ivh ./epel-release-5-4.noarch.rpm
# yum -y groupinstall "Development Tools" # yum -y install rpm-build redhat-rpm-config unifdef gnupg quilt git
# useradd -d /build build
# su build
# cd $HOME
# git clone git://git.whamcloud.com/fs/lustre-release.git # cd lustre-release
# git checkout --track -b b1_8 origin/b1_8
# sh ./autogen.sh 
# cd $HOME
# mkdir -p kernel/rpmbuild/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
# cd kernel
# echo '%_topdir %(echo $HOME)/kernel/rpmbuild' > ~/.rpmmacros
# rpm -i http://vault.centos.org/5.5/os/SRPMS/kernel-2.6.18-194.el5.src.rpm
# rpmbuild -bp --target=`uname -m` ~/kernel/rpmbuild/SPECS/kernel-2.6.spec

# cd ~/kernel/rpmbuild/BUILD/kernel-2.6.18/linux-2.6.18.x86_64
# cp ~/lustre-release/lustre/kernel_patches/kernel_configs/kernel-2.6.18-2.6-rhel5-x86_64.config .config
# ln -s ~/lustre-release/lustre/kernel_patches/series/2.6-rhel5.series series
# ln -s ~/lustre-release/lustre/kernel_patches/patches patches
# quilt push -avApplying patch patches/blkdev_tunables-2.6-rhel5.patch
patching file include/linux/blkdev.h
Hunk #1 succeeded at 783 (offset -5 lines).
patching file include/scsi/scsi_host.h can't find file to patch at input line 36 Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: linux-2.6.18-164.11.1/drivers/scsi/isci/init.c
|===================================================================
|--- linux-2.6.18-164.11.1/drivers/scsi/isci/init.c
|+++ linux-2.6.18-164.11.1/drivers/scsi/isci/init.c
--------------------------
No file to patch.  Skipping patch. 1 out of 1 hunk ignored 


# cd /build/kernel/rpmbuild/BUILD/kernel-2.6.18/linux-2.6.18.x86_64
# make oldconfig || make menuconfig
# make include/asm
# make include/linux/version.h
# make SUBDIRS=scripts
# make include/linux/utsrelease.h
# make rpm

fs/dcache.c: In function 'd_move_locked':
fs/dcache.c:1619: error: implicit declaration of function '__d_move'
fs/dcache.c: At top level:
fs/dcache.c:1645: error: redefinition of 'd_move_locked'
fs/dcache.c:1617: error: previous definition of 'd_move_locked' was here
make[3]: *** [fs/dcache.o] Error 1
make[2]: *** [fs] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.6263 (%build) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.6263 (%build)
make[1]: *** [rpm] Error 1
make: *** [rpm] Error 2

I would appreciated it if you could help me to solve the problem.

Thanks in advance
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel_lists.lustre.org/attachments/20120802/dcbf28ba/attachment.html>

From spitzcor at cray.com  Tue Aug  7 04:55:44 2012
From: spitzcor at cray.com (Cory Spitz)
Date: Mon, 6 Aug 2012 23:55:44 -0500
Subject: [Lustre-devel] merges to b2_<x>
Message-ID: <50209FD0.8000306@cray.com>

Hi.

We at Cray have been looking at b2_1 landings, and one thing that I 
think would be nice is if we could identify the master commit that the 
b2_1 commit is based on directly from the mod header.  Unless, of 
course, there is an easy way to derive this information via git.  I hope 
that this isn't a stupid question, but is there?  It seems to me that 
since most b2_1 commits are cherry picked that we lose that bit.  It 
seems that git cherry-pick -x might be useful here.  Is that all we need?

If there isn't an easy way for git to provide the lineage, would we be 
able to add an additional commit tag or just advertise a convention to 
follow at http://wiki.whamcloud.com/display/PUB/Commit+Comments?

Thanks,
-Cory

From surya1 at llnl.gov  Tue Aug  7 16:08:54 2012
From: surya1 at llnl.gov (Prakash Surya)
Date: Tue, 7 Aug 2012 09:08:54 -0700
Subject: [Lustre-devel] merges to b2_<x>
In-Reply-To: <50209FD0.8000306@cray.com>
References: <50209FD0.8000306@cray.com>
Message-ID: <20120807160854.GL6857@llnl.gov>

Looking at the man page for git-cherry-pick, I'm not sure the "-x"
option would entirely work:

    "Append the note only for cherry picks without conflicts."

How often do the backported patches apply without conflicts? With the
amount of code change taking place, my guess is conflicts are normal
operation. A developer enforced convention detailing the commit
backported and perhaps what and why changes were necessary to apply
cleanly would suffice. So long as it doesn't clutter the commit message.

Another way to do this would be to use the same Change-Id field for the
backported patch. One could grep for the Change-Id in the commit logs
relatively easily, although I'm not sure how the review system would
handle this.

-- 
Cheers, Prakash

On Mon, Aug 06, 2012 at 09:55:44PM -0700, Cory Spitz wrote:
> Hi.
> 
> We at Cray have been looking at b2_1 landings, and one thing that I 
> think would be nice is if we could identify the master commit that the 
> b2_1 commit is based on directly from the mod header.  Unless, of 
> course, there is an easy way to derive this information via git.  I hope 
> that this isn't a stupid question, but is there?  It seems to me that 
> since most b2_1 commits are cherry picked that we lose that bit.  It 
> seems that git cherry-pick -x might be useful here.  Is that all we need?
> 
> If there isn't an easy way for git to provide the lineage, would we be 
> able to add an additional commit tag or just advertise a convention to 
> follow at http://wiki.whamcloud.com/display/PUB/Commit+Comments?
> 
> Thanks,
> -Cory
> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel

From adilger at whamcloud.com  Tue Aug  7 19:45:43 2012
From: adilger at whamcloud.com (Andreas Dilger)
Date: Tue, 7 Aug 2012 13:45:43 -0600
Subject: [Lustre-devel] [lustre-devel]  merges to b2_<x>
In-Reply-To: <20120807160854.GL6857@llnl.gov>
References: <50209FD0.8000306@cray.com> <20120807160854.GL6857@llnl.gov>
Message-ID: <E6EEE694-681F-4414-A41C-AD634C17800B@whamcloud.com>

On 2012-08-07, at 10:08 AM, Prakash Surya wrote:
> Looking at the man page for git-cherry-pick, I'm not sure the "-x"
> option would entirely work:
> 
>    "Append the note only for cherry picks without conflicts."
> 
> How often do the backported patches apply without conflicts? With the
> amount of code change taking place, my guess is conflicts are normal
> operation. A developer enforced convention detailing the commit
> backported and perhaps what and why changes were necessary to apply
> cleanly would suffice. So long as it doesn't clutter the commit message.

I agree that having some standardized way of linking two commits on different branches would be quite useful.  In some cases, Oleg is able to do a cherry-pick of the original patch from master to b2_1, but in other cases there are separate patches submitted to Gerrit (with separate Change-Ids) for each branch in order to simplify patch testing.

> Another way to do this would be to use the same Change-Id field for the
> backported patch. One could grep for the Change-Id in the commit logs
> relatively easily, although I'm not sure how the review system would
> handle this.

Using the same Change-Id on two different branches causes heartburn for Gerrit, unfortunately.  This has happened by accident a few times, when a series of patches were merged into a development branch and then accidentally pushed to Gerrit.  It thinks that these previously-landed patches are all "in progress" again, and causes every later patch on the original branch (usually master) to claim them as open dependencies.

I'd rather have standardized keyword(s) that contain the original Git commit from master, and possibly the original Change-Id value.  There is already a "{name}-bug-id:" tag in use for tracking a patch from different upstream ticketing systems (e.g. Xyratex, Oracle, Whamcloud).

Cheers, Andreas

> On Mon, Aug 06, 2012 at 09:55:44PM -0700, Cory Spitz wrote:
>> Hi.
>> 
>> We at Cray have been looking at b2_1 landings, and one thing that I 
>> think would be nice is if we could identify the master commit that the 
>> b2_1 commit is based on directly from the mod header.  Unless, of 
>> course, there is an easy way to derive this information via git.  I hope 
>> that this isn't a stupid question, but is there?  It seems to me that 
>> since most b2_1 commits are cherry picked that we lose that bit.  It 
>> seems that git cherry-pick -x might be useful here.  Is that all we need?
>> 
>> If there isn't an easy way for git to provide the lineage, would we be 
>> able to add an additional commit tag or just advertise a convention to 
>> follow at http://wiki.whamcloud.com/display/PUB/Commit+Comments?
>> 
>> Thanks,
>> -Cory
>> _______________________________________________
>> Lustre-devel mailing list
>> Lustre-devel at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-devel
> _______________________________________________
> lustre-devel mailing list
> lustre-devel at lists.opensfs.org
> http://lists.opensfs.org/listinfo.cgi/lustre-devel-opensfs.org


Cheers, Andreas
--
Andreas Dilger                       Whamcloud, Inc.
Principal Lustre Engineer            http://www.whamcloud.com/




From bruce_korb at xyratex.com  Tue Aug  7 21:00:57 2012
From: bruce_korb at xyratex.com (Bruce Korb)
Date: Tue, 07 Aug 2012 14:00:57 -0700
Subject: [Lustre-devel] [lustre-devel]  merges to b2_<x>
In-Reply-To: <E6EEE694-681F-4414-A41C-AD634C17800B@whamcloud.com>
Message-ID: <CC46CE84.5D03%bruce_korb@xyratex.com>

Hi Andreas,

On 8/7/12 12:45 PM, Andreas Dilger wrote:
>> Another way to do this would be to use the same Change-Id field for the
>> backported patch. One could grep for the Change-Id in the commit logs
>> relatively easily, although I'm not sure how the review system would
>> handle this.
>
>Using the same Change-Id on two different branches causes heartburn for
>Gerrit, unfortunately.  This has happened by accident a few times, when a
>series of patches were merged into a development branch and then
>accidentally pushed to Gerrit.  It thinks that these previously-landed
>patches are all "in progress" again, and causes every later patch on the
>original branch (usually master) to claim them as open dependencies.

Maybe you could find some script maestro who could auto-insert this
magic tag at the same time the original Change-Id gets inserted?
Commit-Id: anyone?


From kelly.zhang at emc.com  Wed Aug 22 09:58:35 2012
From: kelly.zhang at emc.com (Zhang, Kelly)
Date: Wed, 22 Aug 2012 05:58:35 -0400
Subject: [Lustre-devel] Test failures with Lustre latest release(2.2.93)
Message-ID: <F62E2618FCA29E42AB21F281C9511BB413EE4CD9B0@MX26A.corp.emc.com>

Hello,

Do you guys meet the following two failures with Lustre latest release(2.2.93)?  Have they already been logged in Maloo?

== sanity test 200: OST pools == 15:56:58 (1345449418)
Creating new pool
lustre1oss1: Pool lustre.cea1 created
Waiting 90 secs for update
Adding targets to pool
lustre1oss1: add the named OSTs to the pool
lustre1oss1: usage pool_add <fsname>.<poolname> <ostname indexed list>
sanity test_200: @@@@@@ FAIL: lfs pool_list bad ost count 0 != 1
  Trace dump:
  = /usr/lib64/lustre/tests/test-framework.sh:3614:error_noexit()
  = /usr/lib64/lustre/tests/sanity.sh:8564:pool_add_targets()
  = /usr/lib64/lustre/tests/sanity.sh:8777:test_200()
  = /usr/lib64/lustre/tests/test-framework.sh:3869:run_one()
  = /usr/lib64/lustre/tests/test-framework.sh:3898:run_one_logged()
  = /usr/lib64/lustre/tests/test-framework.sh:3772:run_test()
  = /usr/lib64/lustre/tests/sanity.sh:8806:main()
Dumping lctl log to /tmp/test_logs/2012-08-20/154136/sanity.test_200.*.1345449428.log


== racer test 1: racer on clients: lustre1cl1 DURATION=300 == 16:47:45 (1345452465)
lustre1cl1: Reading test skip list from /usr/lib64/lustre/tests/cfg/tests-to-skip.sh
racers pids: 28251 28252

Message from syslogd at lustre1cl1 at Aug 20 04:52:46 ...
kernel:LustreError: 16793:0:(osc_lock.c:205:osc_lock_unuse()) ASSERTION( !ols->ols_hold ) failed:
Message from syslogd at lustre1cl1 at Aug 20 04:52:46 ...
kernel:LustreError: 16793:0:(osc_lock.c:205:osc_lock_unuse()) LBUG


Best Regards,
Kelly Zhang(EMC)


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel_lists.lustre.org/attachments/20120822/e7b2ef7e/attachment.html>

From keith at whamcloud.com  Wed Aug 22 22:08:33 2012
From: keith at whamcloud.com (Keith Mannthey)
Date: Wed, 22 Aug 2012 15:08:33 -0700
Subject: [Lustre-devel] [wc-discuss] Test failures with Lustre latest
	release(2.2.93)
In-Reply-To: <F62E2618FCA29E42AB21F281C9511BB413EE4CD9B0@MX26A.corp.emc.com>
References: <F62E2618FCA29E42AB21F281C9511BB413EE4CD9B0@MX26A.corp.emc.com>
Message-ID: <CABy1qO2OrSbKYdbEU2uGDG41qKEpxY=QuwQHgw-QOPKEAcVNOg@mail.gmail.com>

On Wed, Aug 22, 2012 at 2:58 AM, Zhang, Kelly <kelly.zhang at emc.com> wrote:

> Hello,****
>
> ** **
>
> Do you guys meet the following two failures with *Lustre latest
> release(2.2.93)*?  Have they already been logged in Maloo?****
>
> ** **
>
> == sanity test 200: OST pools == 15:56:58 (1345449418)****
>
> Creating new pool****
>
> lustre1oss1: Pool lustre.cea1 created****
>
> Waiting 90 secs for update****
>
> Adding targets to pool****
>
> lustre1oss1: add the named OSTs to the pool****
>
> lustre1oss1: usage pool_add <fsname>.<poolname> <ostname indexed list>****
>
> sanity test_200: @@@@@@ FAIL: lfs pool_list bad ost count 0 != 1****
>
>   Trace dump:****
>
>   = /usr/lib64/lustre/tests/test-framework.sh:3614:error_noexit()****
>
>   = /usr/lib64/lustre/tests/sanity.sh:8564:pool_add_targets()****
>
>   = /usr/lib64/lustre/tests/sanity.sh:8777:test_200()****
>
>   = /usr/lib64/lustre/tests/test-framework.sh:3869:run_one()****
>
>   = /usr/lib64/lustre/tests/test-framework.sh:3898:run_one_logged()****
>
>   = /usr/lib64/lustre/tests/test-framework.sh:3772:run_test()****
>
>   = /usr/lib64/lustre/tests/sanity.sh:8806:main()****
>
> Dumping lctl log to
> /tmp/test_logs/2012-08-20/154136/sanity.test_200.*.1345449428.log****
>
>
>
Yes I know of this first issue, it can be seen at
http://jira.whamcloud.com/browse/LU-1410.
There is a problem running sanity test 200.  We know for sure running with
1 OST only is has this problem and there is a patch to fix the test in the
LU.

It is a simple test change. Please let us know if you use the change and
still have this issue.

== racer test 1: racer on clients: lustre1cl1 DURATION=300 == 16:47:45
> (1345452465)****
>
> lustre1cl1: Reading test skip list from
> /usr/lib64/lustre/tests/cfg/tests-to-skip.sh****
>
> racers pids: 28251 28252****
>
> ** **
>
> Message from syslogd at lustre1cl1 at Aug 20 04:52:46 ...****
>
> kernel:LustreError: 16793:0:(osc_lock.c:205:osc_lock_unuse()) ASSERTION(
> !ols->ols_hold ) failed:****
>
> Message from syslogd at lustre1cl1 at Aug 20 04:52:46 ...****
>
> kernel:LustreError: 16793:0:(osc_lock.c:205:osc_lock_unuse()) LBUG
>


This 2nd issue may be related to
http://jira.whamcloud.com/browse/LU-1772(it is a reported timeout).

Thanks,
 Keith Mannthey
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel_lists.lustre.org/attachments/20120822/da74f1a0/attachment.html>

From kelly.zhang at emc.com  Thu Aug 23 09:53:51 2012
From: kelly.zhang at emc.com (Zhang, Kelly)
Date: Thu, 23 Aug 2012 05:53:51 -0400
Subject: [Lustre-devel] [wc-discuss] Test failures with Lustre latest
	release(2.2.93)
In-Reply-To: <CABy1qO2OrSbKYdbEU2uGDG41qKEpxY=QuwQHgw-QOPKEAcVNOg@mail.gmail.com>
References: <F62E2618FCA29E42AB21F281C9511BB413EE4CD9B0@MX26A.corp.emc.com>
	<CABy1qO2OrSbKYdbEU2uGDG41qKEpxY=QuwQHgw-QOPKEAcVNOg@mail.gmail.com>
Message-ID: <F62E2618FCA29E42AB21F281C9511BB413EE4CDAC7@MX26A.corp.emc.com>

Hi Keith,

Thank you so much for your prompt answer.  It is great they had already been recorded.

Best Regards,
Kelly

From: Keith Mannthey [mailto:keith at whamcloud.com]
Sent: 2012年8月23日 6:09
To: Zhang, Kelly
Cc: wc-discuss at whamcloud.com; lustre-devel at lists.lustre.org; Tang, Haiying; China COE FastData
Subject: Re: [wc-discuss] Test failures with Lustre latest release(2.2.93)

On Wed, Aug 22, 2012 at 2:58 AM, Zhang, Kelly <kelly.zhang at emc.com<mailto:kelly.zhang at emc.com>> wrote:
Hello,

Do you guys meet the following two failures with Lustre latest release(2.2.93)?  Have they already been logged in Maloo?

== sanity test 200: OST pools == 15:56:58 (1345449418)
Creating new pool
lustre1oss1: Pool lustre.cea1 created
Waiting 90 secs for update
Adding targets to pool
lustre1oss1: add the named OSTs to the pool
lustre1oss1: usage pool_add <fsname>.<poolname> <ostname indexed list>
sanity test_200: @@@@@@ FAIL: lfs pool_list bad ost count 0 != 1
  Trace dump:
  = /usr/lib64/lustre/tests/test-framework.sh:3614:error_noexit()
  = /usr/lib64/lustre/tests/sanity.sh:8564:pool_add_targets()
  = /usr/lib64/lustre/tests/sanity.sh:8777:test_200()
  = /usr/lib64/lustre/tests/test-framework.sh:3869:run_one()
  = /usr/lib64/lustre/tests/test-framework.sh:3898:run_one_logged()
  = /usr/lib64/lustre/tests/test-framework.sh:3772:run_test()
  = /usr/lib64/lustre/tests/sanity.sh:8806:main()
Dumping lctl log to /tmp/test_logs/2012-08-20/154136/sanity.test_200.*.1345449428.log

Yes I know of this first issue, it can be seen at http://jira.whamcloud.com/browse/LU-1410.
There is a problem running sanity test 200.  We know for sure running with 1 OST only is has this problem and there is a patch to fix the test in the LU.

It is a simple test change. Please let us know if you use the change and still have this issue.
== racer test 1: racer on clients: lustre1cl1 DURATION=300 == 16:47:45 (1345452465)
lustre1cl1: Reading test skip list from /usr/lib64/lustre/tests/cfg/tests-to-skip.sh
racers pids: 28251 28252

Message from syslogd at lustre1cl1 at Aug 20 04:52:46 ...
kernel:LustreError: 16793:0:(osc_lock.c:205:osc_lock_unuse()) ASSERTION( !ols->ols_hold ) failed:
Message from syslogd at lustre1cl1 at Aug 20 04:52:46 ...
kernel:LustreError: 16793:0:(osc_lock.c:205:osc_lock_unuse()) LBUG

This 2nd issue may be related to http://jira.whamcloud.com/browse/LU-1772 (it is a reported timeout).

Thanks,
 Keith Mannthey

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel_lists.lustre.org/attachments/20120823/dc5bedc8/attachment.html>