Description of problem: I was trying to trigger a issue in a script using mongodb dump utilitie, so I created a directory ~/tmp/t/ , then cd to it, ran mongodump a first time, then : chattr +i dump/stickshift_broker_dev/* # mongodump connected to: 127.0.0.1 Fri Jan 4 23:06:33 all dbs Fri Jan 4 23:06:33 DATABASE: stickshift_broker_dev to dump/stickshift_broker_dev Fri Jan 4 23:06:33 stickshift_broker_dev.system.users to dump/stickshift_broker_dev/system.users.bson Erreur de segmentation (core dumped) So mongodb crash if we try to write in a directory where it cannot write ( due to chattr +i ) Version-Release number of selected component: mongodb-2.2.2-1.fc18 Additional info: backtrace_rating: 4 cmdline: mongodump crash_function: _IO_new_fclose executable: /usr/bin/mongodump kernel: 3.6.11-3.fc18.x86_64 remote_result: NOTFOUND uid: 0 Truncated backtrace: Thread no. 1 (5 frames) #0 _IO_new_fclose at iofclose.c:54 #1 Dump::writeCollectionFile at src/mongo/tools/dump.cpp:132 #2 Dump::go at src/mongo/tools/dump.cpp:233 #3 Dump::run at src/mongo/tools/dump.cpp:514 #4 mongo::Tool::main at src/mongo/tools/tool.cpp:266
Created attachment 672591 [details] File: backtrace
Created attachment 672592 [details] File: cgroup
Created attachment 672593 [details] File: core_backtrace
Created attachment 672594 [details] File: dso_list
Created attachment 672595 [details] File: environ
Created attachment 672596 [details] File: limits
Created attachment 672597 [details] File: maps
Created attachment 672598 [details] File: open_fds
Created attachment 672599 [details] File: proc_pid_status
Created attachment 672600 [details] File: smolt_data
Created attachment 672601 [details] File: var_log_messages
Did this get fixed with the 2.2.3 update?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.