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

Bug#467445: marked as done (linux-image-2.6.22-4-amd64: iSCSI management interface is detected as a disk)

Your message dated Fri, 17 Jul 2009 22:13:08 +0200
with message-id <20090717201308.GE17290@inutil.org>
and subject line Re: linux-image-2.6.22-4-amd64: iSCSI management interface is detected as a disk
has caused the Debian Bug report #467445,
regarding linux-image-2.6.22-4-amd64: iSCSI management interface is detected as a disk
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
467445: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467445
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.22-4-amd64
Version: 2.6.22-6~bpo40+2
Severity: minor

  When I log into a Dell MD3000i disk array using iscsiadm, I see the
two volumes that I've configured show up as scsi disks, which is as it
should be:

Feb 21 21:35:10 localhost kernel: scsi1 : iSCSI Initiator over TCP/IP
Feb 21 21:35:10 localhost kernel: scsi 1:0:0:0: Direct-Access     DELL     MD3000i          0670 PQ: 0 ANSI: 5
Feb 21 21:35:10 localhost kernel: sd 1:0:0:0: [sdc] 4269801472 512-byte hardware sectors (2186138 MB)
Feb 21 21:35:10 localhost kernel: sd 1:0:0:0: [sdc] Write Protect is off
Feb 21 21:35:10 localhost kernel: sd 1:0:0:0: [sdc] Mode Sense: 77 00 10 08
Feb 21 21:35:10 localhost kernel: sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
Feb 21 21:35:10 localhost kernel: sd 1:0:0:0: [sdc] 4269801472 512-byte hardware sectors (2186138 MB)
Feb 21 21:35:10 localhost kernel: sd 1:0:0:0: [sdc] Write Protect is off
Feb 21 21:35:10 localhost kernel: sd 1:0:0:0: [sdc] Mode Sense: 77 00 10 08
Feb 21 21:35:10 localhost kernel: sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
Feb 21 21:35:10 localhost kernel:  sdc: unknown partition table
Feb 21 21:35:10 localhost kernel: sd 1:0:0:0: [sdc] Attached SCSI disk
Feb 21 21:35:10 localhost kernel: scsi 1:0:0:1: Direct-Access     DELL     MD3000i          0670 PQ: 0 ANSI: 5
Feb 21 21:35:10 localhost kernel: sd 1:0:0:1: [sdd] 1586597888 512-byte hardware sectors (812338 MB)
Feb 21 21:35:10 localhost kernel: sd 1:0:0:1: [sdd] Write Protect is off
Feb 21 21:35:10 localhost kernel: sd 1:0:0:1: [sdd] Mode Sense: 77 00 10 08
Feb 21 21:35:10 localhost kernel: sd 1:0:0:1: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
Feb 21 21:35:10 localhost kernel: sd 1:0:0:1: [sdd] 1586597888 512-byte hardware sectors (812338 MB)
Feb 21 21:35:10 localhost kernel: sd 1:0:0:1: [sdd] Write Protect is off
Feb 21 21:35:10 localhost kernel: sd 1:0:0:1: [sdd] Mode Sense: 77 00 10 08
Feb 21 21:35:10 localhost kernel: sd 1:0:0:1: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
Feb 21 21:35:10 localhost kernel:  sdd: unknown partition table
Feb 21 21:35:10 localhost kernel: sd 1:0:0:1: [sdd] Attached SCSI disk
Feb 21 21:35:10 localhost kernel: scsi 1:0:0:31: Direct-Access     DELL     Universal Xport  0670 PQ: 0 ANSI: 5

  I also see it attempt to bring up a third "disk", which is actually
the in-band management interface, and I see a number of I/O errors as it
tries to read the partition table:

Feb 21 21:35:10 localhost kernel: sd 1:0:0:31: [sde] 40960 512-byte hardware sectors (21 MB)
Feb 21 21:35:10 localhost kernel: sd 1:0:0:31: [sde] Write Protect is off
Feb 21 21:35:10 localhost kernel: sd 1:0:0:31: [sde] Mode Sense: 77 00 10 08
Feb 21 21:35:10 localhost kernel: sd 1:0:0:31: [sde] Write cache: disabled, read cache: enabled, supports DPO and FUA
Feb 21 21:35:10 localhost kernel: sd 1:0:0:31: [sde] 40960 512-byte hardware sectors (21 MB)
Feb 21 21:35:10 localhost kernel: sd 1:0:0:31: [sde] Write Protect is off
Feb 21 21:35:10 localhost kernel: sd 1:0:0:31: [sde] Mode Sense: 77 00 10 08
Feb 21 21:35:10 localhost kernel: sd 1:0:0:31: [sde] Write cache: disabled, read cache: enabled, supports DPO and FUA
Feb 21 21:35:10 localhost kernel:  sde: unknown partition table
Feb 21 21:35:10 localhost kernel: sd 1:0:0:31: [sde] Attached SCSI disk
Feb 21 21:35:11 localhost kernel: end_request: I/O error, dev sde, sector 48
Feb 21 21:35:11 localhost kernel: Buffer I/O error on device sde, logical block 6
Feb 21 21:35:11 localhost kernel: Buffer I/O error on device sde, logical block 7
Feb 21 21:35:11 localhost kernel: Buffer I/O error on device sde, logical block 8
Feb 21 21:35:11 localhost kernel: Buffer I/O error on device sde, logical block 9
Feb 21 21:35:11 localhost kernel: Buffer I/O error on device sde, logical block 10
Feb 21 21:35:11 localhost kernel: Buffer I/O error on device sde, logical block 11
Feb 21 21:35:11 localhost kernel: Buffer I/O error on device sde, logical block 12
Feb 21 21:35:11 localhost kernel: Buffer I/O error on device sde, logical block 13
Feb 21 21:35:11 localhost kernel: Buffer I/O error on device sde, logical block 14
Feb 21 21:35:11 localhost kernel: Buffer I/O error on device sde, logical block 15

  I'm not sure if this is something the enclosure is reporting oddly
that there's no way for the kernel to get right.  It's also easily work-
around-able by simply disabling the in-band management interface in the
Dell tools.  Nonetheless it seems that in a perfect world, this
interface would be detected for what it is and not exposed as a disk
(even if it's not going to be exposed as a management interface either).
  FWIW, the iSCSI subsystem maintainer has said that this is something
that needs to be addressed in the scsi subsystem, and not anything he
has direct control over from the iSCSI layer.
  Cheers!

-- Package-specific info:

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-amd64
Locale: LANG=en_US.ISO-8859-1, LC_CTYPE=en_US.ISO-8859-1 (charmap=ISO-8859-1)

Versions of packages linux-image-2.6.22-4-amd64 depends on:
ii  e2f 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 ext2 file system utilities and lib
ii  ini 0.85h                                tools for generating an initramfs
ii  mod 3.3-pre4-2                           tools for managing Linux kernel mo

linux-image-2.6.22-4-amd64 recommends no packages.

-- debconf information excluded

--- End Message ---
--- Begin Message --- 
On Sun, Dec 28, 2008 at 09:34:13AM -0500, Andrew Moise wrote:
> On Sat, Dec 27, 2008 at 5:00 PM, Moritz Muehlenhoff <jmm@inutil.org> wrote:
> > On Tue, May 20, 2008 at 06:36:22PM +0200, maximilian attems wrote:
> >> does this still happen with a recent kernel aka 2.6.25 linux images?
> >>
> >> thanks for feedback.
> >
> > Andrew, does this error still occur with more recent kernel versions?
> 
>   This will be a bit difficult for me to test -- I'm no longer working
> for the company were I encountered this bug :-(.  I still do
> contracting for them once in a blue moon; let me see if I can talk
> them into letting me test this upgrade.

We'll close the bug for now. Please reopen if you can still reproduce.

Cheers,
        Moritz

--- End Message ---
Reply to: