On 2013/02/13 12:33 PM, Holger Hoffstaette wrote:
- raise the leaf size to 16k
- use single metadata profile
...
the difference in behaviour on a single disk is *very* noticeable.
Did you try an isolated change of leaf size? I think the devs would be
willing to look into the default size if
tilegx_defconfig:
fs/btrfs/raid56.c: In function 'btrfs_alloc_stripe_hash_table':
fs/btrfs/raid56.c:206:3: error: implicit declaration of function 'vzalloc'
[-Werror=implicit-function-declaration]
fs/btrfs/raid56.c:206:9: warning: assignment makes pointer from integer without
a cast [enabled by
On Sun, Mar 03, 2013 at 04:44:41AM -0700, Geert Uytterhoeven wrote:
tilegx_defconfig:
fs/btrfs/raid56.c: In function 'btrfs_alloc_stripe_hash_table':
fs/btrfs/raid56.c:206:3: error: implicit declaration of function 'vzalloc'
[-Werror=implicit-function-declaration]
fs/btrfs/raid56.c:206:9:
x86 seems to include vmalloc.h by default along some of its arch paths,
but most other architectures don't, leading to this compile failure:
fs/btrfs/raid56.c: In function 'btrfs_alloc_stripe_hash_table':
fs/btrfs/raid56.c:206: error: implicit declaration of function 'vzalloc'
Hi Linus,
Geert and James both sent this one in, sorry guys.
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
Geert Uytterhoeven (1) commits (+1/-0):
btrfs/raid56: Add missing #include linux/vmalloc.h
Total: (1) commits (+1/-0)
fs/btrfs/raid56.c | 1 +
1 file
Greetings all,
I have an extent tree that looks like follows:
item 22 key (27059916800 EXTENT_ITEM 16384) itemoff 2656 itemsize 24
extent refs 1 gen 164 flags 1
item 23 key (27059916800 EXTENT_ITEM 98304) itemoff 2603 itemsize 53
extent refs 1 gen
Hi list,
some rather unexpected btrfs-oopses for my taste. I use btrfs for some
time now (mostly on external harddisks) and these oopses happened
during some simple file and folder deletion operation on that device. It
is a luks-encrypted 80GB drive. Anything like that known? And the fs was
On Sun, Mar 03, 2013 at 06:40:50AM -0700, Alex Lyakas wrote:
Greetings all,
I have an extent tree that looks like follows:
item 22 key (27059916800 EXTENT_ITEM 16384) itemoff 2656 itemsize 24
extent refs 1 gen 164 flags 1
item 23 key (27059916800 EXTENT_ITEM 98304)
Hi Josef,
I have some more questions following up on my previous e-mails.
I now do somewhat understand the place where extent entries get
cow'ed. But I am unclear about the order of operations.
Is it correct that the data extent written first, then the pointer in
the indirect block needs to be
Hi Chris,
On Sun, Mar 3, 2013 at 5:28 PM, Chris Mason chris.ma...@fusionio.com wrote:
On Sun, Mar 03, 2013 at 06:40:50AM -0700, Alex Lyakas wrote:
Greetings all,
I have an extent tree that looks like follows:
item 22 key (27059916800 EXTENT_ITEM 16384) itemoff 2656 itemsize 24
On 2013/02/14 12:15 PM, Vedant Kumar wrote:
Hello,
I'm experiencing periodic write spikes while my system is idle.
...
turned out to be some systemd log in
/var/log/journal. I turned off journald and rebooted, but the write spike
behavior remained.
...
best,
-vk
I believe btrfs syncs every
On Fri, Mar 01, 2013 at 06:05:21PM +, Hugo Mills wrote:
On Fri, Mar 01, 2013 at 11:47:50AM -0600, Eric Sandeen wrote:
On 3/1/13 4:10 AM, Anand Jain wrote:
Signed-off-by: Anand Jain anand.j...@oracle.com
Revieed-by: Eric Sandeen sand...@redhat.com
But the curious side of me
On Sun, Mar 03, 2013 at 03:33:30AM -0700, Brendan Hide wrote:
On 2013/02/13 12:33 PM, Holger Hoffstaette wrote:
- raise the leaf size to 16k
- use single metadata profile
...
the difference in behaviour on a single disk is *very* noticeable.
Did you try an isolated change of leaf
On 2013/02/14 09:53 AM, Tsutomu Itoh wrote:
+ if (ret 0) {
+ fprintf(stderr, error checking %s status: %s\n, file,
+ strerror(-ret));
+ exit(1);
+ }
...
+ /* check if the device
On Fri, Feb 15, 2013 at 05:12:37PM -0600, Simon Kirby wrote:
[...]
Signed-off-by: Simon Kirby s...@hostway.ca
Thanks! 2 comments below.
Reviewed-by: David Sterba dste...@suse.cz
@@ -2919,8 +2923,9 @@ int btrfs_write_out_ino_cache(struct btrfs_root *root,
if (ret) {
On 2013/02/18 12:37 PM, Adam Ryczkowski wrote:
...
to migrate btrfs from one partition layout to another.
...
source sits on top of lvm2 logical volume, which sits on top of
cryptsetup Luks device which subsequentely sits on top of mdadm RAID-6
spanning a partition on each of 4 hard drives ...
On Sat, Mar 2, 2013 at 4:07 PM, Alex Lyakas
alex.bt...@zadarastorage.com wrote:
Hi Josef,
I hope it's ok to piggy back on this thread for the following question:
I see that in btrfs_cross_ref_exist()=check_committed_ref() path,
there is the following check:
if (btrfs_extent_generation(leaf,
On Sun, Mar 3, 2013 at 10:41 AM, Aastha Mehta aasth...@gmail.com wrote:
Hi Josef,
I have some more questions following up on my previous e-mails.
I now do somewhat understand the place where extent entries get
cow'ed. But I am unclear about the order of operations.
Is it correct that the
On Sun, Mar 03, 2013 at 06:57:41AM -0700, Michael Schmitt wrote:
Hi list,
some rather unexpected btrfs-oopses for my taste. I use btrfs for some
time now (mostly on external harddisks) and these oopses happened
during some simple file and folder deletion operation on that device. It
is a
On Feb 23, 2013, Alexandre Oliva ol...@gnu.org wrote:
On Feb 22, 2013, Josef Bacik jba...@fusionio.com wrote:
So I understand what you are getting at, but I think you are doing it wrong.
If
we're calling with CHUNK_ALLOC_FORCE, but somebody has already started to
allocate with
From: Zhi Yong Wu wu...@linux.vnet.ibm.com
Since raid5/6 support was introduced, we should update mkfs.btrfs help info.
Signed-off-by: Zhi Yong Wu wu...@linux.vnet.ibm.com
---
mkfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mkfs.c b/mkfs.c
index 5ece186..f9f26a5
flags = BTRFS_SCAN_REGISTER | BTRFS_SCAN_PRIMARY_SB;
btrfs_scan_one_dir(/dev/, flags)
I just got too flexed into the current way of coding
in btrfs-progs :-)
But let me get at least this part of the code
in the right-way.
Thanks Eric for pointing out.
-Anand
--
To unsubscribe from
22 matches
Mail list logo
