Excerpts from Andreas Dilger's message of 2011-03-15 18:06:49 -0400:
> On 2011-03-15, at 2:57 PM, Christoph Hellwig wrote:
> > On Tue, Mar 15, 2011 at 04:26:50PM -0400, Chris Mason wrote:
> >> #define FS_EXTENT_FL 0x0008 /* Extents */
> >> #define FS_DIRECTIO_FL 0x0010 /* Us
On 2011-03-15, at 2:57 PM, Christoph Hellwig wrote:
> On Tue, Mar 15, 2011 at 04:26:50PM -0400, Chris Mason wrote:
>> #define FS_EXTENT_FL 0x0008 /* Extents */
>> #define FS_DIRECTIO_FL 0x0010 /* Use direct i/o */
>> +#define FS_NOCOW_FL 0x0080 /* Do not cow fil
On Tue, Mar 15, 2011 at 04:26:50PM -0400, Chris Mason wrote:
> Excerpts from liubo's message of 2011-03-03 03:35:42 -0500:
I'm fine with it. I'll defer the check for conflicts with extN-specific flags
to Ted, though.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
th
Excerpts from liubo's message of 2011-03-03 03:35:42 -0500:
>
> For datacow control, the corresponding inode flags are needed.
> This is for the following patch.
>
> Signed-off-by: Liu Bo
> ---
> include/linux/fs.h |2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/
Currently if we have corrupt metadata map_extent_buffer will complain about it,
but not return an error so the caller has no idea a problem was hit. Fix this.
Thanks,
Signed-off-by: Josef Bacik
---
fs/btrfs/extent_io.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/fs/
On Tue, Mar 15, 2011 at 12:58:43PM -0400, Chris Mason wrote:
> Excerpts from Leon Meßner's message of 2011-03-14 20:28:56 -0400:
> > Hi,
> >
> > i'm having a problem with a damaged btrfs after power loss. When i try
> > to mount the fs mount either segfaults (trace at bottom) or hangs in
> > "D"
Excerpts from Leon Meßner's message of 2011-03-14 20:28:56 -0400:
> Hi,
>
> i'm having a problem with a damaged btrfs after power loss. When i try
> to mount the fs mount either segfaults (trace at bottom) or hangs in
> "D" state together with [btrfs-transacti]. I tried to btrfsck the
> filesyst
This patch is based on the scrub v3 patch. It mainly fixes a problem where
a transaction commit led to a rescrub of the current chunk. Also fixed:
- each EIO leaked a bio
- the BIO_UPTODATE check was wrong
- removed some trailing whitespace
Thanks to Ilya Dryomov and Jan Schmidt for pointing th
Hubert Kario wrote:
> btrfs is supposed to be an ext3/4 replacement
Maybe not just yet. :)
//Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sunday, March 13, 2011 00:53:00 Ric Wheeler wrote:
> On 03/12/2011 05:49 PM, Spelic wrote:
> > On 03/10/2011 02:02 PM, Chris Mason wrote:
> >> Cutting the power isn't problem unless you're using something
> >> where cache flushes are not supported.
> >
> > Some disks lie about cache flush havin
10 matches
Mail list logo