Lustre discuss - Jun 2011 - Lustre v2.1 RHEL 6.1 build does not work

Hi, all

As a fan of Lustre file system, recently I got a chance to try to build
Lustre whamcloud code v2.1 branch from scratch, the following build guide
works pretty well:
http://wiki.whamcloud.com/display/PUB/Walk-thru-+Build+Lustre+2.1+on+RHEL6+from+Whamcloud+git

Everything works well until the last step, when I
run  /usr/lib64/lustre/tests/llmount.sh, it failed with the following
error:
#############################################################################################
[root at ip-10-204-59-145 tests]# /usr/lib64/lustre/tests/llmount.sh
Stopping clients: ip-10-204-59-145 /mnt/lustre (opts:)
Stopping clients: ip-10-204-59-145 /mnt/lustre2 (opts:)
Loading modules from /usr/lib64/lustre/tests/..
debug=0x33f0404
subsystem_debug=0xffb7e3ff
gss/krb5 is not supported
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong
into /etc/modprobe.d/.
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong
into /etc/modprobe.d/.
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong
into /etc/modprobe.d/.
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong
into /etc/modprobe.d/.
Formatting mgs, mds, osts
Format mds1: /tmp/lustre-mdt1
Format ost1: /tmp/lustre-ost1
Format ost2: /tmp/lustre-ost2
Checking servers environments
Checking clients ip-10-204-59-145 environments
Loading modules from /usr/lib64/lustre/tests/..
debug=0x33f0404
subsystem_debug=0xffb7e3ff
gss/krb5 is not supported
Setup mgs, mdt, osts
Starting mds1: -o loop,user_xattr,acl  /tmp/lustre-mdt1 /mnt/mds1
mount.lustre: mount /dev/loop0 at /mnt/mds1 failed: Operation not supported
#############################################################################################

Can anyone shed some light on this issue? Does this mean current Whamcloud
Lustre code base (git://git.whamcloud.com/fs/lustre-release.git) is not
ready for test drive?

Detailed system log messages is attached for your information, the test
machine''s info is also dumped as following:

[root at ip-10-204-59-145 tests]# uname -a
Linux ip-10-204-59-145 2.6.32.lustre21 #6 SMP Wed Jun 22 15:27:40 EDT 2011
x86_64 x86_64 x86_64 GNU/Linux

[root at ip-10-204-59-145 tests]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.1 (Santiago)

BTW, thanks to the Whamcloud team for contributing so much to Lustre,
without your effort Lustre is almost dead.

Regards,
-Jon.
jon.zhu at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110622/0ae048f6/attachment-0001.html
-------------- next part --------------
Jun 22 18:38:20 ip-10-204-59-145 kernel: LDISKFS-fs warning (device loop0):
ldiskfs_fill_super: extents feature not enabled on this filesystem, use tune2fs.
Jun 22 18:38:20 ip-10-204-59-145 kernel: LDISKFS-fs (loop0): mounted filesystem
with ordered data mode
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre: MGS MGS started
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre:
4784:0:(sec.c:1474:sptlrpc_import_sec_adapt()) import MGC10.204.59.145 at
tcp->MGC10.204.59.145 at tcp_0 netid 90000: select flavor null
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre:
4784:0:(sec.c:1474:sptlrpc_import_sec_adapt()) Skipped 1 previous similar
message
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre:
4802:0:(ldlm_lib.c:871:target_handle_connect()) MGS: connection from
5800f373-5d34-2e85-92cd-284aaadcff5b at 0@lo t0 exp (null) cur 1308782300 last 0
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre: MGC10.204.59.145 at tcp:
Reactivating import
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre: MGS: Regenerating
lustre-MDTffff log by user request.
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre: Setting parameter
lustre-MDT0000-mdtlov.lov.stripesize in log lustre-MDT0000
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre: Skipped 4 previous similar
messages
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre: Enabling ACL
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre: Enabling user_xattr
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre: lustre-MDT0000: new disk,
initializing
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre:
4816:0:(mdt_lproc.c:254:lprocfs_wr_identity_upcall()) lustre-MDT0000: identity
upcall set to /usr/sbin/l_getidentity
Jun 22 18:38:20 ip-10-204-59-145 kernel: SELinux: (dev lustre, type lustre) has
no xattr support
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre: Failing over lustre-MDT0000
Jun 22 18:38:20 ip-10-204-59-145 kernel: Lustre: Skipped 2 previous similar
messages
Jun 22 18:38:21 ip-10-204-59-145 kernel: Lustre:
4784:0:(quota_master.c:793:close_quota_files()) quota[0] is off already
Jun 22 18:38:21 ip-10-204-59-145 kernel: Lustre:
4784:0:(quota_master.c:793:close_quota_files()) Skipped 1 previous similar
message
Jun 22 18:38:21 ip-10-204-59-145 kernel: Lustre: mdd_obd-lustre-MDT0000:
shutting down for failover; client state will be preserved.
Jun 22 18:38:21 ip-10-204-59-145 kernel: LustreError:
4784:0:(ldlm_request.c:1169:ldlm_cli_cancel_req()) Got rc -108 from cancel RPC:
canceling anyway
Jun 22 18:38:21 ip-10-204-59-145 kernel: LustreError:
4784:0:(ldlm_request.c:1796:ldlm_cli_cancel_list()) ldlm_cli_cancel_list: -108
Jun 22 18:38:21 ip-10-204-59-145 kernel: Lustre: MGS has stopped.
Jun 22 18:38:27 ip-10-204-59-145 kernel: Lustre:
4784:0:(client.c:1775:ptlrpc_expire_one_request()) @@@ Request x1372357163745346
sent from MGC10.204.59.145 at tcp to NID 0 at lo has timed out for slow reply:
[sent 1308782301] [real_sent 1308782301] [current 1308782307] [deadline 6s]
[delay 0s]  req at ffff8801d04e8860 x1372357163745346/t0(0) o-1->MGS at
MGC10.204.59.145@tcp_0:26/25 lens 192/192 e 0 to 1 dl 1308782307 ref 2 fl
Rpc:XN/ffffffff/ffffffff rc 0/-1
Jun 22 18:38:27 ip-10-204-59-145 kernel: Lustre: server umount lustre-MDT0000
complete
Jun 22 18:39:19 ip-10-204-59-145 kernel: Lustre:
4990:0:(debug.c:323:libcfs_debug_str2mask()) You are trying to use a numerical
value for the mask - this will be deprecated in a future release.
Jun 22 18:39:19 ip-10-204-59-145 kernel: Lustre:
4990:0:(debug.c:323:libcfs_debug_str2mask()) Skipped 3 previous similar messages
Jun 22 18:39:22 ip-10-204-59-145 kernel: LDISKFS-fs warning (device loop0):
ldiskfs_fill_super: extents feature not enabled on this filesystem, use tune2fs.
Jun 22 18:39:22 ip-10-204-59-145 kernel: LDISKFS-fs (loop0): warning: maximal
mount count reached, running e2fsck is recommended
Jun 22 18:39:22 ip-10-204-59-145 kernel: LDISKFS-fs (loop0): mounted filesystem
with ordered data mode
Jun 22 18:39:23 ip-10-204-59-145 kernel: LDISKFS-fs (loop0): warning: maximal
mount count reached, running e2fsck is recommended
Jun 22 18:39:23 ip-10-204-59-145 kernel: LDISKFS-fs (loop0): mounted filesystem
with ordered data mode
Jun 22 18:39:25 ip-10-204-59-145 kernel: LDISKFS-fs (loop0): warning: maximal
mount count reached, running e2fsck is recommended
Jun 22 18:39:25 ip-10-204-59-145 kernel: LDISKFS-fs (loop0): mounted filesystem
with ordered data mode
Jun 22 18:39:26 ip-10-204-59-145 kernel: LDISKFS-fs warning (device loop0):
ldiskfs_fill_super: extents feature not enabled on this filesystem, use tune2fs.
Jun 22 18:39:26 ip-10-204-59-145 kernel: LDISKFS-fs (loop0): mounted filesystem
with ordered data mode
Jun 22 18:39:26 ip-10-204-59-145 kernel: ------------[ cut here ]------------
Jun 22 18:39:26 ip-10-204-59-145 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 22 18:39:26 ip-10-204-59-145 kernel: Modules linked in: llite_lloop(U)
obdfilter(U) ost(U) jbd lmv(U) cmm(U) osd_ldiskfs(U) mdt(U) mdd(U) mds(U)
fsfilt_ldiskfs(U) exportfs mgs(U) mgc(U) lustre(U) lov(U) osc(U) lquota(U)
mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U)
ldiskfs(U) autofs4 ipt_REJECT ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6
xt_state nf_conntrack ip6table_filter ip6_tables ipv6 microcode xen_netfront
ext4 mbcache jbd2 xen_blkfront dm_mod [last unloaded: nf_defrag_ipv4]
Jun 22 18:39:26 ip-10-204-59-145 kernel: Pid: 5477, comm: mount.lustre Tainted:
G        W  ----------------   2.6.32.lustre21 #6
Jun 22 18:39:26 ip-10-204-59-145 kernel: Call Trace:
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811a53b7>] ?
shrink_dcache_for_umount_subtree+0x187/0x340
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811a55a6>] ?
shrink_dcache_for_umount+0x36/0x60
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f4ff>] ?
generic_shutdown_super+0x1f/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0295f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0299a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0294885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 22 18:39:26 ip-10-204-59-145 kernel: ---[ end trace dc2087f789e7996c ]---
Jun 22 18:39:26 ip-10-204-59-145 kernel: ------------[ cut here ]------------
Jun 22 18:39:26 ip-10-204-59-145 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 22 18:39:26 ip-10-204-59-145 kernel: Modules linked in: llite_lloop(U)
obdfilter(U) ost(U) jbd lmv(U) cmm(U) osd_ldiskfs(U) mdt(U) mdd(U) mds(U)
fsfilt_ldiskfs(U) exportfs mgs(U) mgc(U) lustre(U) lov(U) osc(U) lquota(U)
mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U)
ldiskfs(U) autofs4 ipt_REJECT ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6
xt_state nf_conntrack ip6table_filter ip6_tables ipv6 microcode xen_netfront
ext4 mbcache jbd2 xen_blkfront dm_mod [last unloaded: nf_defrag_ipv4]
Jun 22 18:39:26 ip-10-204-59-145 kernel: Pid: 5477, comm: mount.lustre Tainted:
G        W  ----------------   2.6.32.lustre21 #6
Jun 22 18:39:26 ip-10-204-59-145 kernel: Call Trace:
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811a53b7>] ?
shrink_dcache_for_umount_subtree+0x187/0x340
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811a55a6>] ?
shrink_dcache_for_umount+0x36/0x60
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f4ff>] ?
generic_shutdown_super+0x1f/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0295f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0299a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0294885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 22 18:39:26 ip-10-204-59-145 kernel: ---[ end trace dc2087f789e7996d ]---
Jun 22 18:39:26 ip-10-204-59-145 kernel: ------------[ cut here ]------------
Jun 22 18:39:26 ip-10-204-59-145 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 22 18:39:26 ip-10-204-59-145 kernel: Modules linked in: llite_lloop(U)
obdfilter(U) ost(U) jbd lmv(U) cmm(U) osd_ldiskfs(U) mdt(U) mdd(U) mds(U)
fsfilt_ldiskfs(U) exportfs mgs(U) mgc(U) lustre(U) lov(U) osc(U) lquota(U)
mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U)
ldiskfs(U) autofs4 ipt_REJECT ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6
xt_state nf_conntrack ip6table_filter ip6_tables ipv6 microcode xen_netfront
ext4 mbcache jbd2 xen_blkfront dm_mod [last unloaded: nf_defrag_ipv4]
Jun 22 18:39:26 ip-10-204-59-145 kernel: Pid: 5477, comm: mount.lustre Tainted:
G        W  ----------------   2.6.32.lustre21 #6
Jun 22 18:39:26 ip-10-204-59-145 kernel: Call Trace:
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f52c>] ?
generic_shutdown_super+0x4c/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0295f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0299a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0294885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 22 18:39:26 ip-10-204-59-145 kernel: ---[ end trace dc2087f789e7996e ]---
Jun 22 18:39:26 ip-10-204-59-145 kernel: ------------[ cut here ]------------
Jun 22 18:39:26 ip-10-204-59-145 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 22 18:39:26 ip-10-204-59-145 kernel: Modules linked in: llite_lloop(U)
obdfilter(U) ost(U) jbd lmv(U) cmm(U) osd_ldiskfs(U) mdt(U) mdd(U) mds(U)
fsfilt_ldiskfs(U) exportfs mgs(U) mgc(U) lustre(U) lov(U) osc(U) lquota(U)
mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U)
ldiskfs(U) autofs4 ipt_REJECT ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6
xt_state nf_conntrack ip6table_filter ip6_tables ipv6 microcode xen_netfront
ext4 mbcache jbd2 xen_blkfront dm_mod [last unloaded: nf_defrag_ipv4]
Jun 22 18:39:26 ip-10-204-59-145 kernel: Pid: 5477, comm: mount.lustre Tainted:
G        W  ----------------   2.6.32.lustre21 #6
Jun 22 18:39:26 ip-10-204-59-145 kernel: Call Trace:
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f52c>] ?
generic_shutdown_super+0x4c/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0295f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0299a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0294885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 22 18:39:26 ip-10-204-59-145 kernel: ---[ end trace dc2087f789e7996f ]---
Jun 22 18:39:26 ip-10-204-59-145 kernel: ------------[ cut here ]------------
Jun 22 18:39:26 ip-10-204-59-145 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 22 18:39:26 ip-10-204-59-145 kernel: Modules linked in: llite_lloop(U)
obdfilter(U) ost(U) jbd lmv(U) cmm(U) osd_ldiskfs(U) mdt(U) mdd(U) mds(U)
fsfilt_ldiskfs(U) exportfs mgs(U) mgc(U) lustre(U) lov(U) osc(U) lquota(U)
mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U)
ldiskfs(U) autofs4 ipt_REJECT ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6
xt_state nf_conntrack ip6table_filter ip6_tables ipv6 microcode xen_netfront
ext4 mbcache jbd2 xen_blkfront dm_mod [last unloaded: nf_defrag_ipv4]
Jun 22 18:39:26 ip-10-204-59-145 kernel: Pid: 5477, comm: mount.lustre Tainted:
G        W  ----------------   2.6.32.lustre21 #6
Jun 22 18:39:26 ip-10-204-59-145 kernel: Call Trace:
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f52c>] ?
generic_shutdown_super+0x4c/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0295f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0299a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0294885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 22 18:39:26 ip-10-204-59-145 kernel: ---[ end trace dc2087f789e79970 ]---
Jun 22 18:39:26 ip-10-204-59-145 kernel: ------------[ cut here ]------------
Jun 22 18:39:26 ip-10-204-59-145 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 22 18:39:26 ip-10-204-59-145 kernel: Modules linked in: llite_lloop(U)
obdfilter(U) ost(U) jbd lmv(U) cmm(U) osd_ldiskfs(U) mdt(U) mdd(U) mds(U)
fsfilt_ldiskfs(U) exportfs mgs(U) mgc(U) lustre(U) lov(U) osc(U) lquota(U)
mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U)
ldiskfs(U) autofs4 ipt_REJECT ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6
xt_state nf_conntrack ip6table_filter ip6_tables ipv6 microcode xen_netfront
ext4 mbcache jbd2 xen_blkfront dm_mod [last unloaded: nf_defrag_ipv4]
Jun 22 18:39:26 ip-10-204-59-145 kernel: Pid: 5477, comm: mount.lustre Tainted:
G        W  ----------------   2.6.32.lustre21 #6
Jun 22 18:39:26 ip-10-204-59-145 kernel: Call Trace:
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f52c>] ?
generic_shutdown_super+0x4c/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0295f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0299a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0294885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 22 18:39:26 ip-10-204-59-145 kernel: ---[ end trace dc2087f789e79971 ]---
Jun 22 18:39:26 ip-10-204-59-145 kernel: ------------[ cut here ]------------
Jun 22 18:39:26 ip-10-204-59-145 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 22 18:39:26 ip-10-204-59-145 kernel: Modules linked in: llite_lloop(U)
obdfilter(U) ost(U) jbd lmv(U) cmm(U) osd_ldiskfs(U) mdt(U) mdd(U) mds(U)
fsfilt_ldiskfs(U) exportfs mgs(U) mgc(U) lustre(U) lov(U) osc(U) lquota(U)
mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U)
ldiskfs(U) autofs4 ipt_REJECT ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6
xt_state nf_conntrack ip6table_filter ip6_tables ipv6 microcode xen_netfront
ext4 mbcache jbd2 xen_blkfront dm_mod [last unloaded: nf_defrag_ipv4]
Jun 22 18:39:26 ip-10-204-59-145 kernel: Pid: 5477, comm: mount.lustre Tainted:
G        W  ----------------   2.6.32.lustre21 #6
Jun 22 18:39:26 ip-10-204-59-145 kernel: Call Trace:
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f52c>] ?
generic_shutdown_super+0x4c/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0295f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0299a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0294885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 22 18:39:26 ip-10-204-59-145 kernel: ---[ end trace dc2087f789e79972 ]---
Jun 22 18:39:26 ip-10-204-59-145 kernel: ------------[ cut here ]------------
Jun 22 18:39:26 ip-10-204-59-145 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 22 18:39:26 ip-10-204-59-145 kernel: Modules linked in: llite_lloop(U)
obdfilter(U) ost(U) jbd lmv(U) cmm(U) osd_ldiskfs(U) mdt(U) mdd(U) mds(U)
fsfilt_ldiskfs(U) exportfs mgs(U) mgc(U) lustre(U) lov(U) osc(U) lquota(U)
mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U)
ldiskfs(U) autofs4 ipt_REJECT ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6
xt_state nf_conntrack ip6table_filter ip6_tables ipv6 microcode xen_netfront
ext4 mbcache jbd2 xen_blkfront dm_mod [last unloaded: nf_defrag_ipv4]
Jun 22 18:39:26 ip-10-204-59-145 kernel: Pid: 5477, comm: mount.lustre Tainted:
G        W  ----------------   2.6.32.lustre21 #6
Jun 22 18:39:26 ip-10-204-59-145 kernel: Call Trace:
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f52c>] ?
generic_shutdown_super+0x4c/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0295f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0299a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0294885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 22 18:39:26 ip-10-204-59-145 kernel: ---[ end trace dc2087f789e79973 ]---
Jun 22 18:39:26 ip-10-204-59-145 kernel: ------------[ cut here ]------------
Jun 22 18:39:26 ip-10-204-59-145 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 22 18:39:26 ip-10-204-59-145 kernel: Modules linked in: llite_lloop(U)
obdfilter(U) ost(U) jbd lmv(U) cmm(U) osd_ldiskfs(U) mdt(U) mdd(U) mds(U)
fsfilt_ldiskfs(U) exportfs mgs(U) mgc(U) lustre(U) lov(U) osc(U) lquota(U)
mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U)
ldiskfs(U) autofs4 ipt_REJECT ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6
xt_state nf_conntrack ip6table_filter ip6_tables ipv6 microcode xen_netfront
ext4 mbcache jbd2 xen_blkfront dm_mod [last unloaded: nf_defrag_ipv4]
Jun 22 18:39:26 ip-10-204-59-145 kernel: Pid: 5477, comm: mount.lustre Tainted:
G        W  ----------------   2.6.32.lustre21 #6
Jun 22 18:39:26 ip-10-204-59-145 kernel: Call Trace:
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f548>] ?
generic_shutdown_super+0x68/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0295f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0299a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa02a2d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffffa0294885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 22 18:39:26 ip-10-204-59-145 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 22 18:39:26 ip-10-204-59-145 kernel: ---[ end trace dc2087f789e79974 ]---
Jun 22 18:39:26 ip-10-204-59-145 kernel: LDISKFS-fs warning (device loop0):
ldiskfs_fill_super: extents feature not enabled on this filesystem, use tune2fs.
Jun 22 18:39:26 ip-10-204-59-145 kernel: LDISKFS-fs (loop0): mounted filesystem
with ordered data mode
Jun 22 18:39:26 ip-10-204-59-145 kernel: Lustre: MGS MGS started
Jun 22 18:39:26 ip-10-204-59-145 kernel: Lustre:
5477:0:(sec.c:1474:sptlrpc_import_sec_adapt()) import MGC10.204.59.145 at
tcp->MGC10.204.59.145 at tcp_0 netid 90000: select flavor null
Jun 22 18:39:26 ip-10-204-59-145 kernel: Lustre:
5477:0:(sec.c:1474:sptlrpc_import_sec_adapt()) Skipped 1 previous similar
message
Jun 22 18:39:26 ip-10-204-59-145 kernel: Lustre:
5497:0:(ldlm_lib.c:871:target_handle_connect()) MGS: connection from
86a8e552-468c-4021-3a14-dbec912bc3c5 at 0@lo t0 exp (null) cur 1308782366 last 0
Jun 22 18:39:26 ip-10-204-59-145 kernel: Lustre: MGC10.204.59.145 at tcp:
Reactivating import
Jun 22 18:39:26 ip-10-204-59-145 kernel: Lustre: MGS: Regenerating
lustre-MDTffff log by user request.
Jun 22 18:39:26 ip-10-204-59-145 kernel: Lustre: Setting parameter
lustre-MDT0000-mdtlov.lov.stripesize in log lustre-MDT0000
Jun 22 18:39:26 ip-10-204-59-145 kernel: Lustre: Skipped 4 previous similar
messages

Jon

It seems that the instructions (written at the end of May) have grown 
stale since the recent realignment on RHEL6.1. We''ll get the 
instructions updated.

Peter

On 11-06-22 6:03 PM, Jon Zhu wrote:
> Hi, all
>
> As a fan of Lustre file system, recently I got a chance to try to 
> build Lustre whamcloud code v2.1 branch from scratch, the following 
> build guide works pretty well:
>
http://wiki.whamcloud.com/display/PUB/Walk-thru-+Build+Lustre+2.1+on+RHEL6+from+Whamcloud+git
>
> Everything works well until the last step, when I 
> run  /usr/lib64/lustre/tests/llmount.sh, it failed with the following 
> error:
>
#############################################################################################
> [root at ip-10-204-59-145 tests]# /usr/lib64/lustre/tests/llmount.sh
> Stopping clients: ip-10-204-59-145 /mnt/lustre (opts:)
> Stopping clients: ip-10-204-59-145 /mnt/lustre2 (opts:)
> Loading modules from /usr/lib64/lustre/tests/..
> debug=0x33f0404
> subsystem_debug=0xffb7e3ff
> gss/krb5 is not supported
> WARNING: Deprecated config file /etc/modprobe.conf, all config files 
> belong into /etc/modprobe.d/.
> WARNING: Deprecated config file /etc/modprobe.conf, all config files 
> belong into /etc/modprobe.d/.
> WARNING: Deprecated config file /etc/modprobe.conf, all config files 
> belong into /etc/modprobe.d/.
> WARNING: Deprecated config file /etc/modprobe.conf, all config files 
> belong into /etc/modprobe.d/.
> Formatting mgs, mds, osts
> Format mds1: /tmp/lustre-mdt1
> Format ost1: /tmp/lustre-ost1
> Format ost2: /tmp/lustre-ost2
> Checking servers environments
> Checking clients ip-10-204-59-145 environments
> Loading modules from /usr/lib64/lustre/tests/..
> debug=0x33f0404
> subsystem_debug=0xffb7e3ff
> gss/krb5 is not supported
> Setup mgs, mdt, osts
> Starting mds1: -o loop,user_xattr,acl  /tmp/lustre-mdt1 /mnt/mds1
> mount.lustre: mount /dev/loop0 at /mnt/mds1 failed: Operation not 
> supported
>
#############################################################################################
>
> Can anyone shed some light on this issue? Does this mean current 
> Whamcloud Lustre code base 
> (git://git.whamcloud.com/fs/lustre-release.git 
> <http://git.whamcloud.com/fs/lustre-release.git>) is not ready for 
> test drive?
>
> Detailed system log messages is attached for your information, the 
> test machine''s info is also dumped as following:
>
> [root at ip-10-204-59-145 tests]# uname -a
> Linux ip-10-204-59-145 2.6.32.lustre21 #6 SMP Wed Jun 22 15:27:40 EDT 
> 2011 x86_64 x86_64 x86_64 GNU/Linux
>
> [root at ip-10-204-59-145 tests]# cat /etc/redhat-release
> Red Hat Enterprise Linux Server release 6.1 (Santiago)
>
> BTW, thanks to the Whamcloud team for contributing so much to Lustre, 
> without your effort Lustre is almost dead.
>
> Regards,
> -Jon.
> jon.zhu at gmail.com <mailto:jon.zhu at gmail.com>
>
>
>
>
>
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
-- 
Peter Jones
Whamcloud, Inc.
www.whamcloud.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110622/03250e41/attachment.html

Thanks, Peter.
The procedure has a step to create initrd:

# /sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod
--install 2.6.32lustre21


It doesn''t work so I used this command instead:
mkinitrd /boot/initramfs-2.6.32.lustre21.img 2.6.32.lustre21

Looking forward to get the new procedure soon.

Regards,
-Jon.

On Thu, Jun 23, 2011 at 1:02 AM, Peter Jones <pjones at whamcloud.com>
wrote:
> **
> Jon
>
> It seems that the instructions (written at the end of May) have grown stale
> since the recent realignment on RHEL6.1. We''ll get the
instructions updated.
>
> Peter
>
>
> On 11-06-22 6:03 PM, Jon Zhu wrote:
>
> Hi, all
>
>  As a fan of Lustre file system, recently I got a chance to try to build
> Lustre whamcloud code v2.1 branch from scratch, the following build guide
> works pretty well:
>
>
http://wiki.whamcloud.com/display/PUB/Walk-thru-+Build+Lustre+2.1+on+RHEL6+from+Whamcloud+git
>
>  Everything works well until the last step, when I
> run  /usr/lib64/lustre/tests/llmount.sh, it failed with the following
> error:
>
>
#############################################################################################
> [root at ip-10-204-59-145 tests]# /usr/lib64/lustre/tests/llmount.sh
> Stopping clients: ip-10-204-59-145 /mnt/lustre (opts:)
> Stopping clients: ip-10-204-59-145 /mnt/lustre2 (opts:)
> Loading modules from /usr/lib64/lustre/tests/..
> debug=0x33f0404
> subsystem_debug=0xffb7e3ff
> gss/krb5 is not supported
> WARNING: Deprecated config file /etc/modprobe.conf, all config files belong
> into /etc/modprobe.d/.
> WARNING: Deprecated config file /etc/modprobe.conf, all config files belong
> into /etc/modprobe.d/.
> WARNING: Deprecated config file /etc/modprobe.conf, all config files belong
> into /etc/modprobe.d/.
> WARNING: Deprecated config file /etc/modprobe.conf, all config files belong
> into /etc/modprobe.d/.
>  Formatting mgs, mds, osts
> Format mds1: /tmp/lustre-mdt1
> Format ost1: /tmp/lustre-ost1
> Format ost2: /tmp/lustre-ost2
> Checking servers environments
> Checking clients ip-10-204-59-145 environments
> Loading modules from /usr/lib64/lustre/tests/..
> debug=0x33f0404
> subsystem_debug=0xffb7e3ff
> gss/krb5 is not supported
> Setup mgs, mdt, osts
> Starting mds1: -o loop,user_xattr,acl  /tmp/lustre-mdt1 /mnt/mds1
> mount.lustre: mount /dev/loop0 at /mnt/mds1 failed: Operation not supported
>
>
#############################################################################################
>
>  Can anyone shed some light on this issue? Does this mean current
> Whamcloud Lustre code base (git://git.whamcloud.com/fs/lustre-release.git)
> is not ready for test drive?
>
>  Detailed system log messages is attached for your information, the test
> machine''s info is also dumped as following:
>
>  [root at ip-10-204-59-145 tests]# uname -a
>  Linux ip-10-204-59-145 2.6.32.lustre21 #6 SMP Wed Jun 22 15:27:40 EDT 2011
> x86_64 x86_64 x86_64 GNU/Linux
>
>  [root at ip-10-204-59-145 tests]# cat /etc/redhat-release
> Red Hat Enterprise Linux Server release 6.1 (Santiago)
>
>  BTW, thanks to the Whamcloud team for contributing so much to Lustre,
> without your effort Lustre is almost dead.
>
>  Regards,
> -Jon.
> jon.zhu at gmail.com
>
>
>
>
>
>
> _______________________________________________
> Lustre-discuss mailing listLustre-discuss at
lists.lustre.orghttp://lists.lustre.org/mailman/listinfo/lustre-discuss
>
>
> --
> Peter Jones
> Whamcloud, Inc.www.whamcloud.com
>
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110623/2f1e1536/attachment.html

Hi Jon,

Can you provide the lustre-release git checkout you used - from your
attached lustre2.1-rhel61-error.txt it looks like the issue may be
related to kernel/lustre versions and I will try to reproduce you work
exactly.

I''m going to refresh the walk through to add in RHEL 6.1 - and I
appreciate your feedback and mkinitrd comments.

Cheers,
Richard

On Thu, Jun 23, 2011 at 7:26 AM, Jon Zhu <jon.zhu at gmail.com>
wrote:
> Thanks, Peter.
> The procedure has a step to create initrd:
>
> # /sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod
> --install 2.6.32lustre21
>
> It doesn''t work so I used this command instead:
> mkinitrd /boot/initramfs-2.6.32.lustre21.img 2.6.32.lustre21
>
> Looking forward to get the new procedure soon.
> Regards,
> -Jon.
> On Thu, Jun 23, 2011 at 1:02 AM, Peter Jones <pjones at
whamcloud.com> wrote:
>>
>> Jon
>>
>> It seems that the instructions (written at the end of May) have grown
>> stale since the recent realignment on RHEL6.1. We''ll get the
instructions
>> updated.
>>
>> Peter
>>
>> On 11-06-22 6:03 PM, Jon Zhu wrote:
>>
>> Hi, all
>> As a fan of Lustre file system, recently I got a chance to try to build
>> Lustre whamcloud code v2.1 branch from scratch, the following build
guide
>> works pretty well:
>>
>>
http://wiki.whamcloud.com/display/PUB/Walk-thru-+Build+Lustre+2.1+on+RHEL6+from+Whamcloud+git
>> Everything works well until the last step, when I
>> run??/usr/lib64/lustre/tests/llmount.sh, it failed with the following
>> error:
>>
>>
#############################################################################################
>> [root at ip-10-204-59-145 tests]# /usr/lib64/lustre/tests/llmount.sh
>> Stopping clients: ip-10-204-59-145 /mnt/lustre (opts:)
>> Stopping clients: ip-10-204-59-145 /mnt/lustre2 (opts:)
>> Loading modules from /usr/lib64/lustre/tests/..
>> debug=0x33f0404
>> subsystem_debug=0xffb7e3ff
>> gss/krb5 is not supported
>> WARNING: Deprecated config file /etc/modprobe.conf, all config files
>> belong into /etc/modprobe.d/.
>> WARNING: Deprecated config file /etc/modprobe.conf, all config files
>> belong into /etc/modprobe.d/.
>> WARNING: Deprecated config file /etc/modprobe.conf, all config files
>> belong into /etc/modprobe.d/.
>> WARNING: Deprecated config file /etc/modprobe.conf, all config files
>> belong into /etc/modprobe.d/.
>> Formatting mgs, mds, osts
>> Format mds1: /tmp/lustre-mdt1
>> Format ost1: /tmp/lustre-ost1
>> Format ost2: /tmp/lustre-ost2
>> Checking servers environments
>> Checking clients ip-10-204-59-145 environments
>> Loading modules from /usr/lib64/lustre/tests/..
>> debug=0x33f0404
>> subsystem_debug=0xffb7e3ff
>> gss/krb5 is not supported
>> Setup mgs, mdt, osts
>> Starting mds1: -o loop,user_xattr,acl ?/tmp/lustre-mdt1 /mnt/mds1
>> mount.lustre: mount /dev/loop0 at /mnt/mds1 failed: Operation not
>> supported
>>
>>
#############################################################################################
>> Can anyone shed some light on this issue? Does this mean current
Whamcloud
>> Lustre code base (git://git.whamcloud.com/fs/lustre-release.git) is not
>> ready for test drive?
>> Detailed system log messages is attached for your information, the test
>> machine''s info is also dumped as following:
>> [root at ip-10-204-59-145 tests]# uname -a
>> Linux ip-10-204-59-145 2.6.32.lustre21 #6 SMP Wed Jun 22 15:27:40 EDT
2011
>> x86_64 x86_64 x86_64 GNU/Linux
>> [root at ip-10-204-59-145 tests]# cat /etc/redhat-release
>> Red Hat Enterprise Linux Server release 6.1 (Santiago)
>> BTW, thanks to the Whamcloud team for contributing so much to Lustre,
>> without your effort Lustre is almost dead.
>> Regards,
>> -Jon.
>> jon.zhu at gmail.com
>>
>>
>>
>>
>>
>> _______________________________________________
>> Lustre-discuss mailing list
>> Lustre-discuss at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>>
>> --
>> Peter Jones
>> Whamcloud, Inc.
>> www.whamcloud.com
>>
>> _______________________________________________
>> Lustre-discuss mailing list
>> Lustre-discuss at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>>
>
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
>


-- 
Richard.Henwood at whamcloud.com
Whamcloud Inc.
tel: +1 512 410 9612

Hi, Richard

I just ran the following command according to the Wiki guide at
approximately 11:00AM EST yesterday.

git clone git://git.whamcloud.com/fs/lustre-release.git


Thanks for the quick reply, and let me know if you need any other
information.

Regards,
-Jon.

On Thu, Jun 23, 2011 at 10:36 AM, Richard Henwood <rhenwood at
whamcloud.com>wrote:
> Hi Jon,
>
> Can you provide the lustre-release git checkout you used - from your
> attached lustre2.1-rhel61-error.txt it looks like the issue may be
> related to kernel/lustre versions and I will try to reproduce you work
> exactly.
>
> I''m going to refresh the walk through to add in RHEL 6.1 - and I
> appreciate your feedback and mkinitrd comments.
>
> Cheers,
> Richard
>
> On Thu, Jun 23, 2011 at 7:26 AM, Jon Zhu <jon.zhu at gmail.com>
wrote:
> > Thanks, Peter.
> > The procedure has a step to create initrd:
> >
> > # /sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod
> > --install 2.6.32lustre21
> >
> > It doesn''t work so I used this command instead:
> > mkinitrd /boot/initramfs-2.6.32.lustre21.img 2.6.32.lustre21
> >
> > Looking forward to get the new procedure soon.
> > Regards,
> > -Jon.
> > On Thu, Jun 23, 2011 at 1:02 AM, Peter Jones <pjones at
whamcloud.com>
> wrote:
> >>
> >> Jon
> >>
> >> It seems that the instructions (written at the end of May) have
grown
> >> stale since the recent realignment on RHEL6.1. We''ll get
the
> instructions
> >> updated.
> >>
> >> Peter
> >>
> >> On 11-06-22 6:03 PM, Jon Zhu wrote:
> >>
> >> Hi, all
> >> As a fan of Lustre file system, recently I got a chance to try to
build
> >> Lustre whamcloud code v2.1 branch from scratch, the following
build
> guide
> >> works pretty well:
> >>
> >>
>
http://wiki.whamcloud.com/display/PUB/Walk-thru-+Build+Lustre+2.1+on+RHEL6+from+Whamcloud+git
> >> Everything works well until the last step, when I
> >> run  /usr/lib64/lustre/tests/llmount.sh, it failed with the
following
> >> error:
> >>
> >>
>
#############################################################################################
> >> [root at ip-10-204-59-145 tests]#
/usr/lib64/lustre/tests/llmount.sh
> >> Stopping clients: ip-10-204-59-145 /mnt/lustre (opts:)
> >> Stopping clients: ip-10-204-59-145 /mnt/lustre2 (opts:)
> >> Loading modules from /usr/lib64/lustre/tests/..
> >> debug=0x33f0404
> >> subsystem_debug=0xffb7e3ff
> >> gss/krb5 is not supported
> >> WARNING: Deprecated config file /etc/modprobe.conf, all config
files
> >> belong into /etc/modprobe.d/.
> >> WARNING: Deprecated config file /etc/modprobe.conf, all config
files
> >> belong into /etc/modprobe.d/.
> >> WARNING: Deprecated config file /etc/modprobe.conf, all config
files
> >> belong into /etc/modprobe.d/.
> >> WARNING: Deprecated config file /etc/modprobe.conf, all config
files
> >> belong into /etc/modprobe.d/.
> >> Formatting mgs, mds, osts
> >> Format mds1: /tmp/lustre-mdt1
> >> Format ost1: /tmp/lustre-ost1
> >> Format ost2: /tmp/lustre-ost2
> >> Checking servers environments
> >> Checking clients ip-10-204-59-145 environments
> >> Loading modules from /usr/lib64/lustre/tests/..
> >> debug=0x33f0404
> >> subsystem_debug=0xffb7e3ff
> >> gss/krb5 is not supported
> >> Setup mgs, mdt, osts
> >> Starting mds1: -o loop,user_xattr,acl  /tmp/lustre-mdt1 /mnt/mds1
> >> mount.lustre: mount /dev/loop0 at /mnt/mds1 failed: Operation not
> >> supported
> >>
> >>
>
#############################################################################################
> >> Can anyone shed some light on this issue? Does this mean current
> Whamcloud
> >> Lustre code base (git://git.whamcloud.com/fs/lustre-release.git)
is not
> >> ready for test drive?
> >> Detailed system log messages is attached for your information, the
test
> >> machine''s info is also dumped as following:
> >> [root at ip-10-204-59-145 tests]# uname -a
> >> Linux ip-10-204-59-145 2.6.32.lustre21 #6 SMP Wed Jun 22 15:27:40
EDT
> 2011
> >> x86_64 x86_64 x86_64 GNU/Linux
> >> [root at ip-10-204-59-145 tests]# cat /etc/redhat-release
> >> Red Hat Enterprise Linux Server release 6.1 (Santiago)
> >> BTW, thanks to the Whamcloud team for contributing so much to
Lustre,
> >> without your effort Lustre is almost dead.
> >> Regards,
> >> -Jon.
> >> jon.zhu at gmail.com
> >>
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> Lustre-discuss mailing list
> >> Lustre-discuss at lists.lustre.org
> >> http://lists.lustre.org/mailman/listinfo/lustre-discuss
> >>
> >> --
> >> Peter Jones
> >> Whamcloud, Inc.
> >> www.whamcloud.com
> >>
> >> _______________________________________________
> >> Lustre-discuss mailing list
> >> Lustre-discuss at lists.lustre.org
> >> http://lists.lustre.org/mailman/listinfo/lustre-discuss
> >>
> >
> >
> > _______________________________________________
> > Lustre-discuss mailing list
> > Lustre-discuss at lists.lustre.org
> > http://lists.lustre.org/mailman/listinfo/lustre-discuss
> >
> >
>
>
>
> --
> Richard.Henwood at whamcloud.com
> Whamcloud Inc.
> tel: +1 512 410 9612
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110623/29a77b92/attachment.html

The problem disappeared after I disable SELinux with the following steps, it
works very well. Maybe we need to mention disabling SELinux and probably
creating extra firewall policy to enable Lustre inter-node communication in
the setup guide.

Edit /etc/selinux/config and make sure the following line is
*SELINUX=disabled*
*Reboot host. (this is a must, the test environment must have SELINUX
disabled, *echo 0 >/selinux/enforce won''t work)
*
*
Hope this helps, and thanks for all of your help.

Regards,
-Jon.



On Thu, Jun 23, 2011 at 8:26 AM, Jon Zhu <jon.zhu at gmail.com> wrote:
> Thanks, Peter.
> The procedure has a step to create initrd:
>
> # /sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod
--install 2.6.32lustre21
>
>
> It doesn''t work so I used this command instead:
> mkinitrd /boot/initramfs-2.6.32.lustre21.img 2.6.32.lustre21
>
> Looking forward to get the new procedure soon.
>
> Regards,
> -Jon.
>
> On Thu, Jun 23, 2011 at 1:02 AM, Peter Jones <pjones at
whamcloud.com> wrote:
>
>> **
>> Jon
>>
>> It seems that the instructions (written at the end of May) have grown
>> stale since the recent realignment on RHEL6.1. We''ll get the
instructions
>> updated.
>>
>> Peter
>>
>>
>> On 11-06-22 6:03 PM, Jon Zhu wrote:
>>
>> Hi, all
>>
>>  As a fan of Lustre file system, recently I got a chance to try to
build
>> Lustre whamcloud code v2.1 branch from scratch, the following build
guide
>> works pretty well:
>>
>>
http://wiki.whamcloud.com/display/PUB/Walk-thru-+Build+Lustre+2.1+on+RHEL6+from+Whamcloud+git
>>
>>  Everything works well until the last step, when I
>> run  /usr/lib64/lustre/tests/llmount.sh, it failed with the following
>> error:
>>
>>
#############################################################################################
>> [root at ip-10-204-59-145 tests]# /usr/lib64/lustre/tests/llmount.sh
>> Stopping clients: ip-10-204-59-145 /mnt/lustre (opts:)
>> Stopping clients: ip-10-204-59-145 /mnt/lustre2 (opts:)
>> Loading modules from /usr/lib64/lustre/tests/..
>> debug=0x33f0404
>> subsystem_debug=0xffb7e3ff
>> gss/krb5 is not supported
>> WARNING: Deprecated config file /etc/modprobe.conf, all config files
>> belong into /etc/modprobe.d/.
>> WARNING: Deprecated config file /etc/modprobe.conf, all config files
>> belong into /etc/modprobe.d/.
>> WARNING: Deprecated config file /etc/modprobe.conf, all config files
>> belong into /etc/modprobe.d/.
>> WARNING: Deprecated config file /etc/modprobe.conf, all config files
>> belong into /etc/modprobe.d/.
>>  Formatting mgs, mds, osts
>> Format mds1: /tmp/lustre-mdt1
>> Format ost1: /tmp/lustre-ost1
>> Format ost2: /tmp/lustre-ost2
>> Checking servers environments
>> Checking clients ip-10-204-59-145 environments
>> Loading modules from /usr/lib64/lustre/tests/..
>> debug=0x33f0404
>> subsystem_debug=0xffb7e3ff
>> gss/krb5 is not supported
>> Setup mgs, mdt, osts
>> Starting mds1: -o loop,user_xattr,acl  /tmp/lustre-mdt1 /mnt/mds1
>> mount.lustre: mount /dev/loop0 at /mnt/mds1 failed: Operation not
>> supported
>>
>>
#############################################################################################
>>
>>  Can anyone shed some light on this issue? Does this mean current
>> Whamcloud Lustre code base
(git://git.whamcloud.com/fs/lustre-release.git)
>> is not ready for test drive?
>>
>>  Detailed system log messages is attached for your information, the
test
>> machine''s info is also dumped as following:
>>
>>  [root at ip-10-204-59-145 tests]# uname -a
>>  Linux ip-10-204-59-145 2.6.32.lustre21 #6 SMP Wed Jun 22 15:27:40 EDT
>> 2011 x86_64 x86_64 x86_64 GNU/Linux
>>
>>  [root at ip-10-204-59-145 tests]# cat /etc/redhat-release
>> Red Hat Enterprise Linux Server release 6.1 (Santiago)
>>
>>  BTW, thanks to the Whamcloud team for contributing so much to Lustre,
>> without your effort Lustre is almost dead.
>>
>>  Regards,
>> -Jon.
>> jon.zhu at gmail.com
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Lustre-discuss mailing listLustre-discuss at
lists.lustre.orghttp://lists.lustre.org/mailman/listinfo/lustre-discuss
>>
>>
>> --
>> Peter Jones
>> Whamcloud, Inc.www.whamcloud.com
>>
>>
>> _______________________________________________
>> Lustre-discuss mailing list
>> Lustre-discuss at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110623/18188ce6/attachment.html

I still got some crash when further run some I/O test with the build,
here''s
some system message containing call stack info maybe be useful to you to
find the bug:

Jun 23 21:39:50 ip-10-112-59-173 abrtd: Registered Database plugin
''SQLite3''
Jun 23 21:39:51 ip-10-112-59-173 abrtd: Non-processed crash in
/var/spool/abrt/kerneloops-1308879590-1002-1, saving into database
Jun 23 21:40:02 ip-10-112-59-173 abrtd: Done checking for unsaved crashes
Jun 23 21:40:02 ip-10-112-59-173 abrtd: Init complete, entering main loop
Jun 23 21:40:02 ip-10-112-59-173 abrtd: Directory
''kerneloops-1308879590-1002-1'' creation detected
Jun 23 21:40:02 ip-10-112-59-173 abrtd: Huh, this crash is already in db?!
Nothing to do
Jun 23 21:40:33 ip-10-112-59-173 kernel: blkfront: xvdt: barriers disabled
Jun 23 21:40:33 ip-10-112-59-173 kernel: xvdt: unknown partition table
Jun 23 21:41:49 ip-10-112-59-173 yum[1192]: Installed:
cryptsetup-luks-libs-1.2.0-3.el6_1.2.x86_64
Jun 23 21:41:50 ip-10-112-59-173 abrt: Kerneloops: Reported 1 kernel oopses
to Abrt
Jun 23 21:41:50 ip-10-112-59-173 abrtd: Directory
''kerneloops-1308879710-1002-1'' creation detected
Jun 23 21:41:50 ip-10-112-59-173 yum[1192]: Installed:
cryptsetup-luks-1.2.0-3.el6_1.2.x86_64
Jun 23 21:41:50 ip-10-112-59-173 abrtd: New crash
/var/spool/abrt/kerneloops-1308879710-1002-1, processing
Jun 23 21:44:00 ip-10-112-59-173 kernel: Intel AES-NI instructions are not
detected.
Jun 23 21:44:00 ip-10-112-59-173 kernel: padlock: VIA PadLock not detected.
Jun 23 21:44:01 ip-10-112-59-173 kernel: padlock: VIA PadLock Hash Engine
not detected.
Jun 23 21:44:01 ip-10-112-59-173 modprobe: FATAL: Error inserting
padlock_sha
(/lib/modules/2.6.32.lustre21/kernel/drivers/crypto/padlock-sha.ko): No such
device
Jun 23 21:44:06 ip-10-112-59-173 ntpd[993]: synchronized to 69.164.206.65,
stratum 3
Jun 23 21:44:06 ip-10-112-59-173 ntpd[993]: kernel time sync status change
2001
Jun 23 21:45:53 ip-10-112-59-173 kernel: mke2fs used greatest stack depth:
3296 bytes left
Jun 23 21:45:54 ip-10-112-59-173 kernel: init dynlocks cache
Jun 23 21:45:54 ip-10-112-59-173 kernel: LDISKFS-fs warning (device dm-0):
ldiskfs_fill_super: extents feature not enabled on this filesystem, use
tune2fs.
Jun 23 21:45:54 ip-10-112-59-173 kernel: LDISKFS-fs (dm-0): warning: maximal
mount count reached, running e2fsck is recommended
Jun 23 21:45:54 ip-10-112-59-173 kernel: LDISKFS-fs (dm-0): mounted
filesystem with ordered data mode
Jun 23 21:46:10 ip-10-112-59-173 kernel: Lustre: OBD class driver,
http://www.lustre.org/
Jun 23 21:46:10 ip-10-112-59-173 kernel: Lustre:         Lustre Version:
2.0.62
Jun 23 21:46:10 ip-10-112-59-173 kernel: Lustre:         Build Version:
v2_0_62_0-ge4cb5ca-CHANGED-2.6.32.lustre21
Jun 23 21:46:10 ip-10-112-59-173 kernel: Lustre: Lustre LU module
(ffffffffa02cfbe0).
Jun 23 21:46:11 ip-10-112-59-173 kernel: Lustre: Added LNI
10.112.59.173 at tcp[8/256/0/180]
Jun 23 21:46:11 ip-10-112-59-173 kernel: Lustre: Accept secure, port 988
Jun 23 21:46:11 ip-10-112-59-173 kernel: Lustre: Lustre OSC module
(ffffffffa04fe240).
Jun 23 21:46:12 ip-10-112-59-173 kernel: Lustre: Lustre LOV module
(ffffffffa055cb40).
Jun 23 21:46:12 ip-10-112-59-173 kernel: Lustre: Lustre client module
(ffffffffa05e64e0).
Jun 23 21:46:12 ip-10-112-59-173 kernel: LDISKFS-fs warning (device dm-0):
ldiskfs_fill_super: extents feature not enabled on this filesystem, use
tune2fs.
Jun 23 21:46:12 ip-10-112-59-173 kernel: LDISKFS-fs (dm-0): mounted
filesystem with ordered data mode
Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
]------------
Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Not tainted)
Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in: lustre(U) lov(U)
osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U)
lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd aes_x86_64
aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront ext4 mbcache
jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm: mount.lustre Not
tainted 2.6.32.lustre21 #6
Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a53b7>] ?
shrink_dcache_for_umount_subtree+0x187/0x340
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a55a6>] ?
shrink_dcache_for_umount+0x36/0x60
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f4ff>] ?
generic_shutdown_super+0x1f/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0273f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0277a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0279070>] ?
lustre_init_lsi+0xd0/0x5b0 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0272885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace a8fb737c71bfba13
]---
Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
]------------
Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in: lustre(U) lov(U)
osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U)
lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd aes_x86_64
aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront ext4 mbcache
jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm: mount.lustre
Tainted: G        W  ----------------   2.6.32.lustre21 #6
Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a53b7>] ?
shrink_dcache_for_umount_subtree+0x187/0x340
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a55a6>] ?
shrink_dcache_for_umount+0x36/0x60
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f4ff>] ?
generic_shutdown_super+0x1f/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0273f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0277a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0279070>] ?
lustre_init_lsi+0xd0/0x5b0 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0272885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace a8fb737c71bfba14
]---
Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
]------------
Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in: lustre(U) lov(U)
osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U)
lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd aes_x86_64
aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront ext4 mbcache
jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm: mount.lustre
Tainted: G        W  ----------------   2.6.32.lustre21 #6
Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f52c>] ?
generic_shutdown_super+0x4c/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0273f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0277a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0279070>] ?
lustre_init_lsi+0xd0/0x5b0 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0272885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace a8fb737c71bfba15
]---
Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
]------------
Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in: lustre(U) lov(U)
osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U)
lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd aes_x86_64
aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront ext4 mbcache
jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm: mount.lustre
Tainted: G        W  ----------------   2.6.32.lustre21 #6
Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f52c>] ?
generic_shutdown_super+0x4c/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0273f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0277a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0279070>] ?
lustre_init_lsi+0xd0/0x5b0 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0272885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace a8fb737c71bfba16
]---
Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
]------------
Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in: lustre(U) lov(U)
osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U)
lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd aes_x86_64
aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront ext4 mbcache
jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm: mount.lustre
Tainted: G        W  ----------------   2.6.32.lustre21 #6
Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f52c>] ?
generic_shutdown_super+0x4c/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0273f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0277a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0279070>] ?
lustre_init_lsi+0xd0/0x5b0 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0272885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace a8fb737c71bfba17
]---
Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
]------------
Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in: lustre(U) lov(U)
osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U)
lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd aes_x86_64
aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront ext4 mbcache
jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm: mount.lustre
Tainted: G        W  ----------------   2.6.32.lustre21 #6
Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f52c>] ?
generic_shutdown_super+0x4c/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0273f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0277a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0279070>] ?
lustre_init_lsi+0xd0/0x5b0 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0272885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace a8fb737c71bfba18
]---
Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
]------------
Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in: lustre(U) lov(U)
osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U)
lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd aes_x86_64
aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront ext4 mbcache
jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm: mount.lustre
Tainted: G        W  ----------------   2.6.32.lustre21 #6
Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f52c>] ?
generic_shutdown_super+0x4c/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0273f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0277a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0279070>] ?
lustre_init_lsi+0xd0/0x5b0 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0272885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace a8fb737c71bfba19
]---
Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
]------------
Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in: lustre(U) lov(U)
osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U)
lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd aes_x86_64
aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront ext4 mbcache
jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm: mount.lustre
Tainted: G        W  ----------------   2.6.32.lustre21 #6
Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f52c>] ?
generic_shutdown_super+0x4c/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0273f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0277a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0279070>] ?
lustre_init_lsi+0xd0/0x5b0 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0272885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace a8fb737c71bfba1a
]---
Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
]------------
Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Tainted: G        W  ----------------  )
Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in: lustre(U) lov(U)
osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U)
lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd aes_x86_64
aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront ext4 mbcache
jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm: mount.lustre
Tainted: G        W  ----------------   2.6.32.lustre21 #6
Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a82f9>] ?
invalidate_inodes+0xc9/0x180
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f548>] ?
generic_shutdown_super+0x68/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0273f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0277a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0279070>] ?
lustre_init_lsi+0xd0/0x5b0 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0272885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace a8fb737c71bfba1b
]---
Jun 23 21:46:12 ip-10-112-59-173 kernel: LDISKFS-fs warning (device dm-0):
ldiskfs_fill_super: extents feature not enabled on this filesystem, use
tune2fs.
Jun 23 21:46:12 ip-10-112-59-173 kernel: LDISKFS-fs (dm-0): mounted
filesystem with ordered data mode
Jun 23 21:46:13 ip-10-112-59-173 kernel: Lustre: MGS MGS started
Jun 23 21:46:13 ip-10-112-59-173 kernel: Lustre:
1421:0:(sec.c:1474:sptlrpc_import_sec_adapt()) import MGC10.112.59.173 at
tcp-
>MGC10.112.59.173 at tcp_0 netid 90000: select flavor null
Jun 23 21:46:13 ip-10-112-59-173 kernel: Lustre:
1474:0:(ldlm_lib.c:871:target_handle_connect()) MGS: connection from
1214c02b-3fd7-e9fe-03f5-f408534272c1 at 0@lo t0 exp (null) cur 1308879973 last
0
Jun 23 21:46:13 ip-10-112-59-173 kernel: Lustre: MGC10.112.59.173 at tcp:
Reactivating import
Jun 23 21:46:13 ip-10-112-59-173 kernel: Lustre: MGS: Regenerating
temp-MDTffff log by user request.
Jun 23 21:46:14 ip-10-112-59-173 kernel: Lustre: Enabling ACL
Jun 23 21:46:14 ip-10-112-59-173 kernel: Lustre: temp-MDT0000: new disk,
initializing
Jun 23 21:46:14 ip-10-112-59-173 kernel: llog_process_th used greatest stack
depth: 1080 bytes left
.......


