Hi, I have a large (25G) virtual disk on a btrfs fs. Yes, I know this is not optimial. So I try to defrag it from time to time. However, using "btrfs fi defrag -c vm.vdi" results in even more fragments than before (reported by filefrag). So I wrote my own pseudo defragger, ----- #!/bin/sh test -f $1 || exit 2 echo "defrag $1" /usr/sbin/filefrag $1 || exit fallocate -n -l `filesize $1` $1.new || exit chattr +C $1.new dd if=$1 of=$1.new conv=notrunc oflag=append status=none chmod --reference $1 $1.new chown --reference $1 $1.new mv $1.new $1 /usr/sbin/filefrag $1 ----- which produces much better results (ok, the file must not be in use). Somewhere in the 3.17 cycle the resulting image got corrupted using the script above. Running filefrag on it returns "FIBMAP unsupported". Virtualbox returns "AHCI#0P0: Read at offset 606236672 (49152 bytes left) returned rc=VERR_DEV_IO_ERROR". No errors in the kernel log. Trying "cp vm.vdi /dev/null" returns: cp: Error reading „vm.vdi“: IO-Error kernel 3.17-rc7 btrfs 3.17.x mount options: rw,nodiratime,relatime,compress=lzo,space_cache,autodefrag Marc -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
