(Note that F12 dump is possibly also affected by this bug, see below.) dump aborts when used in pipe with restore to copy the whole filesystem contents. Reproducible always. Dump should run to completion instead of aborting. Version: [vopicka@ntb tmp]$ rpm -q dump dump-0.4-0.1.b42.fc11.i586 [vopicka@ntb tmp]$ Sample from terminal: [root@ntb x]# dump 0bf 1024 - | restore xf - DUMP: Must specify disk or filesystem DUMP: The ENTIRE dump is aborted. restore: Tape read error on first record [root@ntb x]# dump 0bf 1024 - /boot | restore xf - DUMP: Date of this level 0 dump: Tue Nov 3 11:18:47 2009 DUMP: Dumping /dev/sda3 (/boot) to standard output DUMP: Label: /boot DUMP: Writing 1024 Kilobyte records DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 46808 blocks. DUMP: Volume 1 started with block 1 at: Tue Nov 3 11:18:48 2009 DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 2.19% done, finished in 0:00 set owner/mode for '.'? [yn] y DUMP: Broken pipe DUMP: The ENTIRE dump is aborted. DUMP: error reading command pipe in master: Invalid argument DUMP: The ENTIRE dump is aborted. [root@ntb x]# Thank you in advance to fix this as soon as possibble. Note that dump from F12 development compiled under F11 exhibits exactly the same problem.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The same strange behavior observed today on fully up-to date Fedora12, dump-0.4-0.3.b42.fc12.i686. I am changing Fedora version od this bug to 12 to prevent this bug to be automa[tg]ically closed with F12 EOL.
s/F12/F11/
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Hello. No doubt, this bug is present in F14 release, see below. Dump aborts miserably. Brgds, Ed [root@lin y]# dump 0bf 1024 - /tmp/x | restore xf - DUMP: Date of this level 0 dump: Thu Nov 4 21:16:27 2010 DUMP: Dumping /dev/md0 (/ (dir tmp/x)) to standard output DUMP: Label: / DUMP: Writing 1024 Kilobyte records DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 1166 blocks. DUMP: Volume 1 started with block 1 at: Thu Nov 4 21:16:29 2010 DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: 87.82% done, finished in 0:00 set owner/mode for '.'? [yn] y DUMP: Broken pipe DUMP: The ENTIRE dump is aborted. DUMP: error reading command pipe in master: Invalid argument DUMP: The ENTIRE dump is aborted. [root@lin y]# date Thu Nov 4 21:16:34 CET 2010 [root@lin y]# uname -a Linux lin.local 2.6.35.6-48.fc14.i686.PAE #1 SMP Fri Oct 22 15:27:53 UTC 2010 i686 i686 i386 GNU/Linux [root@lin y]# rpm -q dump dump-0.4-0.8.b43.fc14.i686 [root@lin y]#
This is caused by the fact that you're specifying a non default blocksize to dump (-b 1024), and you do not do the same for restore (adding -b 1024 to the restore arguments will make everybody happy). This looks to me more like an operator error than a bug in dump (although restore could be modified to gracefully handle operator errors...). Stelian.
Unfortunately, I must disagree. The problem appears sporadically even when -b with the same block size is specified on both dump and restore command line. The problem manifests itself only when dump output is piped to restore. If the same filesystem that exhibits the problem with dump|restore pipe is dumped to file and then restored from taht file,there is no problem. Due to the planned switch to btrfs in F16, I am switching from dump/restore to cpio, so resolving the dump|restore problem in now of low importance to me. Brgds, Ed
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping