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

Bug#414689: linux-image-2.6.18-4-amd64: usb-storage process stuck in state D after massive IO



Package: linux-image-2.6.18-4-amd64
Version: 2.6.18.dfsg.1-11
Severity: normal

Hello

I've launched a command to remove a massive amount of file on an usb
disk. Roughly speaking ~200000 files for ~ 10Gb of data.

The command worked fine for several minutes, but now the rm process is
stuck: 

$ cat /proc/30886/status
Name:   rm
State:  D (disk sleep)
SleepAVG:       78%
Tgid:   30886
Pid:    30886
PPid:   30219
TracerPid:      0
Uid:    0       0       0       0
Gid:    0       0       0       0
FDSize: 256
Groups: 0
VmPeak:     3852 kB
VmSize:     3852 kB
VmLck:         0 kB
VmHWM:       512 kB
VmRSS:       512 kB
VmData:      160 kB
VmStk:        88 kB
VmExe:        40 kB
VmLib:      1248 kB
VmPTE:        20 kB
Threads:        1
SigQ:   4/18446744073709551615
SigPnd: 0000000000000100
ShdPnd: 0000000000084100
SigBlk: 0000000000000000
SigIgn: 0000000000000000
SigCgt: 0000000000000000
CapInh: 0000000000000000
CapPrm: 00000000fffffeff
CapEff: 00000000fffffeff
Cpus_allowed:   ffffffff
Mems_allowed:   00000000,00000001

Kill and kill -9 don't work.

Any other access to the usb disk are also stuck in state D.

The stuck disk is mounted with (from /etc/mtab):
/dev/sde6 /media/disk ext3 rw,noexec,nosuid,nodev,sync,data=ordered 0 0


On the other hand, access to another usb disk (on a different usb
head) works normally.

Since kill does not work, halt does not work either. I need to reset
my machine to restore access to the usb disk.

Feel free to contact me if you need other informations.

Cheers

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages linux-image-2.6.18-4-amd64 depends on:
ii  coreutil 5.97-5.3                        The GNU core utilities
ii  debconf  1.5.13                          Debian configuration management sy
ii  e2fsprog 1.39+1.40-WIP-2006.11.14+dfsg-2 ext2 file system utilities and lib
ii  initramf 0.85f                           tools for generating an initramfs
ii  module-i 3.3-pre4-2                      tools for managing Linux kernel mo

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

-- debconf information:
  linux-image-2.6.18-4-amd64/postinst/kimage-is-a-directory:
  linux-image-2.6.18-4-amd64/postinst/bootloader-test-error-2.6.18-4-amd64:
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.18-4-amd64/preinst/lilo-initrd-2.6.18-4-amd64: true
  linux-image-2.6.18-4-amd64/preinst/initrd-2.6.18-4-amd64:
  linux-image-2.6.18-4-amd64/preinst/abort-overwrite-2.6.18-4-amd64:
  linux-image-2.6.18-4-amd64/preinst/failed-to-move-modules-2.6.18-4-amd64:
  linux-image-2.6.18-4-amd64/postinst/old-initrd-link-2.6.18-4-amd64: true
  linux-image-2.6.18-4-amd64/postinst/depmod-error-initrd-2.6.18-4-amd64: false
  linux-image-2.6.18-4-amd64/postinst/create-kimage-link-2.6.18-4-amd64: true
  linux-image-2.6.18-4-amd64/preinst/lilo-has-ramdisk:
  linux-image-2.6.18-4-amd64/postinst/old-dir-initrd-link-2.6.18-4-amd64: true
  linux-image-2.6.18-4-amd64/postinst/depmod-error-2.6.18-4-amd64: false
  linux-image-2.6.18-4-amd64/prerm/removing-running-kernel-2.6.18-4-amd64: true
  linux-image-2.6.18-4-amd64/postinst/bootloader-error-2.6.18-4-amd64:
  linux-image-2.6.18-4-amd64/postinst/old-system-map-link-2.6.18-4-amd64: true
  linux-image-2.6.18-4-amd64/preinst/already-running-this-2.6.18-4-amd64:
  linux-image-2.6.18-4-amd64/preinst/bootloader-initrd-2.6.18-4-amd64: true
  linux-image-2.6.18-4-amd64/preinst/overwriting-modules-2.6.18-4-amd64: true
  linux-image-2.6.18-4-amd64/preinst/elilo-initrd-2.6.18-4-amd64: true
  linux-image-2.6.18-4-amd64/preinst/abort-install-2.6.18-4-amd64:
  linux-image-2.6.18-4-amd64/prerm/would-invalidate-boot-loader-2.6.18-4-amd64: true



Reply to: