https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-4981 Lustre <p>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.</p> <p><span class="error">&#91;18:14:13&#93;</span> John Hammond: I'm a bit concerned that sanity 133g may be having/exposing some subtle effects on sanity.<br/> <span class="error">&#91;18:14:53&#93;</span> John Hammond: I see weird messages that the current identity upcall is '^E'.<br/> <span class="error">&#91;18:15:33&#93;</span> John Hammond: Just FYI. I'll probably create an issue here soon.<br/> <span class="error">&#91;18:16:41&#93;</span> Oleg Drokin: ah… I very well can believe that. Luckily, we do not use identity-upcall in our testing I think<br/> <span class="error">&#91;18:16:56&#93;</span> John Hammond: We do use it.<br/> <span class="error">&#91;18:18:07&#93;</span> Oleg Drokin: do we? interesting<br/> <span class="error">&#91;18:18:37&#93;</span> Oleg Drokin: sigh, need to make it the very last test then?<br/> <span class="error">&#91;18:18:40&#93;</span> John Hammond: If the mdt.*.identity_upcall is set to something other than NONE then we use that.<br/> <span class="error">&#91;18:19:43&#93;</span> John Hammond: I see mdt_identity_do_upcall() being executed several times in a sanity run.<br/> <span class="error">&#91;18:20:13&#93;</span> Oleg Drokin: hopefully mostly before test 133<br/> <span class="error">&#91;18:20:29&#93;</span> Oleg Drokin: but there were some other side effects like disabling changelog masks and such<br/> <span class="error">&#91;18:20:37&#93;</span> Oleg Drokin: so it does make sense to move the test to be the very last one<br/> <span class="error">&#91;18:22:13&#93;</span> John Hammond: Or unmount and remount after it.</p> LU-4981

need to remount after sanity 133g

Bug Critical Resolved Fixed Bobbie Lind John Hammond procfs tests Tue, 29 Apr 2014 23:24:41 +0000 Thu, 8 May 2014 13:29:01 +0000 Thu, 8 May 2014 13:29:01 +0000 Lustre 2.6.0 Lustre 2.6.0 0 5 <p><span class="error">&#91;18:40:05&#93;</span> Oleg Drokin: does that actually reset all proc vars if we don't do full module unload, though?<br/> <span class="error">&#91;18:42:09&#93;</span> John Hammond: No not all.<br/> <span class="error">&#91;18:44:00&#93;</span> Oleg Drokin: so we need to go through the entire unmount and remount. just easier to move it to the end?<br/> <span class="error">&#91;18:44:56&#93;</span> John Hammond: Sure, except for when we have two tests that each need to be the last one...<br/> <span class="error">&#91;18:45:27&#93;</span> Oleg Drokin: true, I guess. so full unmount and reload of modules test 65j style then?<br/> <span class="error">&#91;18:50:20&#93;</span> John Hammond: Indeed.</p> <p>Maybe we should kill this part:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre> rc = write(fd, &amp;fd, 1); if (rc != 1) perror("write one byte"); </pre> </div></div> <p>This explains why the identity_upcall was being set to "^E" == "\005".</p> <p>I think 1 byte write is important since there are certain pieces in the code that might not handle that properly</p> <p>Bobbie,<br/> Could you please take this one?<br/> Thank you!</p> <p><a href="http://review.whamcloud.com/10174" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/10174</a> Since this will block me landing 9511, I will just push a patch here. </p> <p>Patch landed to Master. please reopen ticket if more work is needed</p> Related LU-4930 Development Rank 1|hzwlgn: Rank (Obsolete) 13801 Severity