Hi,
I'm experimenting with btrfs on top of zvol block device (using
zfsonlinux), and got oops on a simple mount test.
While I'm sure that zfsonlinux is somehow also at fault here (since
the same test with zram works fine), the oops only shows things
btrfs-related without any usable mention of
The disk format description implies that btrfs should be able to support tail
packing. I just did some experimentation, and while small files are packed, it
seems that files occupying more than one block are not. For example, a lot of
32769-byte files will end up taking over 36KB on average (a
On Fri, Aug 31, 2012 at 08:47:16AM -0600, Fengguang Wu wrote:
Hi Liu,
FYI, kernel build failed on
tree: git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git
master
head: 8ccfefeea39d6ee32ad312b1fd3b8eeb19de9265
commit: 8ccfefeea39d6ee32ad312b1fd3b8eeb19de9265 [29/29]
On Fri, Aug 31, 2012 at 08:40:36AM -0600, Ben Wreder wrote:
The disk format description implies that btrfs should be able to support tail
packing. I just did some experimentation, and while small files are packed,
it seems that files occupying more than one block are not. For example, a lot
This patch is a follow up on below patch:
[PATCH] exportfs: add FILEID_INVALID to indicate invalid fid_type
https://patchwork.kernel.org/patch/1385131/
Signed-off-by: Namjae Jeon linkinj...@gmail.com
Signed-off-by: Vivek Trivedi vtrivedi...@gmail.com
---
fs/btrfs/export.c |4 ++--
On 08/30/2012 08:24 PM, Goffredo Baroncelli wrote:
And magically the filesystem is now composed by three disks. However 4
physical devices are show. This because the disk /dev/vdi superblock
says that the disk is still valid (after the btrfs device del the disk
is not touched any more)
I have
Hi all, Yan,
On 08/31/2012 09:08 PM, Goffredo Baroncelli wrote:
However making a test I found both the behaviours: sometime the removed
disk disappears from the output of btrfs fi show and sometime not...
May be that there is a bug somewhere...
I became crazy looking at this bug. I found
