some feedbacks seen on btrfs

[Roger Pack <rogerpack2005@gmail.com>]

First off, thanks for an awesome file system, it is working well for
my purposes of compressing a  filesystem on a small VPS.  Woot!

I thought I'd call out a few things (in the hopes of spurring
improvements) I'd seen about btrfs (in case they weren't common
knowledge...):

http://linux.slashdot.org/story/13/04/26/1231213/btrfs-is-getting-there-but-not-quite-ready-for-production
links to
http://www.anchor.com.au/blog/2013/04/the-btrfs-backup-experiment/
which mentions problems when they start to "fill up" a btrfs filesystem.

Also, in the slashdot comments, saw this:
"...nice features, speed ok, but i happened to unplug by mistake the
power supply, without a battery. bad crash... I tried using btrfsck,
and other debug tools, even in the "dangerdon'teveruse" git branch,
they just segfaulted. at the end my filesystem was unrecoverable, I
used btrfs-restore, only to find out that 90% of my files had been
truncated to 0... even files i didn't use for months....now, maybe it
was the compress=lzo option, or maybe I played a little too much with
the repair tools (possible)...
btrfs is supposed to save a consistent state every 30 seconds, so I
don't understand how I messed up that bad.... maybe the superblock was
gone and the btrfsck --repair borked everything, I don't know....
luckily for me: backups :)"

FWIW.
Thanks again!
-roger-