Is this something we need to worry about for OMV 1.x and 2.x?
The Article states it's caused by the 4.0 Kernel, so no. For the time beeing you can't be affected by it. But we should keep an eye on it when we move to jessie and start using the backports kernel - when jessie has the 4.0 kernel as backports then.
This problem seems to be very limited. Never the less I will contact @votdev to take a deeper look at the bug to find out wether or not this could affect you.
"Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"
Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. Upload Logfile via WebGUI/CLI
#openmediavault on freenode IRC | German & English | GMT+1
Absolutely no Support via PM!
I host parts of the omv-extras.org Repository, the OpenMediaVault Live Demo and the pre-built PXE Images. If you want you can take part and help covering the costs by having a look at my profile page.
I'm not sure that i am able to tell you what you want to hear. I'm not a kernel developer, so i can not say anything about this issue. What i read about it is that the scenario is limited to RAID0 w/o discard mount option, but that should be nothing new to you. You have to decide yourself if this bug is a problem for your installation.
Absolutely no support through PM!
I must not fear.
Fear is the mind-killer.
Fear is the little-death that brings total obliteration.
I will face my fear.
I will permit it to pass over me and through me.
And when it has gone past I will turn the inner eye to see its path.
Where the fear has gone there will be nothing.
Only I will remain.
I have not had any issues with EXT4 either, yet (EXT4 in 5 x 2TB in RAID 5). Just another point on the side of changing to XFS for future builds especially if someone wants to do a RAID 0 build for speed.