On Mon, 2014-02-24 at 09:22 +0100, Henrik Goldman wrote: > > > > What's the extra patch..? > > > > It's https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=95cadace8f3959282e76ebf8b382bd0930807d2c > target/file: Update hw_max_sectors based on current block_size > > We're still waiting for next official Ubuntu to have it included. > Hence the manual patching. > > Ok yeah, that one is good to have. > > > > Need more context on what's underneath the FILEIO LUNs to be helpful.. > > > > We have a LSI-9261-8i controller with a set of SSD's. They are > configured as a RAID 5 volume exported to the OS as /dev/sda. This > volume is directly used using targetcli as a backing device. No > paritions are made or anything but directly exported as buffered IO as > a LUN. > The command for creation was: > > /> cd backstores/fileio/ > create SSD /dev/sda buffered=true > > Let me know if more details are needed. > So AFAICT the -EINVAL error on READs is most likely coming some where from within the underlying file-system, and not the underlying storage (eg: we'd typically see a HBA failure if this was the case). Anything special about the file-system here..? --nab -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
