Problem solved The service wasn't starting correctly due to the init script looking for directories /var/target/pr and /var/target/alua when they are actually installed in /var/lib/target/... Fixed the init script in my repo, updated, started service and worked perfectly. ________________________________________ From: Nicholas A. Bellinger [nab@xxxxxxxxxxxxxxx] Sent: 18 October 2013 20:16 To: Myles Gray Cc: target-devel@xxxxxxxxxxxxxxx Subject: Re: [Errno 22] Invalid argument: '/sys/kernel/config/target/core/iblock_0' Hi Myles, On Thu, 2013-10-17 at 08:34 +0000, Myles Gray wrote: > Hi All, > > Seeing this problem when creating an iblock backstore > (it's worked on this config before): > > /backstores/iblock> create data0 /dev/sda5 > Cannot create backstore: > [Errno 22] Invalid argument: '/sys/kernel/config/target/core/iblock_0' > > It won't let me create any backstores: > > /backstores/fileio> create data0 /tmp/test 1G > Cannot create backstore: > [Errno 22] Invalid argument: '/sys/kernel/config/target/core/fileio_0' > > The error message is very unhelpful - does anyone > recognise what might be going on? > As Benjamin mentioned, the dmesg output would be the most helpful to determine where kernel code is returning -EINVAL. Also, the target_core_iblock.ko + target_core_fileio.ko modules will be automatically modprobed by target_core_mod.ko when necessary, but it would be worthwhile to verify they are loaded. --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
