>> You are able to read all the journald files, aren't you? You are running >> cp -r so it looks like so. > > IO errors can also cause a process to hang, and enter the dreaded "D" > state. It varies. Sometimes it hangs as a D-state process; sometimes it explicitly says 'segmentation fault' and other times it just says 'bus error (core dumped)'. Also cp -r does die with exit status 1 and errors /bin/cp: error reading 'journal/8ba8e3a22718630e590610ed000007dc/system@81fd64a9006446f2af954d739934edeb-0000000000073a5b-0004f09d7cc446d8.journal': Input/output error /bin/cp: failed to extend 'journal-new/8ba8e3a22718630e590610ed000007dc/system@81fd64a9006446f2af954d739934edeb-0000000000073a5b-0004f09d7cc446d8.journal': Input/output error Most of the files are copied though and everything works fine afterward.
