[ovirt-users] Issues with ZFS volume creation

[Staniforth, Paul]

Hello Tal,

                 ZFS is probably detecting a partition table on the disks, you could delete the partition tables on /dev/sda,/dev/sdb  ... etc, or you could use the force option of ZFS create making sure they aren't mounted somewhere.


Regards,

               Paul S.

________________________________
From: users-bounces at ovirt.org <users-bounces at ovirt.org> on behalf of Tal Bar-Or <tbaror at gmail.com>
Sent: 25 March 2018 15:54
To: users
Subject: [ovirt-users] Issues with ZFS volume creation


Hello All,
I know this question is might be out of Ovirt scope, but I don't have anywhere else to ask for this issue (ZFS users mailing doesn't work), so I am trying my luck here anyway
so the issues go as follows :

Installed ZFS on top of CentOs 7.4 with Ovirt 4.2 , on physical Dell R720 with 15 sas  10 k 1.2TB each attached to PERC H310 adapter, disks are configured to non-raid, all went OK, but when I am trying to create new zfs pool using the following command:

zpool create -m none -o ashift=12 zvol raidz2 sda sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl sdm
I get the following error below:
/dev/sda is in use and contains a unknown filesystem.
/dev/sdb is in use and contains a unknown filesystem.
/dev/sdc is in use and contains a unknown filesystem.
/dev/sdd is in use and contains a unknown filesystem.
/dev/sde is in use and contains a unknown filesystem.
/dev/sdf is in use and contains a unknown filesystem.
/dev/sdg is in use and contains a unknown filesystem.
/dev/sdh is in use and contains a unknown filesystem.
/dev/sdi is in use and contains a unknown filesystem.
/dev/sdj is in use and contains a unknown filesystem.
/dev/sdk is in use and contains a unknown filesystem.
/dev/sdl is in use and contains a unknown filesystem.
/dev/sdm is in use and contains a unknown filesystem.

When typing command lsblk I get the following output below, all seems ok, any idea what could be wrong?
Please advice
Thanks

# lsblk
NAME                MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
sda                   8:0    0  1.1T  0 disk
??35000cca07245c0ec 253:2    0  1.1T  0 mpath
sdb                   8:16   0  1.1T  0 disk
??35000cca072463898 253:10   0  1.1T  0 mpath
sdc                   8:32   0  1.1T  0 disk
??35000cca0724540e8 253:8    0  1.1T  0 mpath
sdd                   8:48   0  1.1T  0 disk
??35000cca072451b68 253:7    0  1.1T  0 mpath
sde                   8:64   0  1.1T  0 disk
??35000cca07245f578 253:3    0  1.1T  0 mpath
sdf                   8:80   0  1.1T  0 disk
??35000cca07246c568 253:11   0  1.1T  0 mpath
sdg                   8:96   0  1.1T  0 disk
??35000cca0724620c8 253:12   0  1.1T  0 mpath
sdh                   8:112  0  1.1T  0 disk
??35000cca07245d2b8 253:13   0  1.1T  0 mpath
sdi                   8:128  0  1.1T  0 disk
??35000cca07245f0e8 253:4    0  1.1T  0 mpath
sdj                   8:144  0  1.1T  0 disk
??35000cca072418958 253:5    0  1.1T  0 mpath
sdk                   8:160  0  1.1T  0 disk
??35000cca072429700 253:1    0  1.1T  0 mpath
sdl                   8:176  0  1.1T  0 disk
??35000cca07245d848 253:9    0  1.1T  0 mpath
sdm                   8:192  0  1.1T  0 disk
??35000cca0724625a8 253:0    0  1.1T  0 mpath
sdn                   8:208  0  1.1T  0 disk
??35000cca07245f5ac 253:6    0  1.1T  0 mpath


--
Tal Bar-or
To view the terms under which this email is distributed, please go to:-
http://disclaimer.leedsbeckett.ac.uk/disclaimer/disclaimer.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180403/b44b6e2b/attachment.html>