On Tue, Mar 11, 2014 at 10:59:32PM +0000, Richard W.M. Jones wrote: > On Tue, Mar 11, 2014 at 05:08:19PM -0500, Eric Sandeen wrote: > > blktrace is probably the place to start. Do you see discard > > requests? then ext4 is doing its job. If not, we can trace > > ext4 to see why it's not issuing them, assuming there really > > is work to do. > > At the moment I can't get this to work. The script I'm using is: > > ---------------------------------------------------------------------- > set -e > set -x > trace-cmd record -e all -o /tmp/trace & > pid=$! > fstrim /sysroot > kill $pid; sleep 2 > trace-cmd report -i /tmp/trace > ---------------------------------------------------------------------- I got it to work by using: ---------------------------------------------------------------------- set -e set -x trace-cmd record -e all fstrim /sysroot trace-cmd report ---------------------------------------------------------------------- The output is absolutely huge and I didn't capture it. However just the act of doing the tracing *caused* the trim to happen properly in the underlying disk. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top -- 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
