Your message dated Thu, 27 Apr 2017 09:12:03 +0200 with message-id <6a625bf1-0523-a766-ae34-5efe436fa...@physik.fu-berlin.de> and subject line Re: /bin/dd: dd writes ISO image to non-existent device and after connected some programs don't detect it. has caused the Debian Bug report #861279, regarding /bin/dd: dd writes ISO image to non-existent device and after connected some programs don't detect it. 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 ow...@bugs.debian.org immediately.) -- 861279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: coreutils Version: 8.26-3 Severity: critical File: /bin/dd Tags: d-i Justification: breaks unrelated software Dear Maintainer, I wanted to burn a Fedora ISO image to a USB flash drive for testing using the dd command. However, I typed the command into the terminal before plugging the flash drive. dd showed as if it had recorded the data, although there was nothing plugged: ------------------------------------------------------------- # dd if=Fedora-Workstation-Live-x86_64-25-1.3.iso of=/dev/sdb 2813952+0 records in 2813952+0 records out 1440743424 bytes (1,4 GB, 1,3 GiB) copied, 2,30878 s, 624 MB/s ------------------------------------------------------------- After that, I plugged the flash drive and ran the command again. dd shows as if the data had been recorded (same output shown above), but nothing happened. I tried to see if I could list the device using "# fdisk -l" but it does not appear; However, the nautilus file manager mounts the flash drive and displays it with the ISO image label. It is possible to write data by nautilus but nothing happens using dd. After a few failed attempts I went to dismount the USB flash in nautilus but appear the following error message: ------------------------------------------------------------- Error ejecting /dev/sdb: Command-line `eject "/dev/sdb"' exited with non-zero exit status 1: eject: tried to use `/dev/sdb' as device name but it is no block device eject: tried to use `.//dev/sdb' as device name but it is no block device eject: unable to find or open device for: `/dev/sdb' ------------------------------------------------------------- -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages coreutils depends on: ii libacl1 2.2.52-3+b1 ii libattr1 1:2.4.47-2+b2 ii libc6 2.24-10 ii libselinux1 2.6-3+b1 coreutils recommends no packages. coreutils suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---Hi Klebson! There is no bug here, you are just ignoring the fact that dd works on files, not devices. Hence, if your command is: dd if=bla.img of=/dev/sdb and the device /dev/sdb doesn't exist yet, dd will just create a file with that name which is perfectly fine. The error message that 'eject' spit out is just a result of this. If you run "ls -l /dev/sdb", then you'll notice that your sdb file is missing the "b" flag: root@ikarus:~# ls -l /dev/sda brw-rw---- 1 root disk 8, 0 Apr 20 21:23 /dev/sda root@ikarus:~# ls -l /dev/sdb -rw-r--r-- 1 root root 16375808 Apr 27 09:10 /dev/sdb root@ikarus:~# dd is behaving as expected and I am therefore closing this bug. Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--- End Message ---
