Version-Release number of selected component: f3-2-4.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: f3write /run/media/user/9016-4EF8/ crash_function: measure executable: /usr/bin/f3write kernel: 3.15.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #4 measure at f3write.c:171 #5 create_and_fill_file at f3write.c:318 #6 fill_fs at f3write.c:368
Created attachment 921892 [details] File: backtrace
Created attachment 921893 [details] File: cgroup
Created attachment 921894 [details] File: core_backtrace
Created attachment 921895 [details] File: dso_list
Created attachment 921896 [details] File: environ
Created attachment 921897 [details] File: limits
Created attachment 921898 [details] File: maps
Created attachment 921899 [details] File: open_fds
Created attachment 921900 [details] File: proc_pid_status
Created attachment 921901 [details] File: var_log_messages
Another user experienced a similar problem: simple run f3write to check an USB memory stick. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: f3write /run/media/frank/TUX/ crash_function: measure executable: /usr/bin/f3write kernel: 3.19.3-100.fc20.x86_64 package: f3-2-4.fc20 reason: f3write killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000