Josef Bacik wrote:
This is a huge topic in and of itself, but Christoph mentioned wanting to have
an idea of what we wanted to do with it, so I'm putting it here. There are
really 2 things here
1) Limiting the size of subvolumes. This is really easy for us, just create a
subvolume and
Josef Bacik wrote:
1) Scrap the 256 inode number thing. Instead we'll just put a flag in the
inode
to say Hey, I'm a subvolume and then we can do all of the appropriate magic
that way. This unfortunately will be an incompatible format change, but the
sooner we get this adressed the
Excerpts from Arne Jansen's message of 2010-12-02 04:49:39 -0500:
Josef Bacik wrote:
1) Scrap the 256 inode number thing. Instead we'll just put a flag in the
inode
to say Hey, I'm a subvolume and then we can do all of the appropriate
magic
that way. This unfortunately will be an
Excerpts from Johannes Hirte's message of 2010-12-01 08:11:01 -0500:
On one of my machines with btrfs I got this bug:
entry offset 29085974528, bytes 4096, bitmap no
entry offset 29162995712, bytes 20480, bitmap yes
entry offset 29171744768, bytes 4096, bitmap no
block group has cluster?:
The function btree_migratepage will be extended from the baseclass
only when CONFIG_MIGRATION option is enabled. So, it's useful to
define/build this function only when that config option is enabled.
Fixes an unused function compiler warning when CONFIG_MIGRATION
is not enabled and also removes
Excerpts from Tommy Jonsson's message of 2010-12-01 06:00:56 -0500:
Hi folks!
Been using btrfs for quite a while now, worked great until now.
Got power-loss on my machine and now i have the parent transid verify
failed on X wanted X found X problem.
So I can't get it to mount.
My btrfs
Excerpts from Miao Xie's message of 2010-12-01 03:09:35 -0500:
Compare with Ext3/4, the performance of file creation and deletion on btrfs
is very poor. the reason is that btrfs must do a lot of b+ tree insertions,
such as inode item, directory name item, directory name index and so on.
If
On Thursday 02 December 2010 17:19:56 Chris Mason wrote:
Excerpts from Johannes Hirte's message of 2010-12-01 08:11:01 -0500:
On one of my machines with btrfs I got this bug:
entry offset 29085974528, bytes 4096, bitmap no
entry offset 29162995712, bytes 20480, bitmap yes
entry offset
On Thursday 02 December 2010 17:52:50 Johannes Hirte wrote:
On Thursday 02 December 2010 17:19:56 Chris Mason wrote:
Excerpts from Johannes Hirte's message of 2010-12-01 08:11:01 -0500:
On one of my machines with btrfs I got this bug:
entry offset 29085974528, bytes 4096, bitmap no
On 02/12/10 16:11, Chris Mason wrote:
Excerpts from Arne Jansen's message of 2010-12-02 04:49:39 -0500:
Josef Bacik wrote:
1) Scrap the 256 inode number thing. Instead we'll just put a flag in the inode
to say Hey, I'm a subvolume and then we can do all of the appropriate magic
that
Hallo,
I've new problems.
I use 2 disks (1.5 Tbyte and 2.0 TByte) under 1 LABEL (for my video
collection, nearly alle files have more than 1 GByte):
Label: MM2 uuid: ad7c0668-316c-4a79-ba00-3b505b9d99b4
Total devices 2 FS bytes used 2.38TB
devid2 size 1.35TB used 1.35TB
Excerpts from Johannes Hirte's message of 2010-12-02 12:02:16 -0500:
On Thursday 02 December 2010 17:52:50 Johannes Hirte wrote:
On Thursday 02 December 2010 17:19:56 Chris Mason wrote:
Excerpts from Johannes Hirte's message of 2010-12-01 08:11:01 -0500:
On one of my machines with btrfs
On Wed, Dec 1, 2010 at 10:23 PM, Mike Snitzer snit...@redhat.com wrote:
On Wed, Dec 01 2010 at 3:45pm -0500,
Milan Broz mb...@redhat.com wrote:
On 12/01/2010 08:34 PM, Jon Nelson wrote:
Perhaps this is useful: for myself, I found that when I started using
2.6.37rc3 that postgresql
On Thu, Dec 2, 2010 at 2:34 PM, Josef Bacik jo...@redhat.com wrote:
+ if (!ret) {
+ spin_lock(block_gruop-lock);
+ block_group-disk_cache_state = BTRFS_DC_SETUP;
+ spin_unlock(block_group-lock);
+ }
misspelling:
block_gruop -
Excerpts from Tommy Jonsson's message of 2010-12-02 16:45:39 -0500:
I can't remember if i used -m raid0.
I think i just used mkfs.btrfs /dev/sda then btrfs device add /dev/sdb
and same for sdc.
I am sure that i didn't explicitly use -m raid1 or raid10.
Is there a way that i can check this ?
$ btrfsck -s 1 /dev/sda
using SB copy 1, bytenr 67108864
parent transid verify failed on 2721514774528 wanted 39651 found 39649
btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root-node)' failed.
Aborted
$ btrfsck -s 2 /dev/sda
using SB copy 2, bytenr 274877906944
parent transid verify
Tried btrfs-debug-tree /dev/sda and btrfs-debug-tree -e /dev/sda :
parent transid verify failed on 2721514774528 wanted 39651 found 39649
btrfs-debug-tree: disk-io.c:739: open_ctree_fd: Assertion
`!(!tree_root-node)' failed.
dmesg said:
[268375.903581] device fsid
On Thursday 02 December 2010 21:34:10 Josef Bacik wrote:
On Wed, Dec 01, 2010 at 10:40:29PM +0100, Johannes Hirte wrote:
On Wednesday 01 December 2010 22:22:45 Johannes Hirte wrote:
On Wednesday 01 December 2010 21:03:13 Josef Bacik wrote:
On Wed, Dec 01, 2010 at 08:56:14PM +0100,
Did you fix that typo I posted?
C Anthony [mobile]
On Dec 2, 2010, at 6:05 PM, Johannes Hirte johannes.hi...@fem.tu-ilmenau.de
wrote:
On Thursday 02 December 2010 21:34:10 Josef Bacik wrote:
On Wed, Dec 01, 2010 at 10:40:29PM +0100, Johannes Hirte wrote:
On Wednesday 01 December 2010
On Friday 03 December 2010 01:44:49 C Anthony Risinger wrote:
Did you fix that typo I posted?
C Anthony [mobile]
Yes, without fix it wouldn't compile.
regards,
Johannes
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to
On Thursday 02 December 2010 20:21:30 Chris Mason wrote:
Excerpts from Johannes Hirte's message of 2010-12-02 12:02:16 -0500:
On Thursday 02 December 2010 17:52:50 Johannes Hirte wrote:
On Thursday 02 December 2010 17:19:56 Chris Mason wrote:
Excerpts from Johannes Hirte's message of
On 12/02/2010 04:49 AM, Arne Jansen wrote:
What about the alternative and allocating inode numbers globally? The only
problem would be with snapshots as they share the inum with the source, but
one could just remap inode numbers in snapshots by sparing some bits at the
top of this 64 bit field.
Is there a recommended way to replace a corrupted file or directory on
btrfs? The use case I'm thinking of is handling filesystem corruption
by restoring only the corrupted files from backup. For a corrupted
file, it seems like deleting the file and replacing it with the copy
from the backup
On Thu, Dec 2, 2010 at 10:23 AM, Helmut Hullen hul...@t-online.de wrote:
Btrfs Btrfs v0.19
btrfs in the kernel has been version 0.19 for a *long* time. The
version number there may never change. How do you encode a feature
mask in a version number? Some features may be in one tree but not
Hallo, Mike,
Du meintest am 02.12.10:
Btrfs Btrfs v0.19
btrfs in the kernel has been version 0.19 for a *long* time. The
version number there may never change. How do you encode a feature
mask in a version number? Some features may be in one tree but not
upstreamed all together and
25 matches
Mail list logo