Regards,
-Jon.



On Thu, Jun 23, 2011 at 3:05 PM, Jon Zhu <jon.zhu at gmail.com> wrote:
> The problem disappeared after I disable SELinux with the following steps,
> it works very well. Maybe we need to mention disabling SELinux and probably
> creating extra firewall policy to enable Lustre inter-node communication in
> the setup guide.
>
> Edit /etc/selinux/config and make sure the following line is
> *SELINUX=disabled*
> *Reboot host. (this is a must, the test environment must have SELINUX
> disabled, *echo 0 >/selinux/enforce won''t work)
> *
> *
> Hope this helps, and thanks for all of your help.
>
> Regards,
> -Jon.
>
>
>
>
> On Thu, Jun 23, 2011 at 8:26 AM, Jon Zhu <jon.zhu at gmail.com>
wrote:
>
>> Thanks, Peter.
>> The procedure has a step to create initrd:
>>
>> # /sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod
--install 2.6.32lustre21
>>
>>
>> It doesn''t work so I used this command instead:
>> mkinitrd /boot/initramfs-2.6.32.lustre21.img 2.6.32.lustre21
>>
>> Looking forward to get the new procedure soon.
>>
>> Regards,
>> -Jon.
>>
>> On Thu, Jun 23, 2011 at 1:02 AM, Peter Jones <pjones at
whamcloud.com>wrote:
>>
>>> **
>>> Jon
>>>
>>> It seems that the instructions (written at the end of May) have
grown
>>> stale since the recent realignment on RHEL6.1. We''ll get
the instructions
>>> updated.
>>>
>>> Peter
>>>
>>>
>>> On 11-06-22 6:03 PM, Jon Zhu wrote:
>>>
>>> Hi, all
>>>
>>>  As a fan of Lustre file system, recently I got a chance to try to
build
>>> Lustre whamcloud code v2.1 branch from scratch, the following build
guide
>>> works pretty well:
>>>
>>>
http://wiki.whamcloud.com/display/PUB/Walk-thru-+Build+Lustre+2.1+on+RHEL6+from+Whamcloud+git
>>>
>>>  Everything works well until the last step, when I
>>> run  /usr/lib64/lustre/tests/llmount.sh, it failed with the
following
>>> error:
>>>
>>>
#############################################################################################
>>> [root at ip-10-204-59-145 tests]#
/usr/lib64/lustre/tests/llmount.sh
>>> Stopping clients: ip-10-204-59-145 /mnt/lustre (opts:)
>>> Stopping clients: ip-10-204-59-145 /mnt/lustre2 (opts:)
>>> Loading modules from /usr/lib64/lustre/tests/..
>>> debug=0x33f0404
>>> subsystem_debug=0xffb7e3ff
>>> gss/krb5 is not supported
>>> WARNING: Deprecated config file /etc/modprobe.conf, all config
files
>>> belong into /etc/modprobe.d/.
>>> WARNING: Deprecated config file /etc/modprobe.conf, all config
files
>>> belong into /etc/modprobe.d/.
>>> WARNING: Deprecated config file /etc/modprobe.conf, all config
files
>>> belong into /etc/modprobe.d/.
>>> WARNING: Deprecated config file /etc/modprobe.conf, all config
files
>>> belong into /etc/modprobe.d/.
>>>  Formatting mgs, mds, osts
>>> Format mds1: /tmp/lustre-mdt1
>>> Format ost1: /tmp/lustre-ost1
>>> Format ost2: /tmp/lustre-ost2
>>> Checking servers environments
>>> Checking clients ip-10-204-59-145 environments
>>> Loading modules from /usr/lib64/lustre/tests/..
>>> debug=0x33f0404
>>> subsystem_debug=0xffb7e3ff
>>> gss/krb5 is not supported
>>> Setup mgs, mdt, osts
>>> Starting mds1: -o loop,user_xattr,acl  /tmp/lustre-mdt1 /mnt/mds1
>>> mount.lustre: mount /dev/loop0 at /mnt/mds1 failed: Operation not
>>> supported
>>>
>>>
#############################################################################################
>>>
>>>  Can anyone shed some light on this issue? Does this mean current
>>> Whamcloud Lustre code base (git://
>>> git.whamcloud.com/fs/lustre-release.git) is not ready for test
drive?
>>>
>>>  Detailed system log messages is attached for your information, the
test
>>> machine''s info is also dumped as following:
>>>
>>>  [root at ip-10-204-59-145 tests]# uname -a
>>>  Linux ip-10-204-59-145 2.6.32.lustre21 #6 SMP Wed Jun 22 15:27:40
EDT
>>> 2011 x86_64 x86_64 x86_64 GNU/Linux
>>>
>>>  [root at ip-10-204-59-145 tests]# cat /etc/redhat-release
>>> Red Hat Enterprise Linux Server release 6.1 (Santiago)
>>>
>>>  BTW, thanks to the Whamcloud team for contributing so much to
Lustre,
>>> without your effort Lustre is almost dead.
>>>
>>>  Regards,
>>> -Jon.
>>> jon.zhu at gmail.com
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Lustre-discuss mailing listLustre-discuss at
lists.lustre.orghttp://lists.lustre.org/mailman/listinfo/lustre-discuss
>>>
>>>
>>> --
>>> Peter Jones
>>> Whamcloud, Inc.www.whamcloud.com
>>>
>>>
>>> _______________________________________________
>>> Lustre-discuss mailing list
>>> Lustre-discuss at lists.lustre.org
>>> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110623/870d8e28/attachment-0001.html

