From 8e0b8228d650477b66c665b5bde066c396b94ffa Mon Sep 17 00:00:00 2001 From: rread Date: Fri, 13 Feb 2004 06:43:13 +0000 Subject: [PATCH] b=2712 If mount is unable to connect to the config device to get the profile, then it fails right away and doesn't try to recover. (It will still attempt recovery on the initial connect for the actual devices in the config, though.) If we need to revert this behavior for some reason, all that is needed is to change the 0 back to 1 in the call to lustre_process_log in lustre_fill_super. Fixed the ptlrpc_connect_interpret to also invalidate the import when we are not recoverying an initial connect. Changed the test I just added to jive with this new behavior, and also added another test suggested by Jacob. --- lustre/llite/llite_lib.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lustre/llite/llite_lib.c b/lustre/llite/llite_lib.c index af7cbb7..49ddb12 100644 --- a/lustre/llite/llite_lib.c +++ b/lustre/llite/llite_lib.c @@ -542,7 +542,7 @@ int lustre_fill_super(struct super_block *sb, void *data, int silent) cfg.cfg_instance = sbi->ll_instance; cfg.cfg_uuid = sbi->ll_sb_uuid; cfg.cfg_local_nid = lmd->lmd_local_nid; - err = lustre_process_log(lmd, lmd->lmd_profile, &cfg, 1); + err = lustre_process_log(lmd, lmd->lmd_profile, &cfg, 0); if (err < 0) { CERROR("Unable to process log: %s\n", lmd->lmd_profile); -- 1.8.3.1