/dev/fioa not showing up in OMV gui

nexusone · Nov 4th 2014

Where do I configure what device types show up as storage devices? OMV is not recognizing my /dev/fioa device. It works fine. I can format and mount from cli, but OMV ignores it.

Solo0815 · Nov 4th 2014

As far as I can see, fio is just a device to measure the IO-Performance. Correct me, if I'm wrong. What is "fio". Please explain a little bit more. Feel free to add a feature request on Mantis, also: http://bugtracker.openmediavault.org/main_page.php

To implement is, we have to wait for Volker to have a look @ this.

@ Volker:
Here is more info:
http://serverascode.com/server…-redhat-enterprise-5.html
http://www.thomas-krenn.com/de/wiki/Fio_Grundlagen
http://xinglin-system.blogspot…ure-disk-performance.html
http://www.bluestop.org/fio/HOWTO.txt

nexusone · Nov 4th 2014

When I manually create the filesystem with mkfs.ext4 it creates the UUID and then the partition shows up on OMV but I still can't mount it from the gui and the physical device doesn't show up. Mounting it manually from the cli works perfectly.

Help. How do I tell OMV to behave?

nexusone · Nov 4th 2014

solo0815 : fio is a FusionIO card. PCIe attached SSD.

nicjo814 · Nov 4th 2014

I would say it needs a storage device backend implemented in OMV. There is a list of supported "core" backends and the fusionIO does not seem to be in the list. Either it needs to be added via core implementation or via a plugin.

votdev · Nov 4th 2014

This is correct. If it is currently not detected, then it needs a special storage backend implementation to work in OMV. To do this i need such a device for implementation.

nexusone · Nov 4th 2014

That's unfortunate. It presents exactly like any other storage device. There is nothing special about it once the device driver is loaded, which it is. If you want to collect device status and such from it, then sure I understand that you need something unique to the device, but to mkfs and mount? That seems like it's probably a matter of adding the device identifier (/dev/fio*) to a list somewhere.

Thank you for the response. I'll poke around some more. Worst case I'll just symlink it into an existing share and be done with it.

nexusone · Nov 4th 2014

looks like the hp raid status plugin is a good basis for collecting status from the fio device. They use a tool called fio-status that creates very similar output. no problem there. I can hack that up after work today.

Can you point me to an example of a storage backend?

Thank you.

votdev · Nov 4th 2014

Have a look here http://sourceforge.net/p/openm…openmediavault/system.inc

Look for

Code

OMVStorageDeviceBackendCCISS
OMVStorageDeviceCCISS

votdev · Nov 4th 2014

Maybe this one fits more:

Code

OMVStorageDeviceBackendHDD
OMVStorageDeviceHDD

votdev · Nov 4th 2014

Check http://sourceforge.net/p/openmediavault/code/1561 for the OMVStorageDeviceBackendFIO implementation. Maybe this will work out-of-the-box.

nexusone · Nov 5th 2014

Thanks. I'll poke around and experiment with this.

nexusone · Nov 6th 2014

Other than copying this file into the correct location, is there anything I need to do? I don't see anything changed.

EDIT : Nevermind. A good old reboot cleared whatever was cached. Let me see how this works.

nexusone · Nov 6th 2014

So it shows up in physical disks, but I'm unable to create or mount it from within OMV. So close.

Thanks for the help.

nexusone · Nov 6th 2014

Manually wiped the FIO volume, now I'm able to create a volume inside OMV. Still can't mount it however.

nexusone · Nov 6th 2014

I can manually mount the volume from the cli and it will show up in OMV now. It still won't mount the volume from inside OMV. Odd.

nicjo814 · Nov 6th 2014

To apply changes made to system files while the system is running you have to issue the command "/etc/init.d/openmediavault-engined restart" and if that command fails you can use "omv-engined -d" to check for errors in the code.
Could you try to remove all partitions from the disk in cli and then create a filesystem on it from within the gui? When the filesystem is being created OMV will present a device name in the list of filesyetems. Could you post that name along with the contents of /proc/partitions tomake sure OMV coorrectly identifies the new partiton?

votdev · Nov 6th 2014

Quote from nexusone

Manually wiped the FIO volume, now I'm able to create a volume inside OMV. Still can't mount it however.

What is the output of

Code

# cat /proc/partitions
# export LANG=C; blkid
# export LANG=C; udevadm info --query=property --name=/dev/fioa

after you've created the filesystem via WebGUI?

The FIO storage backend has been improved: http://sourceforge.net/p/openmediavault/code/1562

nexusone · Nov 7th 2014

That update to system.inc seems to have done the trick. Nice work!

nexusone · Nov 7th 2014

For anyone finding this thread later....

1) Get your debian drivers for your card
2) Install the VSL and supporting utility packages as desired (Use SSH. You can't do this from the GUI.) Reboot to load drivers. You can verify operation by using fio-status from the CLI, assuming you installed the supporting utility packages.
3) Create your volume and mount like normal.
4) Make sure you configure the driver with an snmp trap to send alerts on alarm conditions, if you're worried about that.
5) Enjoy your OMV+FIO awesomeness.
6) The physical disk screen does NOT show model, serial number, or vendor of the device. Don't worry about this, it's working fine. Probably something easily fixed with some hacking to pull status from the fio-status tool.

Participate now!