Hwllo~

On Jun 23, 2011, at 9:51 PM, Jon Zhu wrote:
> I still got some crash when further run some I/O test with the build,
here''s some system message containing call stack info maybe be useful
to you to find the bug:
> Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
]------------
> Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at kernel/sched.c:7087
__cond_resched_lock+0x8e/0xb0() (Not tainted)
> Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in: lustre(U)
lov(U) osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U)
lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd aes_x86_64
aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront ext4 mbcache jbd2
xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
> Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm: mount.lustre Not
tainted 2.6.32.lustre21 #6
> Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a53b7>] ?
shrink_dcache_for_umount_subtree+0x187/0x340
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a55a6>] ?
shrink_dcache_for_umount+0x36/0x60
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f4ff>] ?
generic_shutdown_super+0x1f/0xe0
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0273f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0277a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0279070>] ?
lustre_init_lsi+0xd0/0x5b0 [obdclass]
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0272885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
> Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
> Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace a8fb737c71bfba13
]---
This is not a crash, it''s just a warning about scheduling in
inappropriate context I guess, but the kernel will continue to work.
Interesting that I have never seen anything like that in rhel5 xen kernels,
perhaps it''s something with rhel6.1 xen?

Bye,
    Oleg
--
Oleg Drokin
Senior Software Engineer
Whamcloud, Inc.

Yes this is a Redhat 6.1 xen kernel, it works with this warning message, but
well, I found under /var/spool/abrt/kerneloops-1308854953-1114-9 directory,
there is a file called backtrace:

[root at ip-10-83-7-78 kerneloops-1308854953-1114-9]# cat backtrace
WARNING: at kernel/sched.c:7087 __cond_resched_lock+0x8e/0xb0() (Tainted: G
       W  ----------------  )
Modules linked in: ldiskfs(U) lustre(U) lov(U) osc(U) lquota(U) mdc(U)
fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U)
autofs4 ipt_REJECT ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state
nf_conntrack ip6table_filter ip6_tables ipv6 microcode xen_netfront ext4
mbcache jbd2 xen_blkfront dm_mod [last unloaded: nf_defrag_ipv4]
Pid: 3778, comm: mount.lustre Tainted: G        W  ----------------
2.6.32.lustre21 #6
Call Trace:
[<ffffffff81069c37>] ? warn_slowpath_common+0x87/0xc0
[<ffffffff81069c8a>] ? warn_slowpath_null+0x1a/0x20
[<ffffffff810654fe>] ? __cond_resched_lock+0x8e/0xb0
[<ffffffff811a82f9>] ? invalidate_inodes+0xc9/0x180
[<ffffffff8118f548>] ? generic_shutdown_super+0x68/0xe0
[<ffffffff8118f5f1>] ? kill_block_super+0x31/0x50
[<ffffffff811906b5>] ? deactivate_super+0x85/0xa0
[<ffffffff811ac5af>] ? mntput_no_expire+0xbf/0x110
[<ffffffffa0231f8e>] ? unlock_mntput+0x3e/0x60 [obdclass]
[<ffffffffa0235a98>] ? server_kernel_mount+0x268/0xe80 [obdclass]
[<ffffffffa023ed40>] ? lustre_fill_super+0x0/0x1290 [obdclass]
[<ffffffffa0237070>] ? lustre_init_lsi+0xd0/0x5b0 [obdclass]
[<ffffffff810ac71d>] ? lock_release+0xed/0x220
[<ffffffffa023efd0>] ? lustre_fill_super+0x290/0x1290 [obdclass]
[<ffffffff8118ee20>] ? set_anon_super+0x0/0x110
[<ffffffffa023ed40>] ? lustre_fill_super+0x0/0x1290 [obdclass]
[<ffffffff8119035f>] ? get_sb_nodev+0x5f/0xa0
[<ffffffffa0230885>] ? lustre_get_sb+0x25/0x30 [obdclass]
[<ffffffff8118ffbb>] ? vfs_kern_mount+0x7b/0x1b0
[<ffffffff81190162>] ? do_kern_mount+0x52/0x130
[<ffffffff811ae647>] ? do_mount+0x2e7/0x870
[<ffffffff811aec60>] ? sys_mount+0x90/0xe0
[<ffffffff8100b132>] ? system_call_fastpath+0x16/0x1b

You are right kernel is still running but, this kerneloops-xxx directory
name makes me think it''s a  crash, maybe it''s recoverable. Any
idea?

-Jon.


On Fri, Jun 24, 2011 at 2:43 PM, Oleg Drokin <green at whamcloud.com>
wrote:
> Hwllo~
>
> On Jun 23, 2011, at 9:51 PM, Jon Zhu wrote:
>
> > I still got some crash when further run some I/O test with the build,
> here''s some system message containing call stack info maybe be
useful to you
> to find the bug:
>
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
> ]------------
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at
kernel/sched.c:7087
> __cond_resched_lock+0x8e/0xb0() (Not tainted)
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in: lustre(U)
> lov(U) osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U)
> obdclass(U) lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd
> aes_x86_64 aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront
ext4
> mbcache jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm: mount.lustre
> Not tainted 2.6.32.lustre21 #6
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c37>] ?
> warn_slowpath_common+0x87/0xc0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81007671>] ?
> __raw_callee_save_xen_save_fl+0x11/0x1e
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c8a>] ?
> warn_slowpath_null+0x1a/0x20
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810654fe>] ?
> __cond_resched_lock+0x8e/0xb0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a53b7>] ?
> shrink_dcache_for_umount_subtree+0x187/0x340
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a55a6>] ?
> shrink_dcache_for_umount+0x36/0x60
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f4ff>] ?
> generic_shutdown_super+0x1f/0xe0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f5f1>] ?
> kill_block_super+0x31/0x50
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811906b5>] ?
> deactivate_super+0x85/0xa0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ac5af>] ?
> mntput_no_expire+0xbf/0x110
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0273f8e>] ?
> unlock_mntput+0x3e/0x60 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0277a98>] ?
> server_kernel_mount+0x268/0xe80 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
> lustre_fill_super+0x0/0x1290 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0279070>] ?
> lustre_init_lsi+0xd0/0x5b0 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810ac71d>] ?
> lock_release+0xed/0x220
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280fd0>] ?
> lustre_fill_super+0x290/0x1290 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ee20>] ?
> set_anon_super+0x0/0x110
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
> lustre_fill_super+0x0/0x1290 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8119035f>] ?
> get_sb_nodev+0x5f/0xa0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0272885>] ?
> lustre_get_sb+0x25/0x30 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ffbb>] ?
> vfs_kern_mount+0x7b/0x1b0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81190162>] ?
> do_kern_mount+0x52/0x130
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ae647>] ?
> do_mount+0x2e7/0x870
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811aec60>] ?
> sys_mount+0x90/0xe0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8100b132>] ?
> system_call_fastpath+0x16/0x1b
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace
a8fb737c71bfba13
> ]---
>
> This is not a crash, it''s just a warning about scheduling in
inappropriate
> context I guess, but the kernel will continue to work.
> Interesting that I have never seen anything like that in rhel5 xen kernels,
> perhaps it''s something with rhel6.1 xen?
>
> Bye,
>    Oleg
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110624/40a18296/attachment.html

Hello!


On Jun 24, 2011, at 4:00 PM, Jon Zhu wrote:
> Yes this is a Redhat 6.1 xen kernel, it works with this warning message,
but well, I found under /var/spool/abrt/kerneloops-1308854953-1114-9 directory,
there is a file called backtrace:
> You are right kernel is still running but, this kerneloops-xxx directory
name makes me think it''s a  crash, maybe it''s recoverable. Any
idea?
It''s not a crash, just a warning.

Bye,
    Oleg
--
Oleg Drokin
Senior Software Engineer
Whamcloud, Inc.

Agree with you. But here comes the real problem, when I''m running a
program
called fileop to benchmark the Lustre file system from one client, the other
client failed to list file in the directory where the fileop generates files
on the mounted Lustre volume. Is this a known issue?

[root at test1 fileop_L1_0]# ls
ls: cannot open directory .: Stale NFS file handle


Thanks,
-Jon.




On Fri, Jun 24, 2011 at 4:06 PM, Oleg Drokin <green at whamcloud.com>
wrote:
> Hello!
>
>
> On Jun 24, 2011, at 4:00 PM, Jon Zhu wrote:
>
> > Yes this is a Redhat 6.1 xen kernel, it works with this warning
message,
> but well, I found under /var/spool/abrt/kerneloops-1308854953-1114-9
> directory, there is a file called backtrace:
> > You are right kernel is still running but, this kerneloops-xxx
directory
> name makes me think it''s a  crash, maybe it''s
recoverable. Any idea?
>
> It''s not a crash, just a warning.
>
> Bye,
>    Oleg
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110624/7ea380ed/attachment-0001.html

Did it delete the dir before creating the files, but after the other client did
chdir?

On Jun 24, 2011, at 5:09 PM, Jon Zhu wrote:
> Agree with you. But here comes the real problem, when I''m running
a program called fileop to benchmark the Lustre file system from one client, the
other client failed to list file in the directory where the fileop generates
files on the mounted Lustre volume. Is this a known issue?
> 
> [root at test1 fileop_L1_0]# ls
> ls: cannot open directory .: Stale NFS file handle
> 
> 
> Thanks,
> -Jon.
> 
> 
> 
> 
> On Fri, Jun 24, 2011 at 4:06 PM, Oleg Drokin <green at whamcloud.com>
wrote:
> Hello!
> 
> 
> On Jun 24, 2011, at 4:00 PM, Jon Zhu wrote:
> 
> > Yes this is a Redhat 6.1 xen kernel, it works with this warning
message, but well, I found under /var/spool/abrt/kerneloops-1308854953-1114-9
directory, there is a file called backtrace:
> > You are right kernel is still running but, this kerneloops-xxx
directory name makes me think it''s a  crash, maybe it''s
recoverable. Any idea?
> 
> It''s not a crash, just a warning.
> 
> Bye,
>    Oleg
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
> 
> 
--
Oleg Drokin
Senior Software Engineer
Whamcloud, Inc.

Do you mean if this directory is continuously being deleted and re-created
during the test so that''s why the other client cannot list file inside
it? I
guess so, after I stopped the fileop test program I can get into the
directory and there is nothing in it.

Thanks,
-Jon.



On Fri, Jun 24, 2011 at 5:11 PM, Oleg Drokin <green at whamcloud.com>
wrote:
> Did it delete the dir before creating the files, but after the other client
> did chdir?
>
> On Jun 24, 2011, at 5:09 PM, Jon Zhu wrote:
>
> > Agree with you. But here comes the real problem, when I''m
running a
> program called fileop to benchmark the Lustre file system from one client,
> the other client failed to list file in the directory where the fileop
> generates files on the mounted Lustre volume. Is this a known issue?
> >
> > [root at test1 fileop_L1_0]# ls
> > ls: cannot open directory .: Stale NFS file handle
> >
> >
> > Thanks,
> > -Jon.
> >
> >
> >
> >
> > On Fri, Jun 24, 2011 at 4:06 PM, Oleg Drokin <green at
whamcloud.com>
> wrote:
> > Hello!
> >
> >
> > On Jun 24, 2011, at 4:00 PM, Jon Zhu wrote:
> >
> > > Yes this is a Redhat 6.1 xen kernel, it works with this warning
> message, but well, I found under
> /var/spool/abrt/kerneloops-1308854953-1114-9 directory, there is a file
> called backtrace:
> > > You are right kernel is still running but, this kerneloops-xxx
> directory name makes me think it''s a  crash, maybe it''s
recoverable. Any
> idea?
> >
> > It''s not a crash, just a warning.
> >
> > Bye,
> >    Oleg
> > --
> > Oleg Drokin
> > Senior Software Engineer
> > Whamcloud, Inc.
> >
> >
>
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110624/f588d6b8/attachment.html

