Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zpool cannot create pool / mix multipath with vdev_id.conf defined disks (not a bug) #5008

Closed
ltaulell opened this issue Aug 22, 2016 · 1 comment

Comments

@ltaulell
Copy link

Not a bug, Maybe FAQ/Documentation lack.

TL;DR: Do NOT mix multipath and vdev_id.conf configured disks.

I have ran into a mix of several already reported bugs, which were all closed (and patched/corrected) on a brand new server (2016/07, Debian Jessie, zfs 0.6.5.7-8-jessie).

We install our debian fileservers with a bunch of packages, regardless of usage. This include multipath and debian-zfs.

On this particular server (Dell R730xd), there is only one standard SAS card (H330, in JBOD mode), with one backplane and 24+2 disks. No multipath needs. So I configured it only with vdev_id.conf file r730datacs-vdev_id.conf.txt.

I ran into, what seems to be #2582, #2493, and #3708 bugs (at least): I was unable to create any zpool, unless:

  • purge all multipath packages,
  • manually add a gpt label on each futur-zfs disks,
  • reboot (reread partitions tables was not enough, /dev/mapper need to be empty, apparently).

The thing that lead me to a multipath "problem" was lsblk, showing "TYPE: mpath" instead of "TYPE: disk" one some disks (not all), although I was not using multipath at all (no config).

Now, it's running fine. I've been able to create some pools, even use them :o)

Hope its helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@ltaulell and others