Lines Matching refs:replay

9 that is in the WRITE requests is copied into the log to make the replay happen
17 next REQ_FLUSH request.  This is to make it easier for userspace to replay the
47 If we logged DISCARD when it completed, the replay would look like this
51 which isn't quite what happened and wouldn't be caught during the log replay.
76 	write, but first you need to replay up to the mkfs to make sure
84 	  This would allow you to replay the log up to the mkfs mark and
85 	  then replay from that point on doing the fsck check in the
93 There is a userspace tool that will replay the log for you in various ways.
114 replay-log --log /dev/sdc --replay /dev/sdb --end-mark fsync
133 replay-log --log /dev/sdc --replay /dev/sdb --end-mark mkfs
135 replay-log --log /dev/sdc --replay /dev/sdb --start-mark mkfs \
138 And that will replay the log until it sees a FUA request, run the fsck command
139 and if the fsck passes it will replay to the next FUA, until it is completed or