Yes, in case of a patchless client I expect you''d get something like
what you see.
I expect that if you cd into the dir after the test is started it might work,
though.

On Jun 24, 2011, at 5:47 PM, Jon Zhu wrote:
> Do you mean if this directory is continuously being deleted and re-created
during the test so that''s why the other client cannot list file inside
it? I guess so, after I stopped the fileop test program I can get into the
directory and there is nothing in it.
> 
> Thanks,
> -Jon.
> 
> 
> 
> On Fri, Jun 24, 2011 at 5:11 PM, Oleg Drokin <green at whamcloud.com>
wrote:
> Did it delete the dir before creating the files, but after the other client
did chdir?
> 
> On Jun 24, 2011, at 5:09 PM, Jon Zhu wrote:
> 
> > Agree with you. But here comes the real problem, when I''m
running a program called fileop to benchmark the Lustre file system from one
client, the other client failed to list file in the directory where the fileop
generates files on the mounted Lustre volume. Is this a known issue?
> >
> > [root at test1 fileop_L1_0]# ls
> > ls: cannot open directory .: Stale NFS file handle
> >
> >
> > Thanks,
> > -Jon.
> >
> >
> >
> >
> > On Fri, Jun 24, 2011 at 4:06 PM, Oleg Drokin <green at
whamcloud.com> wrote:
> > Hello!
> >
> >
> > On Jun 24, 2011, at 4:00 PM, Jon Zhu wrote:
> >
> > > Yes this is a Redhat 6.1 xen kernel, it works with this warning
message, but well, I found under /var/spool/abrt/kerneloops-1308854953-1114-9
directory, there is a file called backtrace:
> > > You are right kernel is still running but, this kerneloops-xxx
directory name makes me think it''s a  crash, maybe it''s
recoverable. Any idea?
> >
> > It''s not a crash, just a warning.
> >
> > Bye,
> >    Oleg
> > --
> > Oleg Drokin
> > Senior Software Engineer
> > Whamcloud, Inc.
> >
> >
> 
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
> 
> 
--
Oleg Drokin
Senior Software Engineer
Whamcloud, Inc.

Got it. Right now the client is running the same patched Redhat 6.1 xen
kernel as MGS and OSS node, I guess that''s not the **patchless** client
you
mentioned.

Does patchless client means client running on un-patched kernel? Is there a
way to build such client from the latest v2.1 code base? Or I can use
official 2.0 release client to work with v2.1 MDS/OSS nodes?

Thanks for the quick replies!

-Jon.


On Fri, Jun 24, 2011 at 5:50 PM, Oleg Drokin <green at whamcloud.com>
wrote:
> Yes, in case of a patchless client I expect you''d get something
like what
> you see.
> I expect that if you cd into the dir after the test is started it might
> work, though.
>
> On Jun 24, 2011, at 5:47 PM, Jon Zhu wrote:
>
> > Do you mean if this directory is continuously being deleted and
> re-created during the test so that''s why the other client cannot
list file
> inside it? I guess so, after I stopped the fileop test program I can get
> into the directory and there is nothing in it.
> >
> > Thanks,
> > -Jon.
> >
> >
> >
> > On Fri, Jun 24, 2011 at 5:11 PM, Oleg Drokin <green at
whamcloud.com>
> wrote:
> > Did it delete the dir before creating the files, but after the other
> client did chdir?
> >
> > On Jun 24, 2011, at 5:09 PM, Jon Zhu wrote:
> >
> > > Agree with you. But here comes the real problem, when
I''m running a
> program called fileop to benchmark the Lustre file system from one client,
> the other client failed to list file in the directory where the fileop
> generates files on the mounted Lustre volume. Is this a known issue?
> > >
> > > [root at test1 fileop_L1_0]# ls
> > > ls: cannot open directory .: Stale NFS file handle
> > >
> > >
> > > Thanks,
> > > -Jon.
> > >
> > >
> > >
> > >
> > > On Fri, Jun 24, 2011 at 4:06 PM, Oleg Drokin <green at
whamcloud.com>
> wrote:
> > > Hello!
> > >
> > >
> > > On Jun 24, 2011, at 4:00 PM, Jon Zhu wrote:
> > >
> > > > Yes this is a Redhat 6.1 xen kernel, it works with this
warning
> message, but well, I found under
> /var/spool/abrt/kerneloops-1308854953-1114-9 directory, there is a file
> called backtrace:
> > > > You are right kernel is still running but, this
kerneloops-xxx
> directory name makes me think it''s a  crash, maybe it''s
recoverable. Any
> idea?
> > >
> > > It''s not a crash, just a warning.
> > >
> > > Bye,
> > >    Oleg
> > > --
> > > Oleg Drokin
> > > Senior Software Engineer
> > > Whamcloud, Inc.
> > >
> > >
> >
> > --
> > Oleg Drokin
> > Senior Software Engineer
> > Whamcloud, Inc.
> >
> >
>
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110624/e9e66ca7/attachment.html

Hello!

On Jun 24, 2011, at 6:01 PM, Jon Zhu wrote:
> Got it. Right now the client is running the same patched Redhat 6.1 xen
kernel as MGS and OSS node, I guess that''s not the **patchless** client
you mentioned.
Well, lately all clients are "patchless" meaning we no longer ship a
lot of vfs patches we used to.
> Does patchless client means client running on un-patched kernel? Is there a
way to build such client from the latest v2.1 code base? Or I can use official
2.0 release client to work with v2.1 MDS/OSS nodes?
You can build a fully patchless client from 2.1 sources, just checkout latest
2.1 and build it aginst your kernel-devel package
(--with-linux=/lib/modules/`uname -r`/build to configure while booted into
rhel6.1 kernel from RH).

Bye,
    Oleg
--
Oleg Drokin
Senior Software Engineer
Whamcloud, Inc.

Great, thanks a lot.

-Jon.

On Fri, Jun 24, 2011 at 6:56 PM, Oleg Drokin <green at whamcloud.com>
wrote:
> Hello!
>
> On Jun 24, 2011, at 6:01 PM, Jon Zhu wrote:
>
> > Got it. Right now the client is running the same patched Redhat 6.1
xen
> kernel as MGS and OSS node, I guess that''s not the **patchless**
client you
> mentioned.
>
> Well, lately all clients are "patchless" meaning we no longer
ship a lot of
> vfs patches we used to.
>
> > Does patchless client means client running on un-patched kernel? Is
there
> a way to build such client from the latest v2.1 code base? Or I can use
> official 2.0 release client to work with v2.1 MDS/OSS nodes?
>
> You can build a fully patchless client from 2.1 sources, just checkout
> latest 2.1 and build it aginst your kernel-devel package
> (--with-linux=/lib/modules/`uname -r`/build to configure while booted into
> rhel6.1 kernel from RH).
>
> Bye,
>    Oleg
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110624/447062c4/attachment-0001.html

Hi, Oleg

Do we have a procedure on how to build v2.1 GA code on CentOS 5.6 (xen)? On
whamcloud wiki I can only find build v2.1 on RHEL 6.1 or build v1.8 on
CentOS 5.6.

BTW, congratulations on the 2.1 release!

Regards,

Jon Zhu
Sent from Google Mail




On Fri, Jun 24, 2011 at 2:43 PM, Oleg Drokin <green at whamcloud.com>
wrote:
> Hwllo~
>
> On Jun 23, 2011, at 9:51 PM, Jon Zhu wrote:
>
> > I still got some crash when further run some I/O test with the build,
> here''s some system message containing call stack info maybe be
useful to you
> to find the bug:
>
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
> ]------------
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at
kernel/sched.c:7087
> __cond_resched_lock+0x8e/0xb0() (Not tainted)
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in: lustre(U)
> lov(U) osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U)
> obdclass(U) lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd
> aes_x86_64 aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront
ext4
> mbcache jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm: mount.lustre
> Not tainted 2.6.32.lustre21 #6
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c37>] ?
> warn_slowpath_common+0x87/0xc0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81007671>] ?
> __raw_callee_save_xen_save_fl+0x11/0x1e
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c8a>] ?
> warn_slowpath_null+0x1a/0x20
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810654fe>] ?
> __cond_resched_lock+0x8e/0xb0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a53b7>] ?
> shrink_dcache_for_umount_subtree+0x187/0x340
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a55a6>] ?
> shrink_dcache_for_umount+0x36/0x60
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f4ff>] ?
> generic_shutdown_super+0x1f/0xe0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f5f1>] ?
> kill_block_super+0x31/0x50
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811906b5>] ?
> deactivate_super+0x85/0xa0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ac5af>] ?
> mntput_no_expire+0xbf/0x110
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0273f8e>] ?
> unlock_mntput+0x3e/0x60 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0277a98>] ?
> server_kernel_mount+0x268/0xe80 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
> lustre_fill_super+0x0/0x1290 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0279070>] ?
> lustre_init_lsi+0xd0/0x5b0 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810ac71d>] ?
> lock_release+0xed/0x220
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280fd0>] ?
> lustre_fill_super+0x290/0x1290 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ee20>] ?
> set_anon_super+0x0/0x110
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
> lustre_fill_super+0x0/0x1290 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8119035f>] ?
> get_sb_nodev+0x5f/0xa0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0272885>] ?
> lustre_get_sb+0x25/0x30 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ffbb>] ?
> vfs_kern_mount+0x7b/0x1b0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81190162>] ?
> do_kern_mount+0x52/0x130
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ae647>] ?
> do_mount+0x2e7/0x870
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811aec60>] ?
> sys_mount+0x90/0xe0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8100b132>] ?
> system_call_fastpath+0x16/0x1b
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace
a8fb737c71bfba13
> ]---
>
> This is not a crash, it''s just a warning about scheduling in
inappropriate
> context I guess, but the kernel will continue to work.
> Interesting that I have never seen anything like that in rhel5 xen kernels,
> perhaps it''s something with rhel6.1 xen?
>
> Bye,
>    Oleg
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20110929/54e55fd3/attachment.html

Hello!

   There is nothing special, same as rhel6.1:
   unpack the lustre source, run autogen.sh, run configure and provide the path
to the linux kernel source for your distro (need to patch first too), make.

Bye,
    Oleg
On Sep 29, 2011, at 11:21 PM, Jon Zhu wrote:
> Hi, Oleg
> 
> Do we have a procedure on how to build v2.1 GA code on CentOS 5.6 (xen)? On
whamcloud wiki I can only find build v2.1 on RHEL 6.1 or build v1.8 on CentOS
5.6.
> 
> BTW, congratulations on the 2.1 release!
> 
> Regards,
> 
> Jon Zhu
> Sent from Google Mail
> 
> 
> 
> 
> On Fri, Jun 24, 2011 at 2:43 PM, Oleg Drokin <green at whamcloud.com>
wrote:
> Hwllo~
> 
> On Jun 23, 2011, at 9:51 PM, Jon Zhu wrote:
> 
> > I still got some crash when further run some I/O test with the build,
here''s some system message containing call stack info maybe be useful
to you to find the bug:
> 
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
]------------
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at
kernel/sched.c:7087 __cond_resched_lock+0x8e/0xb0() (Not tainted)
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in: lustre(U)
lov(U) osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U) obdclass(U)
lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd aes_x86_64
aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront ext4 mbcache jbd2
xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm: mount.lustre
Not tainted 2.6.32.lustre21 #6
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c37>] ?
warn_slowpath_common+0x87/0xc0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81007671>] ?
__raw_callee_save_xen_save_fl+0x11/0x1e
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81069c8a>] ?
warn_slowpath_null+0x1a/0x20
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810654fe>] ?
__cond_resched_lock+0x8e/0xb0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a53b7>] ?
shrink_dcache_for_umount_subtree+0x187/0x340
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811a55a6>] ?
shrink_dcache_for_umount+0x36/0x60
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f4ff>] ?
generic_shutdown_super+0x1f/0xe0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118f5f1>] ?
kill_block_super+0x31/0x50
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811906b5>] ?
deactivate_super+0x85/0xa0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ac5af>] ?
mntput_no_expire+0xbf/0x110
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0273f8e>] ?
unlock_mntput+0x3e/0x60 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0277a98>] ?
server_kernel_mount+0x268/0xe80 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0279070>] ?
lustre_init_lsi+0xd0/0x5b0 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff810ac71d>] ?
lock_release+0xed/0x220
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280fd0>] ?
lustre_fill_super+0x290/0x1290 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ee20>] ?
set_anon_super+0x0/0x110
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0280d40>] ?
lustre_fill_super+0x0/0x1290 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8119035f>] ?
get_sb_nodev+0x5f/0xa0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffffa0272885>] ?
lustre_get_sb+0x25/0x30 [obdclass]
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8118ffbb>] ?
vfs_kern_mount+0x7b/0x1b0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff81190162>] ?
do_kern_mount+0x52/0x130
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811ae647>] ?
do_mount+0x2e7/0x870
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff811aec60>] ?
sys_mount+0x90/0xe0
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: [<ffffffff8100b132>] ?
system_call_fastpath+0x16/0x1b
> > Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace
a8fb737c71bfba13 ]---
> 
> This is not a crash, it''s just a warning about scheduling in
inappropriate context I guess, but the kernel will continue to work.
> Interesting that I have never seen anything like that in rhel5 xen kernels,
perhaps it''s something with rhel6.1 xen?
> 
> Bye,
>    Oleg
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
> 
> 
--
Oleg Drokin
Senior Software Engineer
Whamcloud, Inc.

Hi, Oleg

I encountered the following error while building Lustre 2.1 release on
Redhat 2.1, do you have any idea on this error?

make[1]: *** No rule to make target
`/build/lustre-release/ldiskfs/Module.symvers'', needed by
`Module.symvers''.
 Stop.


Full build log :
....
+ /usr/lib/rpm/redhat/brp-java-repack-jars
Processing files: lustre-iokit-1.2-201110021351.noarch
Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.IOpHyP
+ umask 022
+ cd /build/kernel/rpmbuild/BUILD
+ cd lustre-iokit-1.2
+
DOCDIR=/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
+ export DOCDIR
+ rm -rf
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
+ /bin/mkdir -p
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
+ cp -pr obdfilter-survey/README.obdfilter-survey
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
+ cp -pr ior-survey/README.ior-survey
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
+ cp -pr ost-survey/README.ost-survey
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
+ cp -pr sgpdd-survey/README.sgpdd-survey
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
+ cp -pr
stats-collect/README.lstats.sh/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
+ exit 0
Provides: lustre-iokit = 1.2
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests)
<= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(VersionedDependencies) <= 3.0.3-1
Requires: /bin/bash /bin/sh /usr/bin/perl perl(File::Path)
perl(Getopt::Long) perl(Getopt::Std) perl(POSIX)
Checking for unpackaged file(s): /usr/lib/rpm/check-files
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64
Wrote: /build/kernel/rpmbuild/SRPMS/lustre-iokit-1.2-201110021351.src.rpm
Wrote:
/build/kernel/rpmbuild/RPMS/noarch/lustre-iokit-1.2-201110021351.noarch.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.0eXePd
+ umask 022
+ cd /build/kernel/rpmbuild/BUILD
+ cd lustre-iokit-1.2
+ /bin/rm -rf
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64
+ exit 0
make[1]: Leaving directory `/build/lustre-release/lustre-iokit''
Finished rpms in lustre-iokit
make[1]: Entering directory `/build/lustre-release''
make[1]: *** No rule to make target
`/build/lustre-release/ldiskfs/Module.symvers'', needed by
`Module.symvers''.
 Stop.
