Re: [PATCH 1/4] btrfs: correct empty compression property behavior

2014-10-16 Thread Filipe David Manana
On Thu, Oct 16, 2014 at 2:37 AM, Satoru Takeuchi wrote: > Hi David and Chris, > > (2014/09/29 18:36), David Sterba wrote: >> >> On Fri, Sep 19, 2014 at 05:45:49PM +0900, Satoru Takeuchi wrote: >>> >>> In the current implementation, compression property == "" has >>> the two different meanings: one

Re: [PATCH 1/4] btrfs: correct empty compression property behavior

2014-10-15 Thread Satoru Takeuchi
Hi David and Chris, (2014/09/29 18:36), David Sterba wrote: On Fri, Sep 19, 2014 at 05:45:49PM +0900, Satoru Takeuchi wrote: In the current implementation, compression property == "" has the two different meanings: one is with BTRFS_INODE_NOCOMPRESS, and the other is without this flag. So, eve

Re: [PATCH 1/4] btrfs: correct empty compression property behavior

2014-09-29 Thread David Sterba
On Fri, Sep 19, 2014 at 05:45:49PM +0900, Satoru Takeuchi wrote: > In the current implementation, compression property == "" has > the two different meanings: one is with BTRFS_INODE_NOCOMPRESS, > and the other is without this flag. > > So, even if the two files a and b have the same compression >

[PATCH 1/4] btrfs: correct empty compression property behavior

2014-09-19 Thread Satoru Takeuchi
From: Naohiro Aota In the current implementation, compression property == "" has the two different meanings: one is with BTRFS_INODE_NOCOMPRESS, and the other is without this flag. So, even if the two files a and b have the same compression property, "", and the same contents, one file seems to