On 07/04/12 13:04, Alexander Block wrote:
On Wed, Jul 4, 2012 at 9:56 AM, Li Zefan lize...@huawei.com wrote:
On 2012/7/4 15:18, chandan r wrote:
This patch adds a new member to the 'struct btrfs_inode' structure to hold
the file creation time.
Well, how do users use this file creation
The following message contained restricted attachment(s) which have been
removed:
From : linux-btrfs@vger.kernel.org
To: bh...@vista.gov.vn
Subject : bh...@vista.gov.vn
Message-ID:
Attachment(s) removed:
-
mail.zip (mail.scr)
--
To
Hi Josef,
I guess I am missing something, but I thought btrfs_next_leaf() should
just jump to the next leaf (or item, if it was added meanwhile)
irrespective of the key that is in the last slot of the current leaf.
The change you added is effective when there is a next leaf, but you
refuse to go
Status reports of the checking process should be printed to stdout
instead of stderr, as that is normal program output and not related to
problems in btrfsck. This patch changes this behaviour and adds the
output Done! after each of the parts.
Signed-off-by: Dieter Ries m...@dieterries.net
---
In the first line of version.sh, $v was set to Btrfs vx.yy, and in
the end Btrfs $v was echoed to the version.h file. This resulted in
the version string Btrfs Btrfs vx.yy. This patch removes the second
occurrence of Btrfs.
Signed-off-by: Dieter Ries m...@dieterries.net
---
version.sh |2 +-
This patch makes btrfsck print the filesystem, which is to be checked,
to stdout. This should be helpful when analyzing (copied and pasted)
output of btrfsck.
Signed-off-by: Dieter Ries m...@dieterries.net
---
btrfsck.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git
Hi,
this patch series implements some mainly cosmetic changes to
btrfs-progs, most in btrfsck.
As this is my first contribution here, I'd kindly ask you for feedback,
and if work like this is appreciated in general.
Cheers,
Dieter
Dieter Ries (3):
btrfs-progs: Remove redundant Btrfs string
On Sun, Sep 30, 2012 at 12:26:36AM +0200, Adam Ryczkowski wrote:
I was using this btrfs file system on kernel 3.6 rc4 and rc5 and 3.5.4 on
Mint 13 (which is based on Ubuntu 12.04). Now, I found the following output
of btrfsck /dev/sda8 (which was of course off-line at that time):
checking
Hi again,
On Sun, Sep 30, 2012 at 11:11:10AM +0900, Itaru Kitayama wrote:
This is the correct one.
Signed-off-by: Itaru Kitayama kitay...@cl.bb4.ne.jp
diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c
index efb044e..c032dbe 100644
--- a/fs/btrfs/extent-tree.c
+++
On Fri, Sep 28, 2012 at 11:02:39AM +0800, Robin Dong wrote:
From: Robin Dong san...@taobao.com
--- a/mkfs.c
+++ b/mkfs.c
@@ -1201,6 +1201,27 @@ static int zero_output_file(int out_fd, u64 size, u32
sectorsize)
return ret;
}
+static int check_leaf_or_node_size(u32 size, u32
On Fri, Sep 28, 2012 at 11:02:40AM +0800, Robin Dong wrote:
From: Robin Dong san...@taobao.com
Using mkfs.btrfs like:
mkfs.btrfs -b 1048576 /dev/sda
will report error:
mkfs.btrfs: volumes.c:796: btrfs_alloc_chunk: Assertion `!(ret)' failed.
Aborted
because the
On Mon, Sep 24, 2012 at 08:36:47AM -0600, cwillu wrote:
For what it's worth, rmdir's behaviour is to continue after errors
(i.e., mkdir 1; mkdir 3; rmdir 1 2 3 deletes 1 and 3, and exits with
a non-zero exit code); unless there's a good reason to do otherwise,
matching that behaviour is
On Sat, Sep 29, 2012 at 04:07:47PM +0800, Robin Dong wrote:
From: Robin Dong san...@taobao.com
When building btrfs from kernel code, it will report:
fs/btrfs/extent_io.h:281: warning: 'extent_buffer_page' declared inline
after being called
fs/btrfs/extent_io.h:281: warning:
On Sat, Sep 29, 2012 at 04:07:46PM +0800, Robin Dong wrote:
From: Robin Dong san...@taobao.com
The function btrfs_insert_some_items() would not be called by any other
functions,
so remove it.
Signed-off-by: Robin Dong san...@taobao.com
Ok from me, thanks.
david
--
To unsubscribe from
On Fri, Sep 28, 2012 at 08:56:33PM +0800, Anand jain wrote:
From: Anand Jain anand.j...@oracle.com
[PATCH] Btrfs-progs: end user may like full path for the subvol list
display
Sure, why not, but please make it optional, eg. with --full-subvol-path
or similar ugly command line option :)
There
Hi David,
Thank you for your comments. I wanted to fix a lockdep warning on a
possible deadlock
case encountered during the xfstests with a scratch space almost full.
You are right I encountered the worst scenario you described below, I
drop this patch and
I'll look at btrfs_congested_fn more to
On Tue, Sep 25, 2012 at 01:02:39PM -0400, Josef Bacik wrote:
implemented as follows on top of next/master, in short:
* disable overcommit completely
* do the optimistically best guess for the metadata and reserve only up
to the current tree height
So I had tried to do this before, the
17 matches
Mail list logo
