Bug 1692742

Summary: [abrt] extundelete: operator new(): extundelete killed by SIGABRT
Product: [Fedora] Fedora Reporter: Paulo Fidalgo <paulo.fidalgo.pt>
Component: extundeleteAssignee: Robert Scheck <redhat-bugzilla>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: redhat-bugzilla, tchollingsworth
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/cffc346c2a8193271be52f3633ab5ee1e5ba163b
Whiteboard: abrt_hash:1430d278a08cf0f1e5861f1406c8c54accd6eba2;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-27 21:39:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Paulo Fidalgo 2019-03-26 10:58:02 UTC 
Description of problem:
I have tried to run it first against a lucks partition on read-only mode, then after failing I've creating a dd image and tried to run 
extundelete --restore-all --after $(date -d "-2 hours" +%s) home.backup

and got the output:

Only show and process deleted entries if they are deleted on or after 1553589531 and before 9223372036854775807.
NOTICE: Extended attributes are not restored.
Loading filesystem metadata ... 1200 groups loaded.
Loading journal descriptors ... malloc(): invalid next size (unsorted)
Aborted (core dumped)

Version-Release number of selected component:
extundelete-0.2.4-13.fc29

Additional info:
reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        extundelete --restore-all --after 1553586295 /dev/mapper/luks-33688525-46fe-4909-86af-844342ec415d
crash_function: operator new
executable:     /usr/bin/extundelete
journald_cursor: s=c49b110047f3435aae6d8562ca94905f;i=344f29;b=42092a333a0e47dfa8da15fdf54137c7;m=211b69627;t=584fc2c808468;x=1451f4077ae4bedd
kernel:         5.0.3-200.fc29.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (4 frames)
 #6 operator new at ../../../../libstdc++-v3/libsupc++/new_op.cc:50
 #7 std::vector<triad<unsigned int, unsigned long long, unsigned long long>, std::allocator<triad<unsigned int, unsigned long long, unsigned long long> > >::_M_realloc_insert<triad<unsigned int, unsigned long long, unsigned long long> > at /usr/include/c++/8/bits/stl_algobase.h:219
 #8 init_journal(struct_ext2_filsys*, struct_ext2_filsys*, journal_superblock_s*) at /usr/include/c++/8/bits/stl_vector.h:1090
 #9 examine_fs at cli.cc:287
Comment 1 Paulo Fidalgo 2019-03-26 10:58:05 UTC 
Created attachment 1547998 [details]
File: backtrace
Comment 2 Paulo Fidalgo 2019-03-26 10:58:06 UTC 
Created attachment 1547999 [details]
File: cgroup
Comment 3 Paulo Fidalgo 2019-03-26 10:58:08 UTC 
Created attachment 1548000 [details]
File: core_backtrace
Comment 4 Paulo Fidalgo 2019-03-26 10:58:09 UTC 
Created attachment 1548001 [details]
File: cpuinfo
Comment 5 Paulo Fidalgo 2019-03-26 10:58:10 UTC 
Created attachment 1548002 [details]
File: dso_list
Comment 6 Paulo Fidalgo 2019-03-26 10:58:11 UTC 
Created attachment 1548003 [details]
File: environ
Comment 7 Paulo Fidalgo 2019-03-26 10:58:12 UTC 
Created attachment 1548004 [details]
File: limits
Comment 8 Paulo Fidalgo 2019-03-26 10:58:13 UTC 
Created attachment 1548005 [details]
File: maps
Comment 9 Paulo Fidalgo 2019-03-26 10:58:14 UTC 
Created attachment 1548006 [details]
File: mountinfo
Comment 10 Paulo Fidalgo 2019-03-26 10:58:16 UTC 
Created attachment 1548007 [details]
File: open_fds
Comment 11 Paulo Fidalgo 2019-03-26 10:58:17 UTC 
Created attachment 1548008 [details]
File: proc_pid_status
Comment 12 Ben Cotton 2019-10-31 19:43:53 UTC 
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
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 EOL if it remains open with a
Fedora 'version' of '29'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.
Comment 13 Ben Cotton 2019-11-27 21:39:18 UTC 
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.