Re: /etc/target/saveconfig.json Fedora 20

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Pascal,

On Fri, 2014-03-14 at 20:41 +0100, pviltard@xxxxxxx wrote:
> Hello,
> 
> I have an another issue.
> 
> /> ls
> o- / ..................................................................... [...]
>   o- backstores .......................................................... [...]
>   | o- block .............................................. [Storage Objects: 1]
>   | | o- backend_x2200 ................ [/dev/zd0 (1.0GiB) write-thru activated]
>   | o- fileio ............................................. [Storage Objects: 0]
>   | o- pscsi .............................................. [Storage Objects: 0]
>   | o- ramdisk ............................................ [Storage Objects: 0]
>   o- iscsi ........................................................ [Targets: 0]
>   o- loopback ..................................................... [Targets: 0]
>   o- qla2xxx ...................................................... [Targets: 1]
>   | o- naa.2100001b3215dd57 ......................................... [gen-acls]
>   |   o- acls ........................................................ [ACLs: 0]
>   |   o- luns ........................................................ [LUNs: 1]
>   |     o- lun0 ............................... [block/backend_x2200 (/dev/zd0)]
>   o- vhost ........................................................ [Targets: 0]
> /> exit
> Global pref auto_save_on_exit=true
> Last 10 configs saved in /etc/target/backup.
> Configuration saved to /etc/target/saveconfig.json
> [root@philippe ~]# reboot
> 
> At the reboot, the file contents :
> [root@philippe target]# more saveconfig.json
> {
>   "fabric_modules": [],
>   "storage_objects": [],
>   "targets": []
> }
> [root@philippe target]# uname -a
> Linux philippe.pvi.org 3.11.10-301.fc20.x86_64 #1 SMP Thu Dec 5 14:01:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> [root@philippe target]#
> 
> I found :
> 
> ------------------------------------------------->
> 
>  Bruno Goncalves 2013-04-26 11:28:10 EDT
> 
> Correct, configuring the process to start on boot solves the problem.
> 
> chkconfig targetcli on
> 
> systemctl list-unit-files | grep targetcli
> targetcli.service                           enabled
> 
> 
> ------------------------------------------------->
> 
> I try it. no configuration at reboot.
> 

Looks like some -fb specific breakage.  CC'ing Andy.

--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




[Index of Archives]     [Linux SCSI]     [Kernel Newbies]     [Linux SCSI Target Infrastructure]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Device Mapper]

  Powered by Linux