[LU-10991] unable to import pools : Upgrading 2.10.3 to 2.11.51 Created: 02/May/18  Updated: 19/Dec/18  Resolved: 23/Oct/18

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.12.0
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Saurabh Tandan (Inactive) Assignee: Nathaniel Clark
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

Older version: 2.10.3
New version: 2.11.51
ZFS
2 clients, 1 OSS with 2 OSTs, 1 MDS with 1 MDT


Issue Links:
Related
is related to LU-10998 Add 2.10.0 zfs and ldiskfs images for... Resolved
Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

Unable to import pools when upgrading OSS from 2.10.3 to 2.11.51.

Steps:

All clients and servers set up with 2.10.3 lustre version.

2.10.3 ZFS version: zfs-0.7.5-1.el7

2.11.51 ZFS version: zfs-0.7.8-1.el7

Upgraded OSS to 2.11.51 and tried to import pools but getting the following:

[root@onyx-70 ~]# modprobe zfs

zpool import lustre-ost2[ 5805.811988] spl: loading out-of-tree module taints kernel.

[ 5805.818394] spl: module verification failed: signature and/or required key missing - tainting kernel

[ 5805.834983] SPL: Loaded module v0.7.8-1

[ 5805.839599] znvpair: module license 'CDDL' taints kernel.

[ 5805.845676] Disabling lock debugging due to kernel taint

[ 5807.838597] ZFS: Loaded module v0.7.8-1, ZFS pool version 5000, ZFS filesystem version 5

[root@onyx-70 ~]# 

[root@onyx-70 ~]# zpool import lustre-ost1

cannot import 'lustre-ost1': no such pool available

[root@onyx-70 ~]# zpool import lustre-ost2

cannot import 'lustre-ost2': no such pool available

[root@onyx-70 ~]# zpool list

no pools available



 Comments   
Comment by Andreas Dilger [ 02/May/18 ]

Please also create new test images for conf-sanity test_32. 

Comment by James Nunez (Inactive) [ 04/May/18 ]

LU-10998 is tracking creating new images for conf-sanity test 32.

Comment by Andreas Dilger [ 05/May/18 ]

Was this resolved with "zfs import -a"?

Comment by Saurabh Tandan (Inactive) [ 06/May/18 ]

Yes it was while doing rolling upgrade/downgrade. But while doing clean upgrade/downgrade I tried to import it using both pool name and "-a" it didn't worked either way.

Comment by Sarah Liu [ 17/Oct/18 ]

The cannot import pool failure still exists when clean upgrade from 2.10.5 to 2.11.56. Both builds use zfs-0.7.9-1

Comment by Sarah Liu [ 17/Oct/18 ]

Just tried upgrade from 2.11.0 to master, not seeing this problem, pool can be imported after upgrade.

Comment by Andreas Dilger [ 17/Oct/18 ]

The cannot import pool failure still exists when clean upgrade from 2.10.5 to 2.11.56. Both builds use zfs-0.7.9-1

Sarah,
are there any error messages on the console when you try to import the pool? This would be a fairly serious error if we can't upgrade from 2.10.x (which is the version almost every ZFS user is using) to 2.12 

Comment by Andreas Dilger [ 17/Oct/18 ]

Nathaniel, can you work with Sarah to understand this issue better? It might be related to some new ZFS feature we are trying to use? In any case, we need to understand it before 2.12 goes out the door or we could have a big compatibility problem on our hands. Hopefully the issue is not already present in the 2.11 release, but at least relatively few people are using that.

Comment by Nathaniel Clark [ 18/Oct/18 ]

The zpool import should be independent of the Lustre version. Do you have a log (messages and journal)?
If you still have a system, can you also run:

zpool events -v
Comment by Sarah Liu [ 19/Oct/18 ]

There isn't error mesg, just a message says "no pool available"

I will run the command Nathaniel mentioned to get more info.

Comment by Sarah Liu [ 23/Oct/18 ]

I cannot reproduce the problem with 2 trials (1 with fresh format zfs; 2 with ldiskfs first, then reformat as zfs); I think there must be some misoperation in my previous test.

Comment by Peter Jones [ 23/Oct/18 ]

ok - thanks Sarah!

Generated at Sat Feb 10 02:39:59 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.