[LU-4981] need to remount after sanity 133g Created: 29/Apr/14 Updated: 08/May/14 Resolved: 08/May/14 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.6.0 |
| Fix Version/s: | Lustre 2.6.0 |
| Type: | Bug | Priority: | Critical |
| Reporter: | John Hammond | Assignee: | Bobbie Lind (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | procfs, tests | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 13801 | ||||||||
| Description |
|
Sanity 133g tries to write garbage to every file in /proc/fs/lustre,... As you can imagine, this may affect the other tests in subtle ways. [18:14:13] John Hammond: I'm a bit concerned that sanity 133g may be having/exposing some subtle effects on sanity. |
| Comments |
| Comment by John Hammond [ 30/Apr/14 ] |
|
[18:40:05] Oleg Drokin: does that actually reset all proc vars if we don't do full module unload, though? |
| Comment by John Hammond [ 30/Apr/14 ] |
|
Maybe we should kill this part: rc = write(fd, &fd, 1);
if (rc != 1)
perror("write one byte");
This explains why the identity_upcall was being set to "^E" == "\005". |
| Comment by Oleg Drokin [ 30/Apr/14 ] |
|
I think 1 byte write is important since there are certain pieces in the code that might not handle that properly |
| Comment by Jodi Levi (Inactive) [ 30/Apr/14 ] |
|
Bobbie, |
| Comment by Di Wang [ 30/Apr/14 ] |
|
http://review.whamcloud.com/10174 Since this will block me landing 9511, I will just push a patch here. |
| Comment by Jodi Levi (Inactive) [ 08/May/14 ] |
|
Patch landed to Master. please reopen ticket if more work is needed |