make[1]: Leaving directory `/build/lustre-release''
make: *** [rpms] Error 2


Thanks,
-Jon.


On Thu, Sep 29, 2011 at 11:34 PM, Oleg Drokin <green at whamcloud.com>
wrote:
> Hello!
>
>   There is nothing special, same as rhel6.1:
>   unpack the lustre source, run autogen.sh, run configure and provide the
> path to the linux kernel source for your distro (need to patch first too),
> make.
>
> Bye,
>     Oleg
> On Sep 29, 2011, at 11:21 PM, Jon Zhu wrote:
>
> > Hi, Oleg
> >
> > Do we have a procedure on how to build v2.1 GA code on CentOS 5.6
(xen)?
> On whamcloud wiki I can only find build v2.1 on RHEL 6.1 or build v1.8 on
> CentOS 5.6.
> >
> > BTW, congratulations on the 2.1 release!
> >
> > Regards,
> >
> > Jon Zhu
> > Sent from Google Mail
> >
> >
> >
> >
> > On Fri, Jun 24, 2011 at 2:43 PM, Oleg Drokin <green at
whamcloud.com>
> wrote:
> > Hwllo~
> >
> > On Jun 23, 2011, at 9:51 PM, Jon Zhu wrote:
> >
> > > I still got some crash when further run some I/O test with the
build,
> here''s some system message containing call stack info maybe be
useful to you
> to find the bug:
> >
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
> ]------------
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at
> kernel/sched.c:7087 __cond_resched_lock+0x8e/0xb0() (Not tainted)
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in:
lustre(U)
> lov(U) osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U)
> obdclass(U) lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd
> aes_x86_64 aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront
ext4
> mbcache jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm:
mount.lustre
> Not tainted 2.6.32.lustre21 #6
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81069c37>] ?
> warn_slowpath_common+0x87/0xc0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81007671>] ?
> __raw_callee_save_xen_save_fl+0x11/0x1e
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81069c8a>] ?
> warn_slowpath_null+0x1a/0x20
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff810654fe>] ?
> __cond_resched_lock+0x8e/0xb0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811a53b7>] ?
> shrink_dcache_for_umount_subtree+0x187/0x340
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811a55a6>] ?
> shrink_dcache_for_umount+0x36/0x60
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118f4ff>] ?
> generic_shutdown_super+0x1f/0xe0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118f5f1>] ?
> kill_block_super+0x31/0x50
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811906b5>] ?
> deactivate_super+0x85/0xa0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811ac5af>] ?
> mntput_no_expire+0xbf/0x110
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0273f8e>] ?
> unlock_mntput+0x3e/0x60 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0277a98>] ?
> server_kernel_mount+0x268/0xe80 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280d40>] ?
> lustre_fill_super+0x0/0x1290 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0279070>] ?
> lustre_init_lsi+0xd0/0x5b0 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff810ac71d>] ?
> lock_release+0xed/0x220
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280fd0>] ?
> lustre_fill_super+0x290/0x1290 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118ee20>] ?
> set_anon_super+0x0/0x110
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280d40>] ?
> lustre_fill_super+0x0/0x1290 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8119035f>] ?
> get_sb_nodev+0x5f/0xa0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0272885>] ?
> lustre_get_sb+0x25/0x30 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118ffbb>] ?
> vfs_kern_mount+0x7b/0x1b0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81190162>] ?
> do_kern_mount+0x52/0x130
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811ae647>] ?
> do_mount+0x2e7/0x870
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811aec60>] ?
> sys_mount+0x90/0xe0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8100b132>] ?
> system_call_fastpath+0x16/0x1b
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace
> a8fb737c71bfba13 ]---
> >
> > This is not a crash, it''s just a warning about scheduling in
> inappropriate context I guess, but the kernel will continue to work.
> > Interesting that I have never seen anything like that in rhel5 xen
> kernels, perhaps it''s something with rhel6.1 xen?
> >
> > Bye,
> >    Oleg
> > --
> > Oleg Drokin
> > Senior Software Engineer
> > Whamcloud, Inc.
> >
> >
>
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20111002/998dbe1e/attachment.html

Hello!

    Last time I hit this (some years ago), a simple touch ldiskfs/Module.symvers
helped. I don''t remember what the issue was or how it was properly
fixed, though.

Bye,
    Oleg
On Oct 2, 2011, at 1:57 PM, Jon Zhu wrote:
> Hi, Oleg
> 
> I encountered the following error while building Lustre 2.1 release on
Redhat 2.1, do you have any idea on this error?
> 
> make[1]: *** No rule to make target
`/build/lustre-release/ldiskfs/Module.symvers'', needed by
`Module.symvers''.  Stop.
> 
> 
> Full build log : 
> ....
> + /usr/lib/rpm/redhat/brp-java-repack-jars
> Processing files: lustre-iokit-1.2-201110021351.noarch
> Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.IOpHyP
> + umask 022
> + cd /build/kernel/rpmbuild/BUILD
> + cd lustre-iokit-1.2
> +
DOCDIR=/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> + export DOCDIR
> + rm -rf
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> + /bin/mkdir -p
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> + cp -pr obdfilter-survey/README.obdfilter-survey
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> + cp -pr ior-survey/README.ior-survey
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> + cp -pr ost-survey/README.ost-survey
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> + cp -pr sgpdd-survey/README.sgpdd-survey
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> + cp -pr stats-collect/README.lstats.sh
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> + exit 0
> Provides: lustre-iokit = 1.2
> Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(VersionedDependencies) <= 3.0.3-1
> Requires: /bin/bash /bin/sh /usr/bin/perl perl(File::Path)
perl(Getopt::Long) perl(Getopt::Std) perl(POSIX)
> Checking for unpackaged file(s): /usr/lib/rpm/check-files
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64
> Wrote: /build/kernel/rpmbuild/SRPMS/lustre-iokit-1.2-201110021351.src.rpm
> Wrote:
/build/kernel/rpmbuild/RPMS/noarch/lustre-iokit-1.2-201110021351.noarch.rpm
> Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.0eXePd
> + umask 022
> + cd /build/kernel/rpmbuild/BUILD
> + cd lustre-iokit-1.2
> + /bin/rm -rf
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64
> + exit 0
> make[1]: Leaving directory `/build/lustre-release/lustre-iokit''
> Finished rpms in lustre-iokit
> make[1]: Entering directory `/build/lustre-release''
> make[1]: *** No rule to make target
`/build/lustre-release/ldiskfs/Module.symvers'', needed by
`Module.symvers''.  Stop.
> make[1]: Leaving directory `/build/lustre-release''
> make: *** [rpms] Error 2
> 
> 
> Thanks,
> -Jon.
> 
> 
> On Thu, Sep 29, 2011 at 11:34 PM, Oleg Drokin <green at
whamcloud.com> wrote:
> Hello!
> 
>   There is nothing special, same as rhel6.1:
>   unpack the lustre source, run autogen.sh, run configure and provide the
path to the linux kernel source for your distro (need to patch first too), make.
> 
> Bye,
>    Oleg
> On Sep 29, 2011, at 11:21 PM, Jon Zhu wrote:
> 
> > Hi, Oleg
> >
> > Do we have a procedure on how to build v2.1 GA code on CentOS 5.6
(xen)? On whamcloud wiki I can only find build v2.1 on RHEL 6.1 or build v1.8 on
CentOS 5.6.
> >
> > BTW, congratulations on the 2.1 release!
> >
> > Regards,
> >
> > Jon Zhu
> > Sent from Google Mail
> >
> >
> >
> >
> > On Fri, Jun 24, 2011 at 2:43 PM, Oleg Drokin <green at
whamcloud.com> wrote:
> > Hwllo~
> >
> > On Jun 23, 2011, at 9:51 PM, Jon Zhu wrote:
> >
> > > I still got some crash when further run some I/O test with the
build, here''s some system message containing call stack info maybe be
useful to you to find the bug:
> >
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut here
]------------
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at
kernel/sched.c:7087 __cond_resched_lock+0x8e/0xb0() (Not tainted)
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in:
lustre(U) lov(U) osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U)
obdclass(U) lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd
aes_x86_64 aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront ext4
mbcache jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm:
mount.lustre Not tainted 2.6.32.lustre21 #6
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81069c37>] ? warn_slowpath_common+0x87/0xc0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81007671>] ? __raw_callee_save_xen_save_fl+0x11/0x1e
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81069c8a>] ? warn_slowpath_null+0x1a/0x20
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff810654fe>] ? __cond_resched_lock+0x8e/0xb0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811a53b7>] ? shrink_dcache_for_umount_subtree+0x187/0x340
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811a55a6>] ? shrink_dcache_for_umount+0x36/0x60
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118f4ff>] ? generic_shutdown_super+0x1f/0xe0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118f5f1>] ? kill_block_super+0x31/0x50
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811906b5>] ? deactivate_super+0x85/0xa0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811ac5af>] ? mntput_no_expire+0xbf/0x110
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0273f8e>] ? unlock_mntput+0x3e/0x60 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0277a98>] ? server_kernel_mount+0x268/0xe80 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280d40>] ? lustre_fill_super+0x0/0x1290 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0279070>] ? lustre_init_lsi+0xd0/0x5b0 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff810ac71d>] ? lock_release+0xed/0x220
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280fd0>] ? lustre_fill_super+0x290/0x1290 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118ee20>] ? set_anon_super+0x0/0x110
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280d40>] ? lustre_fill_super+0x0/0x1290 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8119035f>] ? get_sb_nodev+0x5f/0xa0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0272885>] ? lustre_get_sb+0x25/0x30 [obdclass]
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118ffbb>] ? vfs_kern_mount+0x7b/0x1b0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81190162>] ? do_kern_mount+0x52/0x130
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811ae647>] ? do_mount+0x2e7/0x870
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811aec60>] ? sys_mount+0x90/0xe0
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8100b132>] ? system_call_fastpath+0x16/0x1b
> > > Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace
a8fb737c71bfba13 ]---
> >
> > This is not a crash, it''s just a warning about scheduling in
inappropriate context I guess, but the kernel will continue to work.
> > Interesting that I have never seen anything like that in rhel5 xen
kernels, perhaps it''s something with rhel6.1 xen?
> >
> > Bye,
> >    Oleg
> > --
> > Oleg Drokin
> > Senior Software Engineer
> > Whamcloud, Inc.
> >
> >
> 
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
> 
> 
--
Oleg Drokin
Senior Software Engineer
Whamcloud, Inc.

Thanks a lot, the work around works.

-Jon.



On Sun, Oct 2, 2011 at 3:47 PM, Oleg Drokin <green at whamcloud.com>
wrote:
> Hello!
>
>    Last time I hit this (some years ago), a simple touch
> ldiskfs/Module.symvers helped. I don''t remember what the issue was
or how it
> was properly fixed, though.
>
> Bye,
>     Oleg
> On Oct 2, 2011, at 1:57 PM, Jon Zhu wrote:
>
> > Hi, Oleg
> >
> > I encountered the following error while building Lustre 2.1 release on
> Redhat 2.1, do you have any idea on this error?
> >
> > make[1]: *** No rule to make target
> `/build/lustre-release/ldiskfs/Module.symvers'', needed by
`Module.symvers''.
>  Stop.
> >
> >
> > Full build log :
> > ....
> > + /usr/lib/rpm/redhat/brp-java-repack-jars
> > Processing files: lustre-iokit-1.2-201110021351.noarch
> > Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.IOpHyP
> > + umask 022
> > + cd /build/kernel/rpmbuild/BUILD
> > + cd lustre-iokit-1.2
> > +
>
DOCDIR=/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + export DOCDIR
> > + rm -rf
>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + /bin/mkdir -p
>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + cp -pr obdfilter-survey/README.obdfilter-survey
>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + cp -pr ior-survey/README.ior-survey
>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + cp -pr ost-survey/README.ost-survey
>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + cp -pr sgpdd-survey/README.sgpdd-survey
>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + cp -pr
stats-collect/README.lstats.sh/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + exit 0
> > Provides: lustre-iokit = 1.2
> > Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1
> rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <=
4.0-1
> rpmlib(VersionedDependencies) <= 3.0.3-1
> > Requires: /bin/bash /bin/sh /usr/bin/perl perl(File::Path)
> perl(Getopt::Long) perl(Getopt::Std) perl(POSIX)
> > Checking for unpackaged file(s): /usr/lib/rpm/check-files
> /build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64
> > Wrote:
/build/kernel/rpmbuild/SRPMS/lustre-iokit-1.2-201110021351.src.rpm
> > Wrote:
> /build/kernel/rpmbuild/RPMS/noarch/lustre-iokit-1.2-201110021351.noarch.rpm
> > Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.0eXePd
> > + umask 022
> > + cd /build/kernel/rpmbuild/BUILD
> > + cd lustre-iokit-1.2
> > + /bin/rm -rf
> /build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64
> > + exit 0
> > make[1]: Leaving directory
`/build/lustre-release/lustre-iokit''
> > Finished rpms in lustre-iokit
> > make[1]: Entering directory `/build/lustre-release''
> > make[1]: *** No rule to make target
> `/build/lustre-release/ldiskfs/Module.symvers'', needed by
`Module.symvers''.
>  Stop.
> > make[1]: Leaving directory `/build/lustre-release''
> > make: *** [rpms] Error 2
> >
> >
> > Thanks,
> > -Jon.
> >
> >
> > On Thu, Sep 29, 2011 at 11:34 PM, Oleg Drokin <green at
whamcloud.com>
> wrote:
> > Hello!
> >
> >   There is nothing special, same as rhel6.1:
> >   unpack the lustre source, run autogen.sh, run configure and provide
the
> path to the linux kernel source for your distro (need to patch first too),
> make.
> >
> > Bye,
> >    Oleg
> > On Sep 29, 2011, at 11:21 PM, Jon Zhu wrote:
> >
> > > Hi, Oleg
> > >
> > > Do we have a procedure on how to build v2.1 GA code on CentOS 5.6
> (xen)? On whamcloud wiki I can only find build v2.1 on RHEL 6.1 or build
> v1.8 on CentOS 5.6.
> > >
> > > BTW, congratulations on the 2.1 release!
> > >
> > > Regards,
> > >
> > > Jon Zhu
> > > Sent from Google Mail
> > >
> > >
> > >
> > >
> > > On Fri, Jun 24, 2011 at 2:43 PM, Oleg Drokin <green at
whamcloud.com>
> wrote:
> > > Hwllo~
> > >
> > > On Jun 23, 2011, at 9:51 PM, Jon Zhu wrote:
> > >
> > > > I still got some crash when further run some I/O test with
the build,
> here''s some system message containing call stack info maybe be
useful to you
> to find the bug:
> > >
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut
here
> ]------------
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at
> kernel/sched.c:7087 __cond_resched_lock+0x8e/0xb0() (Not tainted)
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in:
lustre(U)
> lov(U) osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U)
> obdclass(U) lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd
> aes_x86_64 aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront
ext4
> mbcache jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm:
> mount.lustre Not tainted 2.6.32.lustre21 #6
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81069c37>] ?
> warn_slowpath_common+0x87/0xc0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81007671>] ?
> __raw_callee_save_xen_save_fl+0x11/0x1e
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81069c8a>] ?
> warn_slowpath_null+0x1a/0x20
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff810654fe>] ?
> __cond_resched_lock+0x8e/0xb0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811a53b7>] ?
> shrink_dcache_for_umount_subtree+0x187/0x340
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811a55a6>] ?
> shrink_dcache_for_umount+0x36/0x60
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118f4ff>] ?
> generic_shutdown_super+0x1f/0xe0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118f5f1>] ?
> kill_block_super+0x31/0x50
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811906b5>] ?
> deactivate_super+0x85/0xa0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811ac5af>] ?
> mntput_no_expire+0xbf/0x110
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0273f8e>] ?
> unlock_mntput+0x3e/0x60 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0277a98>] ?
> server_kernel_mount+0x268/0xe80 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280d40>] ?
> lustre_fill_super+0x0/0x1290 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0279070>] ?
> lustre_init_lsi+0xd0/0x5b0 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff810ac71d>] ?
> lock_release+0xed/0x220
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280fd0>] ?
> lustre_fill_super+0x290/0x1290 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118ee20>] ?
> set_anon_super+0x0/0x110
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280d40>] ?
> lustre_fill_super+0x0/0x1290 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8119035f>] ?
> get_sb_nodev+0x5f/0xa0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0272885>] ?
> lustre_get_sb+0x25/0x30 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118ffbb>] ?
> vfs_kern_mount+0x7b/0x1b0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81190162>] ?
> do_kern_mount+0x52/0x130
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811ae647>] ?
> do_mount+0x2e7/0x870
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811aec60>] ?
> sys_mount+0x90/0xe0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8100b132>] ?
> system_call_fastpath+0x16/0x1b
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace
> a8fb737c71bfba13 ]---
> > >
> > > This is not a crash, it''s just a warning about
scheduling in
> inappropriate context I guess, but the kernel will continue to work.
> > > Interesting that I have never seen anything like that in rhel5
xen
> kernels, perhaps it''s something with rhel6.1 xen?
> > >
> > > Bye,
> > >    Oleg
> > > --
> > > Oleg Drokin
> > > Senior Software Engineer
> > > Whamcloud, Inc.
> > >
> > >
> >
> > --
> > Oleg Drokin
> > Senior Software Engineer
> > Whamcloud, Inc.
> >
> >
>
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20111002/a0c92222/attachment-0001.html

Hi, Oleg

Does Lustre 2.1 support Ubuntu client? From the following build map I can
see only ubuntu 10.04 client is supported but kernel needs to be patched.
Is there any plan to support patchless kernel client on Ubuntu? The new
Ubuntu Oneiric 11.10 release kernel 3.0 is being used, any plan to support
that in the near future?
http://build.whamcloud.com/job/lustre-b2_1/?

Thanks,
-Jon.
jon.zhu at gmail.com

On Sun, Oct 2, 2011 at 4:31 PM, Jon Zhu <jon.zhu at gmail.com> wrote:
> Thanks a lot, the work around works.
>
> -Jon.
>
>
>
>
> On Sun, Oct 2, 2011 at 3:47 PM, Oleg Drokin <green at whamcloud.com>
wrote:
>
>> Hello!
>>
>>    Last time I hit this (some years ago), a simple touch
>> ldiskfs/Module.symvers helped. I don''t remember what the issue
was or how
>> it was properly fixed, though.
>>
>> Bye,
>>     Oleg
>> On Oct 2, 2011, at 1:57 PM, Jon Zhu wrote:
>>
>> > Hi, Oleg
>> >
>> > I encountered the following error while building Lustre 2.1
release on
>> Redhat 2.1, do you have any idea on this error?
>> >
>> > make[1]: *** No rule to make target
>> `/build/lustre-release/ldiskfs/Module.symvers'', needed by
`Module.symvers''.
>>  Stop.
>> >
>> >
>> > Full build log :
>> > ....
>> > + /usr/lib/rpm/redhat/brp-java-repack-jars
>> > Processing files: lustre-iokit-1.2-201110021351.noarch
>> > Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.IOpHyP
>> > + umask 022
>> > + cd /build/kernel/rpmbuild/BUILD
>> > + cd lustre-iokit-1.2
>> > +
>>
DOCDIR=/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
>> > + export DOCDIR
>> > + rm -rf
>>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
>> > + /bin/mkdir -p
>>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
>> > + cp -pr obdfilter-survey/README.obdfilter-survey
>>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
>> > + cp -pr ior-survey/README.ior-survey
>>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
>> > + cp -pr ost-survey/README.ost-survey
>>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
>> > + cp -pr sgpdd-survey/README.sgpdd-survey
>>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
>> > + cp -pr
stats-collect/README.lstats.sh/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
>> > + exit 0
>> > Provides: lustre-iokit = 1.2
>> > Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1
>> rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <=
4.0-1
>> rpmlib(VersionedDependencies) <= 3.0.3-1
>> > Requires: /bin/bash /bin/sh /usr/bin/perl perl(File::Path)
>> perl(Getopt::Long) perl(Getopt::Std) perl(POSIX)
>> > Checking for unpackaged file(s): /usr/lib/rpm/check-files
>> /build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64
>> > Wrote:
>> /build/kernel/rpmbuild/SRPMS/lustre-iokit-1.2-201110021351.src.rpm
>> > Wrote:
>>
/build/kernel/rpmbuild/RPMS/noarch/lustre-iokit-1.2-201110021351.noarch.rpm
>> > Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.0eXePd
>> > + umask 022
>> > + cd /build/kernel/rpmbuild/BUILD
>> > + cd lustre-iokit-1.2
>> > + /bin/rm -rf
>> /build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64
>> > + exit 0
>> > make[1]: Leaving directory
`/build/lustre-release/lustre-iokit''
>> > Finished rpms in lustre-iokit
>> > make[1]: Entering directory `/build/lustre-release''
>> > make[1]: *** No rule to make target
>> `/build/lustre-release/ldiskfs/Module.symvers'', needed by
`Module.symvers''.
>>  Stop.
>> > make[1]: Leaving directory `/build/lustre-release''
>> > make: *** [rpms] Error 2
>> >
>> >
>> > Thanks,
>> > -Jon.
>> >
>> >
>> > On Thu, Sep 29, 2011 at 11:34 PM, Oleg Drokin <green at
whamcloud.com>
>> wrote:
>> > Hello!
>> >
>> >   There is nothing special, same as rhel6.1:
>> >   unpack the lustre source, run autogen.sh, run configure and
provide
>> the path to the linux kernel source for your distro (need to patch
first
>> too), make.
>> >
>> > Bye,
>> >    Oleg
>> > On Sep 29, 2011, at 11:21 PM, Jon Zhu wrote:
>> >
>> > > Hi, Oleg
>> > >
>> > > Do we have a procedure on how to build v2.1 GA code on CentOS
5.6
>> (xen)? On whamcloud wiki I can only find build v2.1 on RHEL 6.1 or
build
>> v1.8 on CentOS 5.6.
>> > >
>> > > BTW, congratulations on the 2.1 release!
>> > >
>> > > Regards,
>> > >
>> > > Jon Zhu
>> > > Sent from Google Mail
>> > >
>> > >
>> > >
>> > >
>> > > On Fri, Jun 24, 2011 at 2:43 PM, Oleg Drokin <green at
whamcloud.com>
>> wrote:
>> > > Hwllo~
>> > >
>> > > On Jun 23, 2011, at 9:51 PM, Jon Zhu wrote:
>> > >
>> > > > I still got some crash when further run some I/O test
with the
>> build, here''s some system message containing call stack info
maybe be
>> useful to you to find the bug:
>> > >
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[
cut here
>> ]------------
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at
>> kernel/sched.c:7087 __cond_resched_lock+0x8e/0xb0() (Not tainted)
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked
in:
>> lustre(U) lov(U) osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U)
>> ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U) ldiskfs(U)
sha256_generic
>> cryptd aes_x86_64 aes_generic cbc dm_crypt autofs4 ipv6 microcode
>> xen_netfront ext4 mbcache jbd2 xen_blkfront dm_mod [last unloaded:
>> scsi_wait_scan]
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421,
comm:
>> mount.lustre Not tainted 2.6.32.lustre21 #6
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81069c37>] ?
>> warn_slowpath_common+0x87/0xc0
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81007671>] ?
>> __raw_callee_save_xen_save_fl+0x11/0x1e
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81069c8a>] ?
>> warn_slowpath_null+0x1a/0x20
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff810654fe>] ?
>> __cond_resched_lock+0x8e/0xb0
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811a53b7>] ?
>> shrink_dcache_for_umount_subtree+0x187/0x340
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811a55a6>] ?
>> shrink_dcache_for_umount+0x36/0x60
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118f4ff>] ?
>> generic_shutdown_super+0x1f/0xe0
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118f5f1>] ?
>> kill_block_super+0x31/0x50
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811906b5>] ?
>> deactivate_super+0x85/0xa0
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811ac5af>] ?
>> mntput_no_expire+0xbf/0x110
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0273f8e>] ?
>> unlock_mntput+0x3e/0x60 [obdclass]
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0277a98>] ?
>> server_kernel_mount+0x268/0xe80 [obdclass]
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280d40>] ?
>> lustre_fill_super+0x0/0x1290 [obdclass]
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0279070>] ?
>> lustre_init_lsi+0xd0/0x5b0 [obdclass]
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff810ac71d>] ?
>> lock_release+0xed/0x220
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280fd0>] ?
>> lustre_fill_super+0x290/0x1290 [obdclass]
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118ee20>] ?
>> set_anon_super+0x0/0x110
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280d40>] ?
>> lustre_fill_super+0x0/0x1290 [obdclass]
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8119035f>] ?
>> get_sb_nodev+0x5f/0xa0
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0272885>] ?
>> lustre_get_sb+0x25/0x30 [obdclass]
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118ffbb>] ?
>> vfs_kern_mount+0x7b/0x1b0
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81190162>] ?
>> do_kern_mount+0x52/0x130
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811ae647>] ?
>> do_mount+0x2e7/0x870
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811aec60>] ?
>> sys_mount+0x90/0xe0
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8100b132>] ?
>> system_call_fastpath+0x16/0x1b
>> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace
>> a8fb737c71bfba13 ]---
>> > >
>> > > This is not a crash, it''s just a warning about
scheduling in
>> inappropriate context I guess, but the kernel will continue to work.
>> > > Interesting that I have never seen anything like that in
rhel5 xen
>> kernels, perhaps it''s something with rhel6.1 xen?
>> > >
>> > > Bye,
>> > >    Oleg
>> > > --
>> > > Oleg Drokin
>> > > Senior Software Engineer
>> > > Whamcloud, Inc.
>> > >
>> > >
>> >
>> > --
>> > Oleg Drokin
>> > Senior Software Engineer
>> > Whamcloud, Inc.
>> >
>> >
>>
>> --
>> Oleg Drokin
>> Senior Software Engineer
>> Whamcloud, Inc.
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20111129/6907b326/attachment.html

