http://bugzilla.novell.com/show_bug.cgi?id=571841 http://bugzilla.novell.com/show_bug.cgi?id=571841#c1 --- Comment #1 from Heiko Lübbe 2010-02-02 17:01:58 UTC --- I was fallen in the same trap and agree with George that at least the dump utility have to fail to dump an ext4 file system. It is creepy to get no errors, see all files and directory restored and to detect later there is only garbage in the files. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=571841 http://bugzilla.novell.com/show_bug.cgi?id=571841#c3 Martin Mohring changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.mohring@5etech.eu --- Comment #3 from Martin Mohring 2010-06-20 23:20:14 UTC --- I had even more extreme situation. I was using dump (with read only access to the block device) and had created an ext4 fs on a LVM volume. Then I have just tried to check what happens when I do backup using dump. To my surprise: 0. After a while, I get a read error on one of of the Volumes 1. The LVM Volume Group gets destroyed 2. All ext4 filesystems are then lost The only way to get rid of such a LVM is to null it with dd and putting lots of 0 bytes into the underlying partitions. My only explaination for this is that dump somehow tries to read bytes at non existing fs offset. This causes a non recoverable read error, destroying then the mounted filesystem. I though this could never ever happen, because logically dump accesses only with read access. This can only be explained with LVM bug and/or missing error handling in ext4. So keep off of using dump on a ext4 inside a LVM volume. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=571841 http://bugzilla.novell.com/show_bug.cgi?id=571841#c4 Jan Kara changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|NEW |NEEDINFO CC| |nadvornik@novell.com InfoProvider| |martin.mohring@5etech.eu --- Comment #4 from Jan Kara 2010-06-21 11:58:43 UTC --- Well, the problem that dump(8) doesn't quite work with ext4 is a problem in dump itself. Adding dump(8) maintainer to CC. Maybe he could add a check into dump(8) to refuse working with ext4 at least for 11.2. 11.3 should have a new version of dump I suppose. Vlada? Martin, I seriously doubt the problem you saw was caused by dump reading the filesystem. It looks as if some LVM metadata got overwritten, which I'd expect to happen for example when you specify a wrong destination or something like that. Sadly your report does not have too much details. What was the exact command line you run? What was in the system logs? What was your LVM configuration? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=571841 http://bugzilla.novell.com/show_bug.cgi?id=571841#c6 --- Comment #6 from George Deligeirgis 2010-07-29 15:42:59 UTC --- (In reply to comment #5)

Martin, can you provide the information or should I close this bug as NORESPONSE?

Jan, this bug is about dump misbehaving with ext4. Martin made a different point in his post which is in my understanding potentially a different bug. So closing this bug with NORESPONSE is wrong. If you need more info on the original problem feel free to ask for it. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=571841 https://bugzilla.novell.com/show_bug.cgi?id=571841#c8 Humberto Sachs changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hws@txgroup.net --- Comment #8 from Humberto Sachs 2013-09-13 15:30:49 UTC --- YaST fails to restore after system crash. Tested issue twice with Suse 12.3 and Enterprize 11 SP2 & SP3. For reference, see SR 10821897712 originated because Yast was not able to restore the system. The engineer helping me with this SR was most capable, and after attempting several corrective actions the restoration failed. The tag was closed because I got a new registration allowing me to re-install Enterprise in one of my machines. The restoration with YaST freezes as it arrive at a point where a user input is required. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=571841 http://bugzilla.novell.com/show_bug.cgi?id=571841#c10 Vladimir Nadvornik changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from Vladimir Nadvornik --- dump-0.4b44 already supports ext4 -- You are receiving this mail because: You are on the CC list for the bug.