On Wed, 2014-06-25 at 00:25 -0500, Eric Sandeen wrote:
On 6/25/14, 12:14 AM, Eric Sandeen wrote:
On 6/24/14, 9:22 PM, Gui Hecheng wrote:
On Tue, 2014-06-24 at 21:17 -0500, Eric Sandeen wrote:
On 6/11/14, 9:25 PM, Gui Hecheng wrote:
When run chunk-recover on a health btrfs(data profile
Hi Liu,
(2014/06/24 16:39), Liu Bo wrote:
The reproducer is
$ mkfs.btrfs D1 D2 D3 -mraid5
$ mkfs.ext4 D2 mkfs.ext4 D3
$ mount D1 /btrfs -odegraded
Tested-by: Satoru Takeuchitakeuchi_sat...@jp.fujitsu.com
Here is the result of the last mount.
===
...
mount: wrong fs type, bad option, bad
Will it be possible to use DUP for data as well as for metadata on a
single device?
And if so, am I going to be able to specify more than 1 copy of the data?
Storage is pretty cheap now, and to have multiple copies in btrfs is
something that I think could be used a lot. I know I will use multiple
Hi Satoru,
On Wed, Jun 25, 2014 at 04:25:01PM +0900, Satoru Takeuchi wrote:
Hi Liu,
(2014/06/24 16:39), Liu Bo wrote:
The reproducer is
$ mkfs.btrfs D1 D2 D3 -mraid5
$ mkfs.ext4 D2 mkfs.ext4 D3
$ mount D1 /btrfs -odegraded
Tested-by: Satoru
On Wed, Jun 25, 2014 at 09:25:57AM +0200, Daniel Landstedt wrote:
Will it be possible to use DUP for data as well as for metadata on a
single device?
This has variously been possible and not over the last few years. I
think it's finally come down on the side of not, but by all means try
it
It'll be exactly 2 copies at the moment. Note that performance on
an SSD will at least halve, and performance on a rotational device
will probably suck quite badly. Neither will help you in the case of a
full-device failure. You still need backups, kept on a separate machine.
Write
Hi,
I got these during heavy IO (fs indexing):
[175200.080150] INFO: task akonadi_baloo_i:6489 blocked for more than 480
seconds.
[175200.080160] Not tainted 3.16.0-rc2-12.gfc9498b-desktop+ #2
[175200.080164] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables
this message.
The chunk-recover.c/BTRFS_NUM_MIRRORS in the userspace means
the same thing as ctree.h/BTRFS_MAX_MIRRORS in the kernelspace,
so to stay consistent with the kernelspace, just make this movement
in the userspace:
chunk-recover.c/BTRFS_NUM_MIRRORS
===
Daniel Landstedt posted on Wed, 25 Jun 2014 09:25:57 +0200 as excerpted:
Will it be possible to use DUP for data as well as for metadata on a
single device?
See Hugo's answer for the general case. I've learned a lot from him. =:^)
While I believe and as he says the general answer is no,
On 6/23/14, Martin K. Petersen martin.peter...@oracle.com wrote:
Anyway. The short answer is that Linux will pretty much always do I/O in
multiples of the system page size regardless of the logical block size
of the underlying device. There are a few exceptions to this such as
direct I/O,
On 06/24/2014 06:37 PM, Chris Murphy wrote:
On Jun 24, 2014, at 1:52 AM, Tamas Papp tom...@martos.bme.hu wrote:
On 06/22/2014 07:10 PM, Tamas Papp wrote:
On 06/20/2014 02:04 AM, George Mitchell wrote:
Hello Tamas,
I think it would help to provide more information than what you have posted.
On 06/25/2014 03:09 PM, Tamas Papp wrote:
On 06/24/2014 06:37 PM, Chris Murphy wrote:
On Jun 24, 2014, at 1:52 AM, Tamas Papp tom...@martos.bme.hu wrote:
On 06/22/2014 07:10 PM, Tamas Papp wrote:
On 06/20/2014 02:04 AM, George Mitchell wrote:
Hello Tamas,
I think it would help to provide
On 6/25/14, Hugo Mills h...@carfax.org.uk wrote:
Storage is pretty cheap now, and to have multiple copies in btrfs is
something that I think could be used a lot. I know I will use multiple
copies of my data if made possible.
The question is, why? If you have enough disk media errors to
On Wed, 2014-06-25 at 08:47 +0100, Hugo Mills wrote:
This has variously been possible and not over the last few years. I
think it's finally come down on the side of not,
I think that would really be a loss... :(
The question is, why?
Well imagine you have some computer which can only
Imran Geriskovan posted on Wed, 25 Jun 2014 15:01:49 +0200 as excerpted:
Note that gdisk gives default 8 sector alignment value for AF disks.
That is 'sector' meant by gdisk is 'Logical Sector'!
Sufficiently determined user may create misaligned partitions by playing
with alignment value and
kcalloc manages count*sizeof overflow.
Cc: Chris Mason c...@fb.com
Cc: Josef Bacik jba...@fb.com
Cc: linux-btrfs@vger.kernel.org
Signed-off-by: Fabian Frederick f...@skynet.be
---
fs/btrfs/compression.c | 2 +-
fs/btrfs/ctree.c| 8
fs/btrfs/disk-io.c | 2 +-
On Jun 24, 2014, at 11:53 PM, Mike Hartman m...@hartmanipulation.com wrote:
Does this version's btrfs-image allow you to make an image of the file
system?
Nope, same errors and no output.
https://btrfs.wiki.kernel.org/index.php/Restore
Your superblocks are good according to btrfs
On Jun 25, 2014, at 1:47 AM, Hugo Mills h...@carfax.org.uk wrote:
The question is, why? If you have enough disk media errors to make
it worth using multiple copies, then your storage device is basically
broken and needs replacing, and it can't really be relied on for very
much longer.
I don't know all states of this file system, and copies you have. Right now
the earliest copy is obviously broken, and the latest copy is probably more
broken because at the least its csum tree has been blown away meaning there's
no checksums to confirm whether any data extracted/copied
On Fri, Jun 20, 2014 at 08:40:49AM -0700, Josef Bacik wrote:
On 06/19/2014 05:53 PM, Marc MERLIN wrote:
On Thu, Jun 19, 2014 at 03:50:16PM -0700, Josef Bacik wrote:
Ok same drill as before, reset and apply this, hopefully no panic this
time
diff --git a/fs/btrfs/relocation.c
On Mon, Jun 23, 2014 at 05:04:42PM +0200, David Sterba wrote:
On Mon, Jun 23, 2014 at 04:23:48AM +0200, Nils Steinger wrote:
+ rmdir -p --ignore-fail-on-non-empty $(DESTDIR)$(man8dir)
+ rmdir -p --ignore-fail-on-non-empty $(DESTDIR)$(libdir)
+ rmdir -p --ignore-fail-on-non-empty
On Jun 25, 2014, at 1:32 PM, Mike Hartman m...@hartmanipulation.com wrote:
I don't know all states of this file system, and copies you have. Right now
the earliest copy is obviously broken, and the latest copy is probably more
broken because at the least its csum tree has been blown away
This change is based on the corresponding recent change for ext4:
ext4: atomically set inode-i_flags in ext4_set_inode_flags()
That has the following commit message that applies to btrfs as well:
Use cmpxchg() to atomically set i_flags instead of clearing out the
S_IMMUTABLE, S_APPEND,
This is a regression from my patch a26e8c9f75b0bfd89e8f110737b136eb5994, we
need to only unlock the block if we were the one who locked it. Otherwise this
will trip BUG_ON()'s in locking.c Thanks,
cc: sta...@vger.kernel.org
Signed-off-by: Josef Bacik jba...@fb.com
---
fs/btrfs/disk-io.c |
On 06/25/2014 12:40 PM, Marc MERLIN wrote:
On Fri, Jun 20, 2014 at 08:40:49AM -0700, Josef Bacik wrote:
On 06/19/2014 05:53 PM, Marc MERLIN wrote:
On Thu, Jun 19, 2014 at 03:50:16PM -0700, Josef Bacik wrote:
Ok same drill as before, reset and apply this, hopefully no panic this
time
diff
On 25/6/2014 5:41 μμ, Christoph Anton Mitterer wrote:
On Wed, 2014-06-25 at 08:47 +0100, Hugo Mills wrote:
This has variously been possible and not over the last few years. I
think it's finally come down on the side of not,
I think that would really be a loss... :(
The question is,
i'm experiencing what I think are issues with btrfs and suspend/resume,
after a resume, I can no longer start any virtual machines in virtualbox
also, if I attempt a df command, it will just hang. Both of these events
work fine
prior to suspend resume as well as before I migrated to btrfs.
Things
First off: total RFC, don't merge this; it builds, but
is totally untested.
open_ctree() is almost 1000 lines long. I've started trying
to refactor it, primarily into helper functions, and also
simplifying (?) things a bit at the beginning by removing the
ret = func(); if (ret) { err = ret; goto
Original Message
Subject: [PATCH, RFC] btrfs: refactor open_ctree()
From: Eric Sandeen sand...@redhat.com
To: linux-btrfs linux-btrfs@vger.kernel.org
Date: 2014年06月26日 07:55
First off: total RFC, don't merge this; it builds, but
is totally untested.
open_ctree() is almost
The btrfs-image requires at least 2 args to run,
one for the source dev/file, the other for the target dev/file.
Signed-off-by: Gui Hecheng guihc.f...@cn.fujitsu.com
---
btrfs-image.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/btrfs-image.c b/btrfs-image.c
index e0aabfd..b13f236
Steps to reproduce:
# mkfs.btrfs -f dev1
# btrfs-image dev1 image_file
# btrfs-image -r -o image_file dev2
# btrfs check dev2
btrfs check output:
: read block failed check_tree_block
: Couldn't read tree root
: Couldn't open file system
The
Handle the malloc failure for dump_worker in the same way as
the restore worker.
Signed-off-by: Gui Hecheng guihc.f...@cn.fujitsu.com
---
btrfs-image.c | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/btrfs-image.c b/btrfs-image.c
index c90bca8..7131001
Signed-off-by: Gui Hecheng guihc.f...@cn.fujitsu.com
---
btrfs-image.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/btrfs-image.c b/btrfs-image.c
index b13f236..ed0b6ec 100644
--- a/btrfs-image.c
+++ b/btrfs-image.c
@@ -1163,7 +1163,7 @@ static int
If the malloc above fails, the btrfs-image will exit directly
without any error messages.
Now just return the ENOMEM errno and let the caller prompt the
error message.
Signed-off-by: Gui Hecheng guihc.f...@cn.fujitsu.com
---
btrfs-image.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Don't bother free the buffer if the malloc failed.
Signed-off-by: Gui Hecheng guihc.f...@cn.fujitsu.com
---
btrfs-image.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/btrfs-image.c b/btrfs-image.c
index 7131001..2d482c3 100644
--- a/btrfs-image.c
+++ b/btrfs-image.c
@@
Balance recovery is called when RW mounting or remounting from
RO to RW, it is called to finish roots merging.
When doing balance recovery, relocation root's corresponding
fs root(whose root refs is 0) might be destroyed by cleaner
thread, this will make btrfs fail to mount.
Fix this problem by
36 matches
Mail list logo