On 11-11-29 03:11 PM, Jon Zhu wrote:
> Hi, Oleg
I''m not Oleg but hopefully I can be of help.
> Does Lustre 2.1 support Ubuntu client?
It builds.  I''m not sure that any actual QA has been done on it though
as I believe it''s provided on an "as is" basis.
> From the following build map I can
> see only ubuntu 10.04 client is supported
Yes.  10.04 is LTS.
> but kernel needs to be patched.
No it doesn''t.  The build that you pointed at
http://build.whamcloud.com/job/lustre-b2_1/ is with an unpatched kernel.

b.

-- 
Brian J. Murrell
Senior Software Engineer
Whamcloud, Inc.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20111129/9f201733/attachment.bin

Thank you for the reply, Brian.

BTW, what does ofa and inkernel label at the build board actually mean?
http://build.whamcloud.com/job/lustre-b2_1/

Regards,
-Jon.

On Tue, Nov 29, 2011 at 3:20 PM, Brian J. Murrell <brian at
whamcloud.com>wrote:
> On 11-11-29 03:11 PM, Jon Zhu wrote:
> > Hi, Oleg
>
> I''m not Oleg but hopefully I can be of help.
>
> > Does Lustre 2.1 support Ubuntu client?
>
> It builds.  I''m not sure that any actual QA has been done on it
though
> as I believe it''s provided on an "as is" basis.
>
> > From the following build map I can
> > see only ubuntu 10.04 client is supported
>
> Yes.  10.04 is LTS.
>
> > but kernel needs to be patched.
>
> No it doesn''t.  The build that you pointed at
> http://build.whamcloud.com/job/lustre-b2_1/ is with an unpatched kernel.
>
> b.
>
> --
> Brian J. Murrell
> Senior Software Engineer
> Whamcloud, Inc.
>
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20111129/4e5ce42c/attachment-0001.html

On 11-11-29 03:48 PM, Jon Zhu wrote:
> Thank you for the reply, Brian.
NP.
> BTW, what does ofa and inkernel label at the build board actually mean?
     ofa == build with OFED I/B from OFA
inkernel == build with I/B in the upstream kernel

Cheers,
b.

-- 
Brian J. Murrell
Senior Software Engineer
Whamcloud, Inc.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20111129/527c7c56/attachment.bin

Cool. BTW, is it possible to rebuild the Lustre client driver from source,
just like what''s been described in following:
http://wiki.whamcloud.com/display/PUB/Rebuilding+the+Lustre-client+rpms+for+a+new+kernel
If that''s possible, where to grab the kernel source ****.src.deb?

Thanks again!

-Jon.

On Tue, Nov 29, 2011 at 3:49 PM, Brian J. Murrell <brian at
whamcloud.com>wrote:
> On 11-11-29 03:48 PM, Jon Zhu wrote:
> > Thank you for the reply, Brian.
>
> NP.
>
> > BTW, what does ofa and inkernel label at the build board actually
mean?
>
>      ofa == build with OFED I/B from OFA
> inkernel == build with I/B in the upstream kernel
>
> Cheers,
> b.
>
> --
> Brian J. Murrell
> Senior Software Engineer
> Whamcloud, Inc.
>
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20111129/fbd1591f/attachment.html

On 11-11-29 03:51 PM, Jon Zhu wrote:
> Cool. BTW, is it possible to rebuild the Lustre client driver from source,
Sure.
> just like what''s been described in following:
>
http://wiki.whamcloud.com/display/PUB/Rebuilding+the+Lustre-client+rpms+for+a+new+kernel
Well, not exactly.  RPM != DEB.
> If that''s possible, where to grab the kernel source ****.src.deb?
You don''t.  DEBs are packaged as source tarballs with a /debian
directory in them in which you typically do dpkg-buildpackage.  But that
assumes a clean separation of modules and userspace, which the lustre
source does not have, unfortunately.

So, to rebuild the DEB you grab the source tree (i.e. from git) or
tarball (and unpack it) and then run:

$ configure [arguemnts]
$ make debs

Cheers,
b.

-- 
Brian J. Murrell
Senior Software Engineer
Whamcloud, Inc.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20111129/0078febf/attachment.bin

Very cool, thanks a lot, Brian!

-Jon.


On Tue, Nov 29, 2011 at 4:05 PM, Brian J. Murrell <brian at
whamcloud.com>wrote:
> On 11-11-29 03:51 PM, Jon Zhu wrote:
> > Cool. BTW, is it possible to rebuild the Lustre client driver from
> source,
>
> Sure.
>
> > just like what''s been described in following:
> >
>
http://wiki.whamcloud.com/display/PUB/Rebuilding+the+Lustre-client+rpms+for+a+new+kernel
>
> Well, not exactly.  RPM != DEB.
>
> > If that''s possible, where to grab the kernel source
****.src.deb?
>
> You don''t.  DEBs are packaged as source tarballs with a /debian
> directory in them in which you typically do dpkg-buildpackage.  But that
> assumes a clean separation of modules and userspace, which the lustre
> source does not have, unfortunately.
>
> So, to rebuild the DEB you grab the source tree (i.e. from git) or
> tarball (and unpack it) and then run:
>
> $ configure [arguemnts]
> $ make debs
>
> Cheers,
> b.
>
> --
> Brian J. Murrell
> Senior Software Engineer
> Whamcloud, Inc.
>
>
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20111129/8552a9c3/attachment.html

