Btrfs devel - Oct 2012 - unrecognized mount option 'compression=lzo' and defragment -c errors

Hi,

I planned to boost my btrfs performance today. here some errors I met:

my ''btrfs filesystem show'' result:

~ # btrfs filesystem show
failed to read /dev/sr0
Label: none  uuid: 9b9aa9d9-760e-445c-a0ab-68e102d9f02e
        Total devices 1 FS bytes used 36.59GB
        devid    1 size 49.52GB used 49.52GB path /dev/sda6

Label: none  uuid: 559dec06-4fd0-47c1-97b8-cc4fa6153fa0
        Total devices 1 FS bytes used 135.48GB
        devid    1 size 293.56GB used 293.56GB path /dev/sda5

Btrfs v0.19+

my btrfs packages:

* kernel moudule: btrfs-git from mason''s repo, 20121010

* btrfsprogs: 0.19

and my /etc/fstab:

UUID=9b9aa9d9-760e-445c-a0ab-68e102d9f02e /                    btrfs
   defaults,compression=lzo,space_cache,io_cache,comment=systemd.automount
             1 0

UUID=559dec06-4fd0-47c1-97b8-cc4fa6153fa0 /home                btrfs
    defaults,space_cache,comment=systemd.automount              1 0

my btrfs partitions are made in 2011.11, before kernel 3.2 is
released.( is that related? like the previous space_cache issue?)

1. I also added mount option ''compression=lzo'' and
''io_cache'' to /home at first.

then "cannot enter home directory. using ./" in KDE it shows the kdm
login(I used autologin, which should boot directly into the desktop)

and "call to lnusetemp failed.(temporary directories full?) check your
installtion" when I clicked okay.

I checked dmesg log, found it didn''t recogonized my
"compression=lzo" option:

[    7.726768] device fsid 9b9aa9d9-760e-445c-a0ab-68e102d9f02e devid
1 transid 359535 /dev/sda6
[    7.727555] btrfs: disk space caching is enabled
[    9.260024] btrfs: unrecognized mount option
''compression=lzo''

and multiple:

[  232.314220] device fsid 559dec06-4fd0-47c1-97b8-cc4fa6153fa0 devid
1 transid 523509 /dev/sda5
[  232.314744] btrfs: unrecognized mount option
''compression=lzo''
[  232.314816] btrfs: open_ctree failed

outputs.

so I removed them from /home. now I can boot. but it still complains:

btrfs: unrecognized mount option ''io_cache''

for /.

2. After I logged in, I switched to root:

~# umount -o remount,compression="lzo" /dev/sda5 /home

I thought it was mounted with compression enabled, (but actually its
not, before I reported here. I checked dmesg, there''s an entry
4800.xxxxx which should be my second home mount, with unrecognized
compression=lzo either)

so I wanted to make all my existing files compressed. I googled, and
found a post on Ocale.com said:

~# btrfs filesystem -c

"The defragment command has an option -c that lets you specify zlib or
lzo". but it was not true according to:

http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg07563.html

Mason said -c only force compression. so how can I specify compression method?

what''s more, defragment tool always returns:

~ # btrfs filesystem defragment -c /dev/sda5
ERROR: defrag range ioctl not supported in this kernel, please try
without any options.
total 1 failures

~ # btrfs filesystem defragment -c /home
failed to open /home
open:: No such device
total 1 failures

I''m confused. no solution found through google for the first message.
and if we can defragment a file like /home/marguerite/100m.zip, why
/home failed to open?

Thanks for help

Marguerite
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

> 1. I also added mount option ''compression=lzo'' and
''io_cache'' to /home at first.
Neither io_cache nor compression=lzo are options that exist.  You
probably meant compress=lzo for the first, but I really don''t know
what you wanted for io_cache (inode_cache?  that''s not really a
performance thing)

You need to check what the actual parameters are before you change
things.  Making stuff up simply doesn''t work.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

On Sun, Oct 21, 2012 at 8:44 AM, cwillu <cwillu@cwillu.com>
wrote:
> Neither io_cache nor compression=lzo are options that exist.  You
> probably meant compress=lzo for the first, but I really don''t know
> what you wanted for io_cache (inode_cache?  that''s not really a
> performance thing)
>
> You need to check what the actual parameters are before you change
> things.  Making stuff up simply doesn''t work.
Hi, cwillu,

I''m glad you show up immediately.

yes, you''re true. I was making up options. that''s why I got
those errors.

I checked:

/dev/mapper/vgCASRV0104-data /mnt/btrfs btrfs
rw,relatime,compress=lzo,space_cache,inode_cache 0 0

http://www.spinics.net/lists/linux-btrfs/msg19804.html

these are the right options.

thanks

Marguerite
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Hi, cwillu,

I have my filesystems mounted with compress=lzo and inode_cache.

now the only problem is, I can''t "btrfs filesystem defragment -c
/dev/sda5" which says:

earth:/home/marguerite # btrfs filesystem defragment -clzo /dev/sda5
ERROR: defrag range ioctl not supported in this kernel, please try
without any options.
total 1 failures

Thanks

Marguerite
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html