On Sat, Oct 26, 2013 at 11:35 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > On Oct 26, 2013, at 1:46 PM, Igor M <igork20@xxxxxxxxx> wrote: >> >> # mount -t btrfs -o compress=lzo,compress-force=lzo / > > Why do you have two compression mount options? You need to pick one of these. I removed one. I was thinking both were needed. > >> What to do ? > > Are there any kernel messages reported by dmesg at the time the copy starts and fails? What's the exact copy command you're using? No messages. Just whem mounting: device fsid c0bfcb22-8b7c-4936-afcd- 7acdf58f1d6c devid 1 transid 622 /dev/sdb btrfs: force lzo compression btrfs: disk space caching is enabled I even added enospc_debug mount option, still no messages. I'm using simple cp command: # cp -a /mnt/old_hd/data/gbdata/* /usr/local/mysql/data/gbdata/ or for one file # cp -a /mnt/old_hd/data/gbdata/parts_0016.MYD /usr/local/mysql/data/gbdata/ cp: writing ‘/usr/local/mysql/data/gbdata/parts_0016.MYD’: No space left on device cp: failed to extend ‘/usr/local/mysql/data/gbdata/parts_0016.MYD’: No space left on device It's the same error if I try to copy for ex. with midnight commander. On Sat, Oct 26, 2013 at 11:35 PM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > On Oct 26, 2013, at 1:46 PM, Igor M <igork20@xxxxxxxxx> wrote: >> >> # mount -t btrfs -o compress=lzo,compress-force=lzo / > > Why do you have two compression mount options? You need to pick one of these. > >> What to do ? > > Are there any kernel messages reported by dmesg at the time the copy starts and fails? What's the exact copy command you're using? > > > Chris Murphy -- 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