On Tue, Nov 29, 2011 at 3:05 PM, Brian J. Murrell <brian at whamcloud.com>
wrote:
> On 11-11-29 03:51 PM, Jon Zhu wrote:
>> Cool. BTW, is it possible to rebuild the Lustre client driver from
source,
>
> Sure.
>
>> just like what''s been described in following:
>>
http://wiki.whamcloud.com/display/PUB/Rebuilding+the+Lustre-client+rpms+for+a+new+kernel
>
> Well, not exactly. ?RPM != DEB.
>
>> If that''s possible, where to grab the kernel source
****.src.deb?
>
> You don''t. ?DEBs are packaged as source tarballs with a /debian
> directory in them in which you typically do dpkg-buildpackage. ?But that
> assumes a clean separation of modules and userspace, which the lustre
> source does not have, unfortunately.
>
> So, to rebuild the DEB you grab the source tree (i.e. from git) or
> tarball (and unpack it) and then run:
>
> $ configure [arguemnts]
> $ make debs
>
There is an open bug (http://jira.whamcloud.com/browse/LU-788) that
means you may need to stick a

''make''

between ''configure'' and ''make debs''

It would be great if you could confirm to this list or the bug;
cheers,
Richard

-- 
Richard.Henwood at whamcloud.com
Whamcloud Inc.
tel: +1 512 410 9612

Thanks, Richard, I will give it a shot.

Regards,

-Jon.



On Nov 29, 2011, at 19:14, Richard Henwood <rhenwood at whamcloud.com>
wrote:
> On Tue, Nov 29, 2011 at 3:05 PM, Brian J. Murrell <brian at
whamcloud.com> wrote:
>> On 11-11-29 03:51 PM, Jon Zhu wrote:
>>> Cool. BTW, is it possible to rebuild the Lustre client driver from
source,
>> 
>> Sure.
>> 
>>> just like what''s been described in following:
>>>
http://wiki.whamcloud.com/display/PUB/Rebuilding+the+Lustre-client+rpms+for+a+new+kernel
>> 
>> Well, not exactly.  RPM != DEB.
>> 
>>> If that''s possible, where to grab the kernel source
****.src.deb?
>> 
>> You don''t.  DEBs are packaged as source tarballs with a
/debian
>> directory in them in which you typically do dpkg-buildpackage.  But
that
>> assumes a clean separation of modules and userspace, which the lustre
>> source does not have, unfortunately.
>> 
>> So, to rebuild the DEB you grab the source tree (i.e. from git) or
>> tarball (and unpack it) and then run:
>> 
>> $ configure [arguemnts]
>> $ make debs
>> 
> 
> There is an open bug (http://jira.whamcloud.com/browse/LU-788) that
> means you may need to stick a
> 
> ''make''
> 
> between ''configure'' and ''make debs''
> 
> It would be great if you could confirm to this list or the bug;
> cheers,
> Richard
> 
> -- 
> Richard.Henwood at whamcloud.com
> Whamcloud Inc.
> tel: +1 512 410 9612
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss

Yes I confirm Ubuntu 10.04 has the same issue, need to run make right after
configure, when building the Lustre 2.1 client package.

Thanks
-Jon.



On Tue, Nov 29, 2011 at 7:14 PM, Richard Henwood <rhenwood at
whamcloud.com>wrote:
> On Tue, Nov 29, 2011 at 3:05 PM, Brian J. Murrell <brian at
whamcloud.com>
> wrote:
> > On 11-11-29 03:51 PM, Jon Zhu wrote:
> >> Cool. BTW, is it possible to rebuild the Lustre client driver from
> source,
> >
> > Sure.
> >
> >> just like what''s been described in following:
> >>
>
http://wiki.whamcloud.com/display/PUB/Rebuilding+the+Lustre-client+rpms+for+a+new+kernel
> >
> > Well, not exactly.  RPM != DEB.
> >
> >> If that''s possible, where to grab the kernel source
****.src.deb?
> >
> > You don''t.  DEBs are packaged as source tarballs with a
/debian
> > directory in them in which you typically do dpkg-buildpackage.  But
that
> > assumes a clean separation of modules and userspace, which the lustre
> > source does not have, unfortunately.
> >
> > So, to rebuild the DEB you grab the source tree (i.e. from git) or
> > tarball (and unpack it) and then run:
> >
> > $ configure [arguemnts]
> > $ make debs
> >
>
> There is an open bug (http://jira.whamcloud.com/browse/LU-788) that
> means you may need to stick a
>
> ''make''
>
> between ''configure'' and ''make debs''
>
> It would be great if you could confirm to this list or the bug;
> cheers,
> Richard
>
> --
> Richard.Henwood at whamcloud.com
> Whamcloud Inc.
> tel: +1 512 410 9612
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20111130/8fda408d/attachment-0001.html

Hello!

   Yes, we do plan to have 3.x support. The 2.6.38 support is almost finished
and we will start looking at 3.x next.

Bye,
    Oleg
On Nov 29, 2011, at 3:11 PM, Jon Zhu wrote:
> Hi, Oleg
> 
> Does Lustre 2.1 support Ubuntu client? From the following build map I can
see only ubuntu 10.04 client is supported but kernel needs to be patched. Is
there any plan to support patchless kernel client on Ubuntu? The new Ubuntu
Oneiric 11.10 release kernel 3.0 is being used, any plan to support that in the
near future?
> http://build.whamcloud.com/job/lustre-b2_1/?
> 
> Thanks,
> -Jon.
> jon.zhu at gmail.com
> 
> On Sun, Oct 2, 2011 at 4:31 PM, Jon Zhu <jon.zhu at gmail.com> wrote:
> Thanks a lot, the work around works. 
> 
> -Jon.
> 
> 
> 
> 
> On Sun, Oct 2, 2011 at 3:47 PM, Oleg Drokin <green at whamcloud.com>
wrote:
> Hello!
> 
>    Last time I hit this (some years ago), a simple touch
ldiskfs/Module.symvers helped. I don''t remember what the issue was or
how it was properly fixed, though.
> 
> Bye,
>    Oleg
> On Oct 2, 2011, at 1:57 PM, Jon Zhu wrote:
> 
> > Hi, Oleg
> >
> > I encountered the following error while building Lustre 2.1 release on
Redhat 2.1, do you have any idea on this error?
> >
> > make[1]: *** No rule to make target
`/build/lustre-release/ldiskfs/Module.symvers'', needed by
`Module.symvers''.  Stop.
> >
> >
> > Full build log :
> > ....
> > + /usr/lib/rpm/redhat/brp-java-repack-jars
> > Processing files: lustre-iokit-1.2-201110021351.noarch
> > Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.IOpHyP
> > + umask 022
> > + cd /build/kernel/rpmbuild/BUILD
> > + cd lustre-iokit-1.2
> > +
DOCDIR=/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + export DOCDIR
> > + rm -rf
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + /bin/mkdir -p
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + cp -pr obdfilter-survey/README.obdfilter-survey
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + cp -pr ior-survey/README.ior-survey
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + cp -pr ost-survey/README.ost-survey
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + cp -pr sgpdd-survey/README.sgpdd-survey
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + cp -pr stats-collect/README.lstats.sh
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > + exit 0
> > Provides: lustre-iokit = 1.2
> > Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(VersionedDependencies) <= 3.0.3-1
> > Requires: /bin/bash /bin/sh /usr/bin/perl perl(File::Path)
perl(Getopt::Long) perl(Getopt::Std) perl(POSIX)
> > Checking for unpackaged file(s): /usr/lib/rpm/check-files
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64
> > Wrote:
/build/kernel/rpmbuild/SRPMS/lustre-iokit-1.2-201110021351.src.rpm
> > Wrote:
/build/kernel/rpmbuild/RPMS/noarch/lustre-iokit-1.2-201110021351.noarch.rpm
> > Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.0eXePd
> > + umask 022
> > + cd /build/kernel/rpmbuild/BUILD
> > + cd lustre-iokit-1.2
> > + /bin/rm -rf
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64
> > + exit 0
> > make[1]: Leaving directory
`/build/lustre-release/lustre-iokit''
> > Finished rpms in lustre-iokit
> > make[1]: Entering directory `/build/lustre-release''
> > make[1]: *** No rule to make target
`/build/lustre-release/ldiskfs/Module.symvers'', needed by
`Module.symvers''.  Stop.
> > make[1]: Leaving directory `/build/lustre-release''
> > make: *** [rpms] Error 2
> >
> >
> > Thanks,
> > -Jon.
> >
> >
> > On Thu, Sep 29, 2011 at 11:34 PM, Oleg Drokin <green at
whamcloud.com> wrote:
> > Hello!
> >
> >   There is nothing special, same as rhel6.1:
> >   unpack the lustre source, run autogen.sh, run configure and provide
the path to the linux kernel source for your distro (need to patch first too),
make.
> >
> > Bye,
> >    Oleg
> > On Sep 29, 2011, at 11:21 PM, Jon Zhu wrote:
> >
> > > Hi, Oleg
> > >
> > > Do we have a procedure on how to build v2.1 GA code on CentOS 5.6
(xen)? On whamcloud wiki I can only find build v2.1 on RHEL 6.1 or build v1.8 on
CentOS 5.6.
> > >
> > > BTW, congratulations on the 2.1 release!
> > >
> > > Regards,
> > >
> > > Jon Zhu
> > > Sent from Google Mail
> > >
> > >
> > >
> > >
> > > On Fri, Jun 24, 2011 at 2:43 PM, Oleg Drokin <green at
whamcloud.com> wrote:
> > > Hwllo~
> > >
> > > On Jun 23, 2011, at 9:51 PM, Jon Zhu wrote:
> > >
> > > > I still got some crash when further run some I/O test with
the build, here''s some system message containing call stack info maybe
be useful to you to find the bug:
> > >
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[ cut
here ]------------
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at
kernel/sched.c:7087 __cond_resched_lock+0x8e/0xb0() (Not tainted)
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked in:
lustre(U) lov(U) osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U) ptlrpc(U)
obdclass(U) lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic cryptd
aes_x86_64 aes_generic cbc dm_crypt autofs4 ipv6 microcode xen_netfront ext4
mbcache jbd2 xen_blkfront dm_mod [last unloaded: scsi_wait_scan]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421, comm:
mount.lustre Not tainted 2.6.32.lustre21 #6
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81069c37>] ? warn_slowpath_common+0x87/0xc0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81007671>] ? __raw_callee_save_xen_save_fl+0x11/0x1e
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81069c8a>] ? warn_slowpath_null+0x1a/0x20
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff810654fe>] ? __cond_resched_lock+0x8e/0xb0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811a53b7>] ? shrink_dcache_for_umount_subtree+0x187/0x340
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811a55a6>] ? shrink_dcache_for_umount+0x36/0x60
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118f4ff>] ? generic_shutdown_super+0x1f/0xe0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118f5f1>] ? kill_block_super+0x31/0x50
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811906b5>] ? deactivate_super+0x85/0xa0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811ac5af>] ? mntput_no_expire+0xbf/0x110
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0273f8e>] ? unlock_mntput+0x3e/0x60 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0277a98>] ? server_kernel_mount+0x268/0xe80 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280d40>] ? lustre_fill_super+0x0/0x1290 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0279070>] ? lustre_init_lsi+0xd0/0x5b0 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff810ac71d>] ? lock_release+0xed/0x220
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280fd0>] ? lustre_fill_super+0x290/0x1290 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118ee20>] ? set_anon_super+0x0/0x110
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280d40>] ? lustre_fill_super+0x0/0x1290 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8119035f>] ? get_sb_nodev+0x5f/0xa0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0272885>] ? lustre_get_sb+0x25/0x30 [obdclass]
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118ffbb>] ? vfs_kern_mount+0x7b/0x1b0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81190162>] ? do_kern_mount+0x52/0x130
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811ae647>] ? do_mount+0x2e7/0x870
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811aec60>] ? sys_mount+0x90/0xe0
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8100b132>] ? system_call_fastpath+0x16/0x1b
> > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace
a8fb737c71bfba13 ]---
> > >
> > > This is not a crash, it''s just a warning about
scheduling in inappropriate context I guess, but the kernel will continue to
work.
> > > Interesting that I have never seen anything like that in rhel5
xen kernels, perhaps it''s something with rhel6.1 xen?
> > >
> > > Bye,
> > >    Oleg
> > > --
> > > Oleg Drokin
> > > Senior Software Engineer
> > > Whamcloud, Inc.
> > >
> > >
> >
> > --
> > Oleg Drokin
> > Senior Software Engineer
> > Whamcloud, Inc.
> >
> >
> 
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
> 
> 
> 
--
Oleg Drokin
Senior Software Engineer
Whamcloud, Inc.

Hi, Oleg

I just rebuilt the SUSE Lustre 2.1 client under xen kernel environment, no
problem with the rebuild process, but I installed the package on the build
machine got the following errors:

 ip-10-32-62-48://usr/src/packages/RPMS/x86_64 # modprobe lnet
FATAL: Error inserting lnet
(/lib/modules/2.6.32.46-0.3-ec2/updates/kernel/net/lustre/lnet.ko): Invalid
module format
ip-10-32-62-48://usr/src/packages/RPMS/x86_64 # uname -a
Linux ip-10-32-62-48 2.6.32.46-0.3-ec2 #1 SMP 2011-09-29 17:49:31 +0200
x86_64 x86_64 x86_64 GNU/Linux
ip-10-32-62-48://usr/src/packages/RPMS/x86_64 # modinfo
/lib/modules/2.6.32.46-0.3-ec2/updates/kernel/net/lustre/lnet.ko
filename:
/lib/modules/2.6.32.46-0.3-ec2/updates/kernel/net/lustre/lnet.ko
license:        GPL
description:    Portals v3.1
author:         Peter J. Braam <braam at clusterfs.com>
srcversion:     D64519A3761B3BB8EDF41F1
depends:        libcfs
vermagic:       2.6.32.46-0.3-ec2 SMP mod_unload modversions Xen
parm:           accept:Accept connections (secure|all|none) (charp)
parm:           accept_port:Acceptor''s port (same on all nodes) (int)
parm:           accept_backlog:Acceptor''s listen backlog (int)
parm:           accept_timeout:Acceptor''s timeout (seconds) (int)
parm:           forwarding:Explicitly enable/disable forwarding between
networks (charp)
parm:           tiny_router_buffers:# of 0 payload messages to buffer in
the router (int)
parm:           small_router_buffers:# of small (1 page) messages to buffer
in the router (int)
parm:           large_router_buffers:# of large messages to buffer in the
router (int)
parm:           peer_buffer_credits:# router buffer credits per peer (int)
parm:           auto_down:Automatically mark peers down on comms error (int)
parm:           check_routers_before_use:Assume routers are down and ping
them before use (int)
parm:           avoid_asym_router_failure:Avoid asymmetrical failures:
reserved, use at your own risk (int)
parm:           dead_router_check_interval:Seconds between dead router
health checks (<= 0 to disable) (int)
parm:           live_router_check_interval:Seconds between live router
health checks (<= 0 to disable) (int)
parm:           router_ping_timeout:Seconds to wait for the reply to a
router health query (int)
parm:           config_on_load:configure network at module load (int)
parm:           local_nid_dist_zero:Reserved (int)
parm:           ip2nets:LNET network <- IP table (charp)
parm:           networks:local networks (charp)
parm:           routes:routes to non-local networks (charp)

Any idea on this? I do see some error message in system log as well:
Dec 17 01:51:41 ip-10-32-62-48 kernel: [ 3744.865201] libcfs: no symbol
version for module_layout

Thanks,
-Jon.


On Wed, Dec 7, 2011 at 1:24 AM, Oleg Drokin <green at whamcloud.com>
wrote:
> Hello!
>
>   Yes, we do plan to have 3.x support. The 2.6.38 support is almost
> finished and we will start looking at 3.x next.
>
> Bye,
>    Oleg
> On Nov 29, 2011, at 3:11 PM, Jon Zhu wrote:
>
> > Hi, Oleg
> >
> > Does Lustre 2.1 support Ubuntu client? From the following build map I
> can see only ubuntu 10.04 client is supported but kernel needs to be
> patched. Is there any plan to support patchless kernel client on Ubuntu?
> The new Ubuntu Oneiric 11.10 release kernel 3.0 is being used, any plan to
> support that in the near future?
> > http://build.whamcloud.com/job/lustre-b2_1/?
> >
> > Thanks,
> > -Jon.
> > jon.zhu at gmail.com
> >
> > On Sun, Oct 2, 2011 at 4:31 PM, Jon Zhu <jon.zhu at gmail.com>
wrote:
> > Thanks a lot, the work around works.
> >
> > -Jon.
> >
> >
> >
> >
> > On Sun, Oct 2, 2011 at 3:47 PM, Oleg Drokin <green at
whamcloud.com> wrote:
> > Hello!
> >
> >    Last time I hit this (some years ago), a simple touch
> ldiskfs/Module.symvers helped. I don''t remember what the issue was
or how
> it was properly fixed, though.
> >
> > Bye,
> >    Oleg
> > On Oct 2, 2011, at 1:57 PM, Jon Zhu wrote:
> >
> > > Hi, Oleg
> > >
> > > I encountered the following error while building Lustre 2.1
release on
> Redhat 2.1, do you have any idea on this error?
> > >
> > > make[1]: *** No rule to make target
> `/build/lustre-release/ldiskfs/Module.symvers'', needed by
`Module.symvers''.
>  Stop.
> > >
> > >
> > > Full build log :
> > > ....
> > > + /usr/lib/rpm/redhat/brp-java-repack-jars
> > > Processing files: lustre-iokit-1.2-201110021351.noarch
> > > Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.IOpHyP
> > > + umask 022
> > > + cd /build/kernel/rpmbuild/BUILD
> > > + cd lustre-iokit-1.2
> > > +
>
DOCDIR=/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > > + export DOCDIR
> > > + rm -rf
>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > > + /bin/mkdir -p
>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > > + cp -pr obdfilter-survey/README.obdfilter-survey
>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > > + cp -pr ior-survey/README.ior-survey
>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > > + cp -pr ost-survey/README.ost-survey
>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > > + cp -pr sgpdd-survey/README.sgpdd-survey
>
/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > > + cp -pr
stats-collect/README.lstats.sh/build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64/usr/share/doc/lustre-iokit-1.2
> > > + exit 0
> > > Provides: lustre-iokit = 1.2
> > > Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1
> rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <=
4.0-1
> rpmlib(VersionedDependencies) <= 3.0.3-1
> > > Requires: /bin/bash /bin/sh /usr/bin/perl perl(File::Path)
> perl(Getopt::Long) perl(Getopt::Std) perl(POSIX)
> > > Checking for unpackaged file(s): /usr/lib/rpm/check-files
> /build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64
> > > Wrote:
> /build/kernel/rpmbuild/SRPMS/lustre-iokit-1.2-201110021351.src.rpm
> > > Wrote:
> /build/kernel/rpmbuild/RPMS/noarch/lustre-iokit-1.2-201110021351.noarch.rpm
> > > Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.0eXePd
> > > + umask 022
> > > + cd /build/kernel/rpmbuild/BUILD
> > > + cd lustre-iokit-1.2
> > > + /bin/rm -rf
> /build/kernel/rpmbuild/BUILDROOT/lustre-iokit-1.2-201110021351.x86_64
> > > + exit 0
> > > make[1]: Leaving directory
`/build/lustre-release/lustre-iokit''
> > > Finished rpms in lustre-iokit
> > > make[1]: Entering directory `/build/lustre-release''
> > > make[1]: *** No rule to make target
> `/build/lustre-release/ldiskfs/Module.symvers'', needed by
`Module.symvers''.
>  Stop.
> > > make[1]: Leaving directory `/build/lustre-release''
> > > make: *** [rpms] Error 2
> > >
> > >
> > > Thanks,
> > > -Jon.
> > >
> > >
> > > On Thu, Sep 29, 2011 at 11:34 PM, Oleg Drokin <green at
whamcloud.com>
> wrote:
> > > Hello!
> > >
> > >   There is nothing special, same as rhel6.1:
> > >   unpack the lustre source, run autogen.sh, run configure and
provide
> the path to the linux kernel source for your distro (need to patch first
> too), make.
> > >
> > > Bye,
> > >    Oleg
> > > On Sep 29, 2011, at 11:21 PM, Jon Zhu wrote:
> > >
> > > > Hi, Oleg
> > > >
> > > > Do we have a procedure on how to build v2.1 GA code on
CentOS 5.6
> (xen)? On whamcloud wiki I can only find build v2.1 on RHEL 6.1 or build
> v1.8 on CentOS 5.6.
> > > >
> > > > BTW, congratulations on the 2.1 release!
> > > >
> > > > Regards,
> > > >
> > > > Jon Zhu
> > > > Sent from Google Mail
> > > >
> > > >
> > > >
> > > >
> > > > On Fri, Jun 24, 2011 at 2:43 PM, Oleg Drokin <green at
whamcloud.com>
> wrote:
> > > > Hwllo~
> > > >
> > > > On Jun 23, 2011, at 9:51 PM, Jon Zhu wrote:
> > > >
> > > > > I still got some crash when further run some I/O test
with the
> build, here''s some system message containing call stack info maybe
be
> useful to you to find the bug:
> > > >
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: ------------[
cut here
> ]------------
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: WARNING: at
> kernel/sched.c:7087 __cond_resched_lock+0x8e/0xb0() (Not tainted)
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Modules linked
in:
> lustre(U) lov(U) osc(U) lquota(U) mdc(U) fid(U) fld(U) ksocklnd(U)
> ptlrpc(U) obdclass(U) lnet(U) lvfs(U) libcfs(U) ldiskfs(U) sha256_generic
> cryptd aes_x86_64 aes_generic cbc dm_crypt autofs4 ipv6 microcode
> xen_netfront ext4 mbcache jbd2 xen_blkfront dm_mod [last unloaded:
> scsi_wait_scan]
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Pid: 1421,
comm:
> mount.lustre Not tainted 2.6.32.lustre21 #6
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: Call Trace:
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81069c37>] ?
> warn_slowpath_common+0x87/0xc0
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81007671>] ?
> __raw_callee_save_xen_save_fl+0x11/0x1e
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81069c8a>] ?
> warn_slowpath_null+0x1a/0x20
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff810654fe>] ?
> __cond_resched_lock+0x8e/0xb0
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811a53b7>] ?
> shrink_dcache_for_umount_subtree+0x187/0x340
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811a55a6>] ?
> shrink_dcache_for_umount+0x36/0x60
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118f4ff>] ?
> generic_shutdown_super+0x1f/0xe0
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118f5f1>] ?
> kill_block_super+0x31/0x50
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811906b5>] ?
> deactivate_super+0x85/0xa0
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811ac5af>] ?
> mntput_no_expire+0xbf/0x110
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0273f8e>] ?
> unlock_mntput+0x3e/0x60 [obdclass]
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0277a98>] ?
> server_kernel_mount+0x268/0xe80 [obdclass]
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280d40>] ?
> lustre_fill_super+0x0/0x1290 [obdclass]
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0279070>] ?
> lustre_init_lsi+0xd0/0x5b0 [obdclass]
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff810ac71d>] ?
> lock_release+0xed/0x220
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280fd0>] ?
> lustre_fill_super+0x290/0x1290 [obdclass]
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118ee20>] ?
> set_anon_super+0x0/0x110
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0280d40>] ?
> lustre_fill_super+0x0/0x1290 [obdclass]
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8119035f>] ?
> get_sb_nodev+0x5f/0xa0
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffffa0272885>] ?
> lustre_get_sb+0x25/0x30 [obdclass]
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8118ffbb>] ?
> vfs_kern_mount+0x7b/0x1b0
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff81190162>] ?
> do_kern_mount+0x52/0x130
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811ae647>] ?
> do_mount+0x2e7/0x870
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff811aec60>] ?
> sys_mount+0x90/0xe0
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel:
[<ffffffff8100b132>] ?
> system_call_fastpath+0x16/0x1b
> > > > > Jun 23 21:46:12 ip-10-112-59-173 kernel: ---[ end trace
> a8fb737c71bfba13 ]---
> > > >
> > > > This is not a crash, it''s just a warning about
scheduling in
> inappropriate context I guess, but the kernel will continue to work.
> > > > Interesting that I have never seen anything like that in
rhel5 xen
> kernels, perhaps it''s something with rhel6.1 xen?
> > > >
> > > > Bye,
> > > >    Oleg
> > > > --
> > > > Oleg Drokin
> > > > Senior Software Engineer
> > > > Whamcloud, Inc.
> > > >
> > > >
> > >
> > > --
> > > Oleg Drokin
> > > Senior Software Engineer
> > > Whamcloud, Inc.
> > >
> > >
> >
> > --
> > Oleg Drokin
> > Senior Software Engineer
> > Whamcloud, Inc.
> >
> >
> >
>
> --
> Oleg Drokin
> Senior Software Engineer
> Whamcloud, Inc.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20111216/64569268/attachment-0001.html