[LU-3603] posix test_1: path tracing error: path counter 1, expected 3 Created: 17/Jul/13 Updated: 08/Nov/13 Resolved: 08/Nov/13 |
|
| Status: | Closed |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.4.1, Lustre 2.5.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Maloo | Assignee: | Sarah Liu |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | zfs | ||
| Environment: |
lustre-master build #1560 |
||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9146 | ||||||||
| Description |
|
This issue was created by maloo for sarah <sarah@whamcloud.com> This issue relates to the following test suite run: http://maloo.whamcloud.com/test_sets/75c8bd20-ed44-11e2-99b4-52540035b04c. The sub-test test_1 failed with the following error:
path tracing error: path counter 1, expected 3 |
| Comments |
| Comment by Sarah Liu [ 22/Oct/13 ] |
|
hit this error in lustre-b2_5 zfs testing |
| Comment by Andreas Dilger [ 22/Oct/13 ] |
|
It looks like ZFS* is somehow reporting that NAME_MAX IS 256 but it only accepts filenames of 255 bytes. This confuses POSIX. Probably the easiest thing is to change osd-zfs to return a max filename size of 255 to match ldiskfs. [*] pathconf() results might be generated inside glibc instead of the filesystem, which is annoying and needs a patch to glibc to fix. |
| Comment by Jian Yu [ 05/Nov/13 ] |
|
Lustre build: http://build.whamcloud.com/job/lustre-b2_4/49/ posix test results: |
| Comment by Jian Yu [ 08/Nov/13 ] |
|
The patch for |