Package: dump Version: 0.4b41-6 Severity: grave Justification: causes non-serious data loss
I've just noticed that dumps that I've been doing last few weeks are completely unusable. And the reason for that is the recent switch of all my filesystems from ext3 to ext4. What is serious about this is that dump doesn't object or print errors/warnings, it happily does it's job (just like before with ext3), so the operator is completely unaware that backups done that way are _completely useless_. It would be great for this to be fixed, but until then, at least dump should refuse to dump ext4 file systems and thus prevent accidental data loss of bigger proportions. -- System Information: Debian Release: 5.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.28 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=C, LC_CTYPE=hr_HR (charmap=ISO-8859-2) Shell: /bin/sh linked to /bin/bash Versions of packages dump depends on: ii e2fslibs 1.41.3-1 ext2 filesystem libraries ii libblkid1 1.41.3-1 block device id library ii libc6 2.7-18 GNU C Library: Shared libraries ii libcomerr2 1.41.3-1 common error description library ii libncurses5 5.7+20090105-1 shared libraries for terminal hand ii libreadline5 5.2-3 GNU readline and history libraries ii libuuid1 1.41.3-1 universally unique id library ii tar 1.20-1 GNU version of the tar archiving u dump recommends no packages. dump suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
