On Tue, Jul 01, 2014 at 07:43:46PM +0200, David Sterba wrote:
(only nitpick: is 'X' ever reported by lsattr on btrfs? If so,
it could/should still be included)
I'll take a look and will keep 'X' if it's visible somewher.
For the record, with sufficiently new e2fsprogs 'X' appears if the
On Fri, Jun 27, 2014 at 11:38:10AM -0500, Eric Sandeen wrote:
From the btrfs side, we have the object properties that make a nice
interface for accessing the file attributes in parallel with the chattr
tool. The interface is currently underused so it's not possible to
manipulate the flags
On Thu, Jun 26, 2014 at 03:38:33PM -0500, Eric Sandeen wrote:
+FILE ATTRIBUTES
+---
+The btrfs filesystem supports setting the following file
+attributes the `chattr`(1) utility
+append only (a), no atime updates (A), compressed (c), no copy on write (C),
+no dump (d),
On 6/27/14, 8:42 AM, David Sterba wrote:
On Thu, Jun 26, 2014 at 03:38:33PM -0500, Eric Sandeen wrote:
+FILE ATTRIBUTES
+---
+The btrfs filesystem supports setting the following file
+attributes the `chattr`(1) utility
+append only (a), no atime updates (A), compressed (c), no
On 6/27/14, 10:30 AM, David Sterba wrote:
On Fri, Jun 27, 2014 at 09:56:10AM -0500, Eric Sandeen wrote:
* and 'X' does not mean no compression and never has, although I'd
like to see a chattr bit for that because we have the corresponding
inode bit
Ok, then I'm not sure what it does
On 6/27/14, 11:10 AM, David Sterba wrote:
On Fri, Jun 27, 2014 at 10:36:54AM -0500, Eric Sandeen wrote:
...
btrfs tries to handle a flag value which is identical to the
'X' flag value, which lsattr/chattr says is readonly...
I'm looking at it from the kernel side, ie what's its meaning of
The chattr(1) manpage suffers from the same problems mount(1)
had: many options listed, not kept up to date for various
filesystems.
I've submitted a manpage update for chattr(1) which says to
refer to filesystem-specific manpages for supported attributes;
this patch updates btrfs(5) to list the