[LU-4536] sanity test_65ic

• Type: Bug
• Resolution: Fixed
• Priority: Major
• Fix Version/s: Lustre 2.11.0
• Affects Version/s: Lustre 2.7.0
• Labels: HB zfs
• Severity: 3
• Assignee: Nathaniel Clark
• Reporter: Maloo

Description

This issue was created by maloo for Nathaniel Clark <[e-mail]>

This issue relates to the following test suite run:
http://maloo.whamcloud.com/test_sets/c57a95dc-7c91-11e3-b3fa-52540035b04c
https://maloo.whamcloud.com/test_sets/f73662fc-83f0-11e3-bab5-52540035b04c

The sub-test test_65ic failed with the following error:

test failed to respond and timed out

Info required for matching: sanity 65ic

Issue Links

• is related to: LU-5415 High ldlm_poold load on client
• is related to: LU-2524 Tests regressions: tests interrelation introduced.
• is related to: LU-9019 Migrate lustre to standard 64 bit time kernel API

Comments

[James A Simmons]

Patch has landed and the time 64 work fixed the problems.

[Gerrit Updater]

Oleg Drokin ([e-mail]) merged in patch https://review.whamcloud.com/27803/
Subject: LU-4536 tests: Re-enable sanity/65ic
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 10f7f715e23c75b76c9af38c815311e92dc0ef81

[Gerrit Updater]

Nathaniel Clark ([e-mail]) uploaded a new patch: https://review.whamcloud.com/27803
Subject: LU-4536 tests: Re-enable sanity/65ic
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: d7b2f7547eb7fcd4e276baf223b9ca61babe1d94

[James A Simmons]

This Ben thinks this might be a 64 bit timer issues I linked it to LU-9019.

[Andreas Dilger]

This hasn't been seen because the test is currently always being skipped.

[Peter Jones]

Has not been seen in many months

[James A Simmons]

Hm. Looks like I need to push a patch for cleanup the time wrappers.

[Ben Evans (Inactive)]

Just ran into this (or something quite similar) on a 2.5.2 build

I think the ldlm_pool_recalc may help, but I also noticed that internally ldlm_pool_recalc is working with time_t, and returns an int. I'm wondering if there are 32/64 bit issues here. In my case, I know time_t is 64 bit, and int is 32 bit.

[Gerrit Updater]

Nathaniel Clark ([e-mail]) uploaded a new patch: http://review.whamcloud.com/13512
Subject: LU-4536 tests: Add debugging to sanity/65ic
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: d2c638d2e7edaca81699249f35b6b2567a47dd7d

[Oleg Drokin]

so if you run with increased debugging where you can trace by rpc xid to see what happened with that request? could it bemds replied and client missed it? unplausible, but a start to see what's going on.