dump cannot dump ext4 partitions

Bug #325346 reported by Ralf Hildebrandt
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
dump (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: dump

dump can dump ext2 and ext3, but ext4 fails with:

# /sbin/dump -b 1024 -0 -u -f - /dev/sda5
  DUMP: Date of this level 0 dump: Wed Feb 4 16:32:37 2009
  DUMP: Dumping /dev/sda5 (/home) to standard output
  DUMP: Unsupported feature(s) 0x40 in filesystem
/dev/sda5: Filesystem has unsupported feature(s) while opening filesystem
  DUMP: The ENTIRE dump is aborted.

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :

Strictly speaking is "dump" for ext2 only, BUT it also dumps ext3 - thus "4.4bsd dump and restore for ext2 filesystems" is a bit of a misnomer.
Since it dumps both ext2 and ext3, it should also dump ext4.

Revision history for this message
Jeff Balderson (jbalders) wrote :

Dump *will* now make dumps of an ext4 without complaining using dump v0.4b41-6 (Jaunty)

Unfortunately, restoring the data shows that it's been corrupted somewhere in the process (either dump or restore). The data doesn't even remotely resemble the original.

100% reproducibility. Steps to reproduce:

1) Create an ext4 filesystem and mount on /mnt/test
2) Create a simple text file on the filesystem: /mnt/test/testfile.txt
3) "dump -0f /mnt/backup/testbackup.dmp /mnt/test"
4) mkdir /mnt/backup/test; cd /mnt/backup/test
5) "restore -rf /mnt/backup/testbackup.dmp"
6) inspect /mnt/backup/test/testfile.txt to see corrupted data.

Dump should either correctly dump an ext4 or refuse to do so entirely. In the current state, it could be lulling admins into a false sense of security that their data is backed up.

Revision history for this message
udippel (udippel) wrote :

Support this request!
Is there any chance to vote for this?
I have been using dump up and down for ages; I barely remember another utility.

Please, give us dump for Karmic and beyond!

Revision history for this message
Mattia Rizzolo (mapreri) wrote :

I tried this today (version: 0.4b44-1ubuntu1), and it seems working well.
Can you please try out this now?

I mark this bug as incomplete, but if you have something to complain about, please don't hesitate to mark this back to "Confirmed".

Changed in dump (Ubuntu):
status: New → Incomplete
Revision history for this message
Ryddan (anders-ryddan) wrote : Re: [Bug 325346] Re: dump cannot dump ext4 partitions

Hi

I have tried it also now. Seems to work fine.

Regards,
Anders

2013/9/19 Mattia Rizzolo <email address hidden>

> I tried this today (version: 0.4b44-1ubuntu1), and it seems working well.
> Can you please try out this now?
>
> I mark this bug as incomplete, but if you have something to complain
> about, please don't hesitate to mark this back to "Confirmed".
>
> ** Changed in: dump (Ubuntu)
> Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/325346
>
> Title:
> dump cannot dump ext4 partitions
>
> Status in “dump” package in Ubuntu:
> Incomplete
>
> Bug description:
> Binary package hint: dump
>
> dump can dump ext2 and ext3, but ext4 fails with:
>
> # /sbin/dump -b 1024 -0 -u -f - /dev/sda5
> DUMP: Date of this level 0 dump: Wed Feb 4 16:32:37 2009
> DUMP: Dumping /dev/sda5 (/home) to standard output
> DUMP: Unsupported feature(s) 0x40 in filesystem
> /dev/sda5: Filesystem has unsupported feature(s) while opening filesystem
> DUMP: The ENTIRE dump is aborted.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/dump/+bug/325346/+subscriptions
>

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for dump (Ubuntu) because there has been no activity for 60 days.]

Changed in dump (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.