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

Bug#442508: marked as done (coreutils: dd demolishes my computer)

Your message dated Sat, 8 Jun 2013 12:16:25 +0200
with message-id <20130608101625.GD4796@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #442508,
regarding coreutils: dd demolishes my computer
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.)


-- 
442508: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=442508
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: coreutils
Version: 5.97-5.3
Severity: normal


Hi,

first, I'd like to note that I report this problem against the coreutils
package because I don't really know where else to report it
(linux-image-something?).

Secondly, the problem description:

I recently had to create a big file, and ran this:

# dd if=/dev/zero of=/srv/xen/disks/vm1.xm obs=1024K count=20000 seek=10000 conv=notrunc

The effect, apart from growing the file to an unspecified size (it came
out at 31G instead of 20), this brought my machine into an unsusable
state, meaning the machine was unresponsive from the console for about
half an hour at least, and it killed all X related stuff, thus messing
up the display (I didn't find a way to correct this w/o a reboot). Over
the network, the machine was accessible once the dd process was killed
by the kernel. In the kernel log, I find messages like these (exerpt):



Sep 16 14:26:56 debian kernel: DMA: 265*4kB 159*8kB 1*16kB 1*32kB 1*64kB 1*128kB 1*256kB 1*512kB 1*1024kB 1*2048kB 0*4096kB = 6412kB
Sep 16 14:26:56 debian kernel: DMA32: empty
Sep 16 14:26:56 debian kernel: Normal: empty
Sep 16 14:26:56 debian kernel: HighMem: empty
Sep 16 14:26:56 debian kernel: Swap cache: add 125033, delete 124855, find 11742/20953, race 0+13
Sep 16 14:26:56 debian kernel: Free swap  = 3970792kB
Sep 16 14:26:56 debian kernel: Total swap = 4194296kB
Sep 16 14:26:56 debian kernel: Free swap:       3970792kB
Sep 16 14:26:56 debian kernel: oom-killer: gfp_mask=0x201d2, order=0
Sep 16 14:26:56 debian kernel: 
Sep 16 14:26:56 debian kernel: Call Trace:
Sep 16 14:26:56 debian kernel:  [<ffffffff802a2a0c>] out_of_memory+0x2e/0x180
Sep 16 14:26:56 debian kernel:  [<ffffffff8020fb51>] __alloc_pages+0x220/0x2a9
Sep 16 14:26:56 debian kernel:  [<ffffffff8025e30e>] thread_return+0x5d/0xfc
Sep 16 14:26:56 debian kernel:  [<ffffffff80213012>] __do_page_cache_readahead+0xd4/0x24d
Sep 16 14:26:56 debian kernel:  [<ffffffff80228b79>] sync_page+0x0/0x42
Sep 16 14:26:56 debian kernel:  [<ffffffff88190a46>] :dm_mod:dm_any_congested+0x38/0x3f
Sep 16 14:26:56 debian kernel:  [<ffffffff8819258a>] :dm_mod:dm_table_any_congested+0x46/0x63
Sep 16 14:26:56 debian kernel:  [<ffffffff88190a46>] :dm_mod:dm_any_congested+0x38/0x3f
Sep 16 14:26:56 debian kernel:  [<ffffffff80213878>] filemap_nopage+0x148/0x314
Sep 16 14:26:56 debian kernel:  [<ffffffff80208e14>] __handle_mm_fault+0x65f/0xe85
Sep 16 14:26:56 debian kernel:  [<ffffffff8020ba24>] do_page_fault+0xd9b/0x112f
Sep 16 14:26:56 debian kernel:  [<ffffffff8025e30e>] thread_return+0x5d/0xfc
Sep 16 14:26:56 debian kernel:  [<ffffffff80390b65>] sock_ioctl+0x1c1/0x1e5
Sep 16 14:26:56 debian kernel:  [<ffffffff802417ef>] do_ioctl+0x21/0x6b
Sep 16 14:26:56 debian kernel:  [<ffffffff8025c4d7>] error_exit+0x0/0x6e

I had to reboot in order to get back to a sane working state, but found out,
that I needed one more of these files. This time, instead of using 'dd', I used
'cp' to create a copy, and it worked like a charm, not even slowing my computer
down too much.

The computer in question is an AMD64 X2 machine with 2G RAM and a pair of 250G
SATA2 disks, with everything except /boot inside an encrypted LVM partition
(I'm using dm_crypt).


Best,
--Toni++


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (600, 'stable'), (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-xen-amd64
Locale: LANG=de_DE.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)

Versions of packages coreutils depends on:
ii  libacl1                2.2.41-1          Access control list shared library
ii  libc6                  2.3.6.ds1-13etch2 GNU C Library: Shared libraries
ii  libselinux1            1.32-3            SELinux shared libraries

coreutils recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.0 / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: