Lines Matching refs:log
2 dm-log-writes
5 This target takes 2 devices, one to pass all IO to normally, and one to log all
9 able to take arbitrary data from userspace to insert into the log. The data
10 that is in the WRITE requests is copied into the log to make the replay happen
16 We log things in order of completion once we are sure the write is no longer in
19 the log in a way that correlates to what is on disk and not what is in cache,
24 the FLUSH request completes we log all of the WRITEs and then the FLUSH. Only
31 The log would show the following:
52 which isn't quite what happened and wouldn't be caught during the log replay.
59 log-writes <dev_path> <log_dev_path>
63 log_dev_path Device where the log entries are written to.
79 You can use a dmsetup message to set an arbitrary mark in a log.
85 mkfs.btrfs -f /dev/mapper/log
86 dmsetup message log 0 mark mkfs
89 This would allow you to replay the log up to the mkfs mark and
93 Every log has a mark at the end labeled "dm-log-writes-end".
98 There is a userspace tool that will replay the log for you in various ways.
99 It can be found here: https://github.com/josefbacik/log-writes
107 TABLE="0 $(blockdev --getsz /dev/sdb) log-writes /dev/sdb /dev/sdc"
108 dmsetup create log --table "$TABLE"
109 mkfs.btrfs -f /dev/mapper/log
110 dmsetup message log 0 mark mkfs
112 mount /dev/mapper/log /mnt/btrfs-test
114 dmsetup message log 0 mark fsync
118 dmsetup remove log
119 replay-log --log /dev/sdc --replay /dev/sdb --end-mark fsync
127 TABLE="0 $(blockdev --getsz /dev/sdb) log-writes /dev/sdb /dev/sdc"
128 dmsetup create log --table "$TABLE"
129 mkfs.btrfs -f /dev/mapper/log
130 dmsetup message log 0 mark mkfs
132 mount /dev/mapper/log /mnt/btrfs-test
136 dmsetup remove log
138 replay-log --log /dev/sdc --replay /dev/sdb --end-mark mkfs
140 replay-log --log /dev/sdc --replay /dev/sdb --start-mark mkfs \
143 And that will replay the log until it sees a FUA request, run the fsck command