targetcli bug - buffered fileio mode not saved across reboots

[Freaky]

Buffered fileio mode is not saved properly by the current targetcli version which causes the setting to be lost upon reboot.

Please see the relevant iscsi-target list thread for the fix:

http://permalink.gmane.org/gmane.linux.scsi.target.devel/3209

WORKAROUND (from the iscsi-target thread above):

You can manually re-enable FILEIO buffered IO by appending
',fd_buffered_io=1' to each your FILEIO backends like so in
your /etc/target/tcm_start.sh:

tcm_node --establishdev fileio_0/fileio_test0 \
fd_dev_name=/usr/src/fileio_test0,fd_dev_size=21474836480,fd_buffered_io=1

This setting can also be checked via configfs directly:

# cat /sys/kernel/config/target/core/fileio_0/fileio_test0/info
Status: ACTIVATED Max Queue Depth: 32 SectorSize: 512 HwMaxSectors: 1024
        TCM FILEIO ID: 0 File: /usr/src/fileio_test0 Size: 21474836480 Mode: Buffered-WCE

ProblemType: BugDistroRelease: Ubuntu 12.10
Package: targetcli 2.0rc1-2
ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
Uname: Linux 3.5.0-22-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
Date: Thu Jan 31 22:44:06 2013
InstallationDate: Installed on 2013-01-30 (1 days ago)
InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bashSourcePackage: targetcli
UpgradeStatus: No upgrade log present (probably fresh install)

[C de-Avillez (hggdh2)]

Marking triaged/medium; All of Precise, Quantal, and Raring should be affected (same targetcli version). There *is* a workaround, though, as described in the iscsi-target thread in the description.

[cerdea-aws]cerdea@xango3:/build/buildd/lyx$ rmadison targetcli
 targetcli | 2.0rc1-2 | precise/universe | source, all
 targetcli | 2.0rc1-2 | quantal/universe | source, all
 targetcli | 2.0rc1-2 | raring/universe | source, all
[cerdea-aws]cerdea@xango3:/build/buildd/lyx$

[Freaky (freaky)]

Affects 13.04 too.

What does it take to get it fixed? It's only a small python script, looking at this bug takes more time than fixing it for someone with the proper access.