Currently we can specify the testing filesytems like 'check -xfs', but
btrfs is not support in this kind of command option. Add the option
'check -btrfs' support.
Signed-off-by: Wang Sheng-Hui shh...@gmail.com
---
check |2 ++
1 file changed, 2 insertions(+)
diff --git a/check b/check
Signed-off-by: Miao Xie mi...@cn.fujitsu.com
---
fs/btrfs/inode.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
index 590c274..65ae1cb 100644
--- a/fs/btrfs/inode.c
+++ b/fs/btrfs/inode.c
@@ -7136,7 +7136,6 @@ static void
do not print uuid 0 when printing root item
Actually I think we should print all the UUIDs unconditionally. This is
inside the debug-tree utility and a zero uuid is an information that may
be useful, even if only as one of the results 'grep uuid'. I don't see
much point in hiding information
We have an optimization that will go ahead and cache no acls on an inode if
there are no xattrs on the inode. This saves us a lookup later to check the
acls for writes or any other access. The problem is I use selinux so I always
have an xattr on inodes, so make this test a little smarter and
Quoting Dave Jones (2013-06-17 14:58:10)
On Mon, Jun 17, 2013 at 02:42:27PM -0400, Chris Mason wrote:
Quoting Dave Jones (2013-06-17 14:20:06)
On Mon, Jun 17, 2013 at 01:39:42PM -0400, Chris Mason wrote:
Quoting Dave Jones (2013-06-17 09:49:55)
Hit this while running this
On Wed, Jun 19, 2013 at 02:02:33PM -0400, Chris Mason wrote:
Quoting Dave Jones (2013-06-17 14:58:10)
On Mon, Jun 17, 2013 at 02:42:27PM -0400, Chris Mason wrote:
Quoting Dave Jones (2013-06-17 14:20:06)
On Mon, Jun 17, 2013 at 01:39:42PM -0400, Chris Mason wrote:
Quoting
Quoting Dave Jones (2013-06-19 14:34:50)
On Wed, Jun 19, 2013 at 02:02:33PM -0400, Chris Mason wrote:
Quoting Dave Jones (2013-06-17 14:58:10)
On Mon, Jun 17, 2013 at 02:42:27PM -0400, Chris Mason wrote:
Quoting Dave Jones (2013-06-17 14:20:06)
On Mon, Jun 17, 2013 at
Don't emit OOM warnings when k.alloc calls fail when
there there is a v.alloc immediately afterwards.
Converted a kmalloc/vmalloc with memset to kzalloc/vzalloc.
Signed-off-by: Joe Perches j...@perches.com
---
drivers/block/drbd/drbd_bitmap.c | 2 +-
There are all of these checks in the ENOSPC code to see if committing the
transaction would free up enough space to make the allocation. This is because
early on we just committed the transaction and hoped and prayed, which resulted
in cases where it took _forever_ to get an ENOSPC when we really
Hi,
here's an update on my situation.
On Tue, 2013-06-18 at 14:11 +0200, Michael Zugelder wrote:
Anyway, I tried using btrfsck from Josef Bacik's tree (commit f392a28d,
git://github.com/josefbacik/btrfs-progs.git) and it doesn't crash.
Output is this:
Checking filesystem on
On Jun 19, 2013, at 5:55 PM, John Haller john.h.hal...@gmail.com wrote:
It appears that devid 1 was never balanced. Note that the drive
numbers are different because I still have the backup device connected
which had the originals of corrupted files. The filesystem started
with devid 1, was
Hi Chris,
On Tue, 18 Jun 2013, Chris Mason wrote:
[...]
Very long way of saying I think we're one release_path short. Sage, I
haven't tested this at all yet, I was hoping to trigger it first.
diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c
index c276ac9..c1954b3 100644
---
12 matches
Mail list logo
