https://bugzilla.kernel.org/show_bug.cgi?id=78651 --- Comment #15 from Joseph D. Wagner <joe@xxxxxxxxxxxxxxxxxx> --- Assuming these don't change across reboots: 253, 1 -> /dev/dm-1 -> system-os 253, 3 -> /dev/dm-3 -> backup (destination) 253, 5 -> /dev/dm-5 -> data-home (source) I used the same options for formatting. Here are the exact commands: $ mke2fs -E lazy_itable_init=0,lazy_journal_init=0 -J size=1024 -L backup -m 1 -t ext4 -v /dev/mapper/backup $ mke2fs -E lazy_itable_init=0,lazy_journal_init=0 -J size=256 -L backup -m 1 -t ext4 -v /dev/mapper/backup Here is the exact command for the ftrace and dump: $ trace-cmd record -o /root/ftrace/trace.dat \ -e jbd2:jbd2_checkpoint \ -e jbd2:jbd2_run_stats \ dump -${DUMPLEVEL} -a -b 64 -u -A "${TARGET_TOC}" -f "${TARGET_IMG}" -Q "${TARGET_QFA}" "${SNAPSHOT_PATH}" Often (but not always), I would set the system to shutdown immediately after backup. However, it was mounted automatically by /etc/fstab on each boot, and it was left mounted in the background. Prior to submitting these bug report, I had been running without reformatting for a number of months. I just finally got sick of it when I submitted my report. What do you think should be the next step? Reformat with those options, and rerun with a trace? -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
