https://bugzilla.novell.com/show_bug.cgi?id=818373 https://bugzilla.novell.com/show_bug.cgi?id=818373#c1 Jan Kara changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jack@suse.com AssignedTo|jack@suse.com |dsterba@suse.com --- Comment #1 from Jan Kara 2013-05-06 13:07:07 UTC --- I guess this is more for David than for me - it looks like btrfs specific issue... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=818373 https://bugzilla.novell.com/show_bug.cgi?id=818373#c3 Sven Hartrumpf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hartrumpf@gmx.net --- Comment #3 from Sven Hartrumpf 2013-05-06 17:58:51 UTC --- (In reply to comment #2)

Trying to replicate the problem, I did a quick test on a test partition of mine (12.3 VM). I get that error on symlinks, normal files are accepted.

The files that cause errors are not soft links. (I removed them, see the "find" command above.) In a separate test set, 2467 of 277000 text files failed.

I pointed this to the OP in the forum where he asked first, but got no response from him

Now answered, forum software did not email me:-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=818373 https://bugzilla.novell.com/show_bug.cgi?id=818373#c4 --- Comment #4 from Sven Hartrumpf 2014-03-06 11:43:30 UTC --- Just to share some more information: This bug also affects openSUSE 13.1 and Kernel:Stable (3.13.5-1.g4e9ddcc-default). Should I open a new bug against openSUSE 13.1? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=818373 https://bugzilla.novell.com/show_bug.cgi?id=818373#c6 Filipe Manana changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fdmanana@suse.com --- Comment #6 from Filipe Manana 2014-08-13 18:28:08 UTC --- This fails because chattr +c calls the getflags ioctl to get the current flags, which include FS_NOCOMP_FL because the file isn't compressible as David said, and adds the requested flags (+c) to the flags it got. Finally it calls the setflags ioctl with flags == (FS_NOCOMP_FL | FS_COMPR_FL). The btrfs ioctl returns with EINVAL in ioctl.c:check_flags(): if ((flags & FS_NOCOMP_FL) && (flags & FS_COMPR_FL)) return -EINVAL; If you try calling chattr =c instead, it won't OR the current flags with the requested flags, and whence no error returned. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=818373 https://bugzilla.novell.com/show_bug.cgi?id=818373#c8 --- Comment #8 from Filipe Manana 2014-08-13 19:51:09 UTC --- One last finding... So it turns out lsattr can show the FS_NOCOMP_FL flag, with the letter 'X' representing it, if and only if e2fsprogs was built with compression enabled (i.e. ./configure --enable-compression), in which case we get something like this: root 21:21:08 /mnt/sdd > /home/fdmanana/tmp/e2/e2fsprogs-1.42.11/misc/lsattr -v ./bin/ipod-time-sync AQUI flags: 400 6 -----------X-------- ./bin/ipod-time-sync root 21:21:19 /mnt/sdd > But the flag FS_COMPR_FL is always displayed if set, regardless of building with --enable-compression or not. Equally confusing, is the long name of the the FS_NOCOMP_FL flag: http://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/tree/lib/e2p/pf.c#n30 "Compression_Raw_Access" not something like "compression disabled" for example. To note as well that using --enable-compression causes the build to emit several warnings telling that compression support is experimental, probably why most distros at least don't seem to build with it (even thought this experimental status applies to extN only). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=818373 https://bugzilla.novell.com/show_bug.cgi?id=818373#c10 --- Comment #10 from Filipe Manana 2014-08-14 15:04:14 UTC --- Thanks Jan. Jeff has a patch that updates the documentation and makes lsattr show X (FS_NOCOMP_FL) regardless of building with or without --enable-compression. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.