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-4354 Lustre <p>Clients are unable to mount an ldiskfs filesystem upgraded from 2.1 to 2.4.</p> <p>Transcribed client messages:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>mgc_request.c:247 do_config_log_add() failed processing sptlrpc log: -2 genops.c:304 class_newdev() ls4-OST0000-osc-... alread exists, won't add obd_config.c:368:class_attach() Cannot create defvice ls4-OST000... of type osc: -17 obd_config.c:1491:class_config_llog_handler() Err -17 on cfg command: cmd=cf001 0:ls4-OST0000... 1:osc 2:ls4-clilov_UUID LustreError: The configuration from log 'ls4-client' failed (-17). ... </pre> </div></div> LU-4354

2.1 clients fail to mount upgraded 2.4 filesystem with EEXIST

Bug Critical Resolved Not a Bug Cliff White Ned Bass Thu, 5 Dec 2013 23:18:45 +0000 Mon, 20 Jan 2014 18:09:16 +0000 Mon, 20 Jan 2014 18:09:16 +0000 0 3 <p>On MGS we get in debug log when client tries to mount:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>MGS fail to handle opc = 501: rc = -2 </pre> </div></div> <p>Can you attach the debug log? </p> <p>This may have been related to an incomplete writeconf procedure. Admins are repeating the procedure now.</p> <p>Sorry Cliff the system is classified.</p> <p>Had a feeling you would say that. I would indeed repeat the writeconf, if there are still issues I would directly examine the ls4-client config log with llog_reader and see what is in there. The writeconf is likely the correct answer.</p> <p>I am curious, why would a writeconf is needed? Unless you need to change the NIDS, or backup/restore.</p> <p>Minh, we did a writeconf because these are upgraded 1.8 filesystems, and we were advised that a writeconf is needed before going to 2.4. Otherwise clients would not initialize the lmv layer which is needed after DNE landed.</p> <p>Did the writeconf fix this issue? </p> <p>Cliff, yes the filesystem is back online after a writeconf. So I guess there is not a bug here, other than poor error reporting.</p> <p>I am closing this issue as a non bug. Please reopen if you have further questions/issues</p> Development Rank 1|hzwat3: Rank (Obsolete) 11926 Severity