[LU-3511] sanity test 154a: probably issues Created: 26/Jun/13 Updated: 10/Jul/13 Resolved: 10/Jul/13 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.5.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Alexey Lyashkov | Assignee: | WC Triage |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
RHEL6 |
||
| Severity: | 3 |
| Rank (Obsolete): | 8835 |
| Description |
|
i not sure about access by name in .fid directory == sanity test 154a: Open-by-FID == 16:27:40 (1372253260) stat fid [0x200002341:0x6:0x0] touch fid [0x200002341:0x6:0x0] write to fid [0x200002341:0x6:0x0] read fid [0x200002341:0x6:0x0] append write to fid [0x200002341:0x6:0x0] rename fid [0x200002341:0x6:0x0] mv: cannot move `/mnt/lustre/.lustre/fid/[0x200002341:0x6:0x0]' to `/mnt/lustre/f.sanity.154a.1': Operation not permitted mv: cannot move `/mnt/lustre/f.sanity.154a.1' to `/mnt/lustre/.lustre/fid/[0x200002341:0x6:0x0]': Operation not permitted truncate fid [0x200002341:0x6:0x0] link fid [0x200002341:0x6:0x0] setfacl fid [0x200002341:0x6:0x0] getfacl fid [0x200002341:0x6:0x0] getfacl: Removing leading '/' from absolute path names unlink fid [0x200002341:0x6:0x0] unlink: cannot unlink `/mnt/lustre/.lustre/fid/[0x200002341:0x6:0x0]': Operation not permitted mknod fid [0x200002341:0x6:0x0] mknod: `/mnt/lustre/.lustre/fid/[0x200002341:0x6:0x0]': Operation not permitted stat non-exist fid [0xf00000400:0x1:0x0] stat: cannot stat `/mnt/lustre/.lustre/fid/[0xf00000400:0x1:0x0]': Input/output error write to non-exist fid [0xf00000400:0x1:0x0] sanity.sh: line 8757: /mnt/lustre/.lustre/fid/[0xf00000400:0x1:0x0]: Input/output error link new fid [0xf00000400:0x1:0x0] ln: accessing `/mnt/lustre/.lustre/fid/[0xf00000400:0x1:0x0]': Input/output error ls [0x200002341:0xe:0x0] touch [0x200002341:0xe:0x0]/f.sanity.154a.1 touch /mnt/lustre/.lustre/fid/f.sanity.154a touch: setting times of `/mnt/lustre/.lustre/fid/f.sanity.154a': Invalid argument setxattr to /mnt/lustre/.lustre/fid listxattr for /mnt/lustre/.lustre/fid getfattr: Removing leading '/' from absolute path names # file: mnt/lustre/.lustre/fid trusted.lma=0sAAAAAAAAAAACAAAAAgAAAAIAAAAAAAAA trusted.name1="value1" delxattr from /mnt/lustre/.lustre/fid touch invalid fid: /mnt/lustre/.lustre/fid/[0x200000400:0x2:0x3] touch: setting times of `/mnt/lustre/.lustre/fid/[0x200000400:0x2:0x3]': Invalid argument touch non-normal fid: /mnt/lustre/.lustre/fid/[0x1:0x2:0x0] touch: setting times of `/mnt/lustre/.lustre/fid/[0x1:0x2:0x0]': Invalid argument rename d0.sanity/d154 to /mnt/lustre/.lustre/fid rename returned -1: Operation not permitted change mode of /mnt/lustre/.lustre/fid to 777 restore mode of /mnt/lustre/.lustre/fid to 100 Succeed in opening file "/mnt/lustre/f.sanity.154a-2"(flags=O_LOV_DELAY_CREATE) cp /etc/passwd /mnt/lustre/.lustre/fid/[0x200002341:0x14:0x0] cp: cannot create regular file `/mnt/lustre/.lustre/fid/[0x200002341:0x14:0x0]': Operation not permitted cp /etc/passwd /mnt/lustre/f.sanity.154a-2 diff /etc/passwd /mnt/lustre/.lustre/fid/[0x200002341:0x14:0x0] rm: cannot remove `/mnt/lustre/.lustre/fid': Operation not permitted touch: setting times of `/mnt/lustre/.lustre/file': No such file or directory mkdir: cannot create directory `/mnt/lustre/.lustre/dir': Operation not permitted Resetting fail_loc on all nodes...done. PASS 154a (1s) == sanity test |
| Comments |
| Comment by John Hammond [ 26/Jun/13 ] |
|
Probably so. But could you be more specific about where? |
| Comment by Alexey Lyashkov [ 26/Jun/13 ] |
|
John, that is just run from lustre checkout directory where developing new patch for LU-3276. |
| Comment by John Hammond [ 26/Jun/13 ] |
|
Yes but the test passed and to me the output looks correct for a pass. Do you suspect issues because of the error messages or because of some other aspect? Note that many of the operations performed above are not intended to succeed but are performed just to torture the special case code backing .lustre/fid. Several of them caused LBUGs or oopses in the past. It it distracting to have the errors printed. Probably we should redirect stderr to /dev/null for the operations we expect to fail. |
| Comment by Alexey Lyashkov [ 26/Jun/13 ] |
|
I worry about "touch /mnt/lustre/.lustre/fid/f.sanity.154a" |
| Comment by John Hammond [ 26/Jun/13 ] |
|
No, that's intentional. From the test: echo "touch $MOUNT/.lustre/fid/$tfile"
touch $MOUNT/.lustre/fid/$tfile && \
error "touch $MOUNT/.lustre/fid/$tfile should fail."
|
| Comment by John Hammond [ 10/Jul/13 ] |
|
Alexey, based on the discussion I'm closing this as not a bug, please reopen or comment here if you disagree. |