[Pkg-iscsi-maintainers] Bug#661397: iscsitarget: prompting due to modified conffiles which where not modified by the user
Ritesh Raj Sarraf
rrs at debian.org
Thu Mar 29 12:01:22 UTC 2012
Package: iscsitarget
Version: 1.4.20.2-10
Followup-For: Bug #661397
I did an update of iscsitarget on my box and did not see the prompt. I will still try with older versions if time permits. But this stands low on priority on my list.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages iscsitarget depends on:
ii libc6 2.13-27
ii lsb-base 4.1+Debian0
ii procps 1:3.3.2-3
Versions of packages iscsitarget recommends:
pn iscsitarget-module <none>
Versions of packages iscsitarget suggests:
ii iscsitarget-dkms 1.4.20.2-10
-- Configuration Files:
/etc/iet/ietd.conf changed:
Target iqn.2001-04.com.example:storage.debian-sanboot
Lun 0 Path=/dev/vdl,Type=fileio,ScsiId=vdl,ScsiSN=vdl
Alias Debian-SANBooot
Target iqn.2001-04.com.example:storage.debian
# CHAP Users
#
# The same rules as for discovery users apply here.
#
# Don't set them if you don't want to use CHAP authentication.
#
#IncomingUser joe secret
#OutgoingUser jim 12charpasswd
#
# Logical Unit definition
#
# Block devices, regular files (fileio only), LVM, and RAID
# can be offered to the initiators as a block device.
#
# Lun numbers MUST start with zero (each target needs a Lun 0)
#
Lun 0 Path=/dev/vdg,Type=fileio,ScsiId=vdb,ScsiSN=vdb
Lun 1 Path=/dev/vdh,Type=fileio,ScsiId=vdc,ScsiSN=vdc
Lun 2 Path=/dev/vdi,Type=fileio,ScsiId=vdd,ScsiSN=vdd
Lun 3 Path=/dev/vdj,Type=fileio,ScsiId=vde,ScsiSN=vde
Lun 4 Path=/dev/vdk,Type=fileio,ScsiId=vdf,ScsiSN=vdf
#
# Alias name for this target (Not Used)
#
Alias Debian
Target iqn.2001-04.com.example:storage.disk2.sys1.xyz
# CHAP Users
#
# The same rules as for discovery users apply here.
#
# Don't set them if you don't want to use CHAP authentication.
#
#IncomingUser joe secret
#OutgoingUser jim 12charpasswd
#
# Logical Unit definition
#
# Block devices, regular files (fileio only), LVM, and RAID
# can be offered to the initiators as a block device.
#
# Lun numbers MUST start with zero (each target needs a Lun 0)
#
Lun 0 Path=/dev/vdb,Type=fileio,ScsiId=vdb,ScsiSN=vdb
Lun 1 Path=/dev/vdc,Type=fileio,ScsiId=vdc,ScsiSN=vdc
Lun 2 Path=/dev/vdd,Type=fileio,ScsiId=vdd,ScsiSN=vdd
Lun 3 Path=/dev/vde,Type=fileio,ScsiId=vde,ScsiSN=vde
Lun 4 Path=/dev/vdf,Type=fileio,ScsiId=vdf,ScsiSN=vdf
#
# Alias name for this target (Not Used)
#
Alias Fedora
#
# Various iSCSI parameters
# (not all are used right now, see also iSCSI spec for details)
#
# Outgoing SCSI data (initiator to target user data or command
# parameters) is sent as either solicited data or unsolicited data.
# Solicited data is sent in response to R2T PDUs. Unsolicited data
# can be sent as part of an iSCSI command PDU sequence
# ("Immediate Data") or as a separate iSCSI data PDU sequence.
#
#MaxConnections 1 # Number of connections/session
# We only support 1
#MaxSessions 0 # Number of sessions/target
# 0 = no explicit limit
#InitialR2T Yes # Wait first for R2T
# Yes = no unsolicited data
#ImmediateData Yes # Data can accompany command
# Yes = cmnd/data in same PDU
#MaxRecvDataSegmentLength 8192 # Max data per PDU to receive
#MaxXmitDataSegmentLength 8192 # Max data per PDU to transmit
#MaxBurstLength 262144 # Max data per sequence (R2T)
#FirstBurstLength 65536 # Max unsolicited data sequence
#DefaultTime2Wait 2 # Secs wait for ini to log out
# Not used
#DefaultTime2Retain 20 # Secs keep cmnds after log out
# Not used
#MaxOutstandingR2T 1 # Max outstanding R2Ts per cmnd
#DataPDUInOrder Yes # Data in PDUs is ordered
# We only support ordered
#DataSequenceInOrder Yes # PDUs in sequence are ordered
# We only support ordered
#ErrorRecoveryLevel 0 # We only support level 0
#HeaderDigest None,CRC32C # PDU header checksum algo list
# None or CRC32C
# If only one is set then the
# initiator must agree to it
# or the connection will fail
#DataDigest None,CRC32C # PDU data checksum algo list
# Same as above
#MaxSessions 0 # Maximum number of sessions to
# this target - 0 = unlimited
#NOPInterval 0 # Send a NOP-In ping each after
# that many seconds if the conn
# is otherwise idle - 0 = off
#NOPTimeout 0 # Wait that many seconds for a
# response on a NOP-In ping
# If 0 or > NOPInterval, NOPInterval
# is used!
#
# Various target parameters
#
#Wthreads 8 # Number of IO threads
#QueuedCommands 32 # Number of queued commands
/etc/iet/initiators.allow changed:
iqn.2001-04.com.example:storage.debian ALL
iqn.2001-04.com.example:storage.disk2.sys1.xyz 192.168.122.0/8
iqn.2001-04.com.example:storage.debian-sanboot ALL
-- no debconf information
-------------- next part --------------
Preparing to replace iscsitarget 1.4.20.2-6 (using .../iscsitarget_1.4.20.2-10_amd64.deb) ...
Removing iSCSI enterprise target devices: :.
Unpacking replacement iscsitarget ...
Preparing to replace iscsitarget-dkms 1.4.20.2-6 (using .../iscsitarget-dkms_1.4.20.2-10_all.deb) ...
-------- Uninstall Beginning --------
Module: iscsitarget
Version: 1.4.20.2
Kernel: 3.0.0-1-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
iscsi_trgt.ko:
- Uninstallation
- Deleting from: /lib/modules/3.0.0-1-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
depmod.........
DKMS: uninstall completed.
------------------------------
Deleting module version: 1.4.20.2
completely from the DKMS tree.
------------------------------
Done.
Unpacking replacement iscsitarget-dkms ...
Preparing to replace iso-codes 3.28-1 (using .../iso-codes_3.33-1_all.deb) ...
and later....
Setting up iscsitarget (1.4.20.2-10) ...
Installing new version of config file /etc/init.d/iscsitarget ...
iscsitarget not enabled in "/etc/default/iscsitarget", not starting... ... (warning).
Setting up iscsitarget-dkms (1.4.20.2-10) ...
Creating symlink /var/lib/dkms/iscsitarget/1.4.20.2/source ->
/usr/src/iscsitarget-1.4.20.2
DKMS: add completed.
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area....
make KERNELRELEASE=3.0.0-1-amd64 -C /lib/modules/3.0.0-1-amd64/build M=/var/lib/dkms/iscsitarget/1.4.20.2/build.........
cleaning build area....
DKMS: build completed.
iscsi_trgt:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/3.0.0-1-amd64/updates/dkms/
depmod....
DKMS: install completed.
Setting up iso-codes (3.33-1) ...
Setting up libglib2.0-data (2.30.2-6) ...
Setting up libsgutils2-2 (1.33-1) ...
More information about the Pkg-iscsi-maintainers
mailing list