similar to: btrfs as default fs in Ubuntu 10.10?

Hi, I''m using btrfs on Ubuntu 10.10 for some test partitions. After doing some normal operations I suddenly couldn''t mount the partition anymore. I always get the error "BTRFS: inode 120790 still on the orphan list" in the kernel log again and again and it''s impossible to stop the mount command or shutdown the system. Any ideas how to work around this issue?

Hello all We are experimenting with btrfs and we''ve run into some problems. We are running on two Sun Storage J4400 Arrays containing a total of 48 1 TB disks. With 24 disks in the btrfs: # mkfs.btrfs /dev/sd[b-y] WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using adding device /dev/sdc id 2 ... adding device /dev/sdy id 24 fs

Hello Josef, FYI build failure occured in fs/btrfs/ctree.h. CC fs/btrfs/super.o In file included from fs/btrfs/delayed-inode.h:30:0, from fs/btrfs/super.c:45: fs/btrfs/ctree.h:3235:1: error: expected identifier or ‘(’ before ‘<<’ token make[3]: *** [fs/btrfs/super.o] Error 1 make[2]: *** [fs/btrfs] Error 2 make[1]: *** [fs] Error 2 make[1]: Leaving directory ` make:

I''ve been getting a compile error when building the ''next-rc'' branch of btrfs-unstable. CC fs/btrfs/disk-io.o fs/btrfs/disk-io.c: In function ‘btree_migratepage’: fs/btrfs/disk-io.c:716: error: called object ‘0u’ is not a function make[2]: *** [fs/btrfs/disk-io.o] Error 1 make[1]: *** [fs/btrfs] Error 2 make: *** [fs] Error 2 Line 716 of fs/btrfs/disk-io.c is:

Hi, I''m trying to run btrfs-convert on a system that has three raid partitions (boot/md1, swap/md2 and root/md3). When I boot a rescue system from md1, and try to run "btrfs-convert /dev/md3", it complains that /dev/md3 is already mounted, although it definitely is not. The only partition mounted is /dev/md1 because of the rescue system. When I replicate the setup in a

tree: git://git.kernel.org/pub/scm/linux/kernel/git/josef/btrfs-next.git master head: 0cb8658e96f1ba2ff2d730224cb31e231edd318d commit: 7017ac470ed5b029bc683883714a7f4a4ed34c33 Btrfs: move some common code into a subfunction date: 2 days ago config: make ARCH=x86_64 allyesconfig All warnings: fs/btrfs/volumes.c: In function ''btrfs_rm_device'': fs/btrfs/volumes.c:1505:1:

From: Julia Lawall <julia@diku.dk> If spin_lock_irqsave is called twice in a row with the same second argument, the interrupt state at the point of the second call overwrites the value saved by the first call. Indeed, the second call does not need to save the interrupt state, so it is changed to a simple spin_lock. The semantic match that finds this problem is as follows:

Hi, I''m getting a Kernel Bug when trying to delete some file in a btrfs while using 3.2.0-rc5. Here''s the kernel log: [ 676.672080] btrfs bad tree block start 0 40044687360 [ 676.672233] btrfs bad tree block start 0 40044687360 [ 676.672323] btrfs bad tree block start 0 40044687360 [ 676.672399] btrfs bad tree block start 0 40044687360 [ 676.672488] btrfs bad tree block

So I''m writing my (dis)adventure with btrfs here hoping to help the developers or someone with similar problems. I had a btrfs filesystem at work, using two 1TB disks, raid1 for both data and metadata. A week ago one of the two disks start having hundreds of relocated sectors, so I decide to change it. I remove the failing disk, mount with -o degraded and every works fine. The day later

I''ve enabled "extended inode refs" and "skinny metadata extent refs" with btrfstune. Then, I''ve tried running "btrfs filesystem balance" - unfortunately it segfaulted. (not sure if I should run balance operation after using btrfstune with -r and -x)? This is with 3.10 kernel with "Btrfs: make backref walking code handle skinny metadata"

I want to report a btrfs bug that happened this morning on kernel 3.2.1. I was copying a +5 GB file between two external usb harddisks, one formated with btrfs (the source) and the other with ext4 (the destination). In the meantime I decided to compile the 3.3-rc1 kernel with the output dir on the ext4 external harddisk. After some time I started to get many I/O errors coming from the ext4 drive

Older kernels would generally be able to still mount the filesystem with the default subvolume set, but it would result in a different volume being mounted, which could be an even more unpleasant suprise for users. So if you set your default subvolume, you can''t go back to older kernels. Thanks, Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/ctree.h | 4 +++-

Hi, I''ve some btrfs fs which are encrypted with loopaes. I decrypt them in a script during bootup. Now I want to determine if the decrypted fs is a btrfs fs. If not I missspelled the password and I can handle that error in my script. Thanks for any help! Felix -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to

Since theres not a good way to make sure the user sees the original default root tree id, and not to mention it''s 5 so is way different than any other volume, just make subvol=0 mount the original default root. This makes it a bit easier for users to handle in the long run. Thanks, Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/super.c | 12 +++++++++--- 1 files

Yesterday, I compiled the new kernel 3.0rc1 from git, but I never successed to go over the point: "Removing old temporary files". Pressing control-c let me boot on, but the pc was the complete time on very high load. It took me minutes, just to reach the tty login - and again minutes after login in, that I had my shell and a prompt to enter something. The load was at that time beyond 10.

Extend mkfs options to specify optional or potentially backwards incompatible features. Signed-off-by: David Sterba <dsterba@suse.cz> --- man/mkfs.btrfs.8.in | 9 ++++ mkfs.c | 124 +++++++++++++++++++++++++++++++++++++++++++++++----- 2 files changed, 123 insertions(+), 10 deletions(-) diff --git a/man/mkfs.btrfs.8.in b/man/mkfs.btrfs.8.in index a3f1503..548e754 100644 ---

Hello, My computer locked up and I had to press the reset button. Ever since then I can''t mount the btrfs filesystem, here''s the output: [ 37.645583] ------------[ cut here ]------------ [ 37.645598] WARNING: at fs/btrfs/free-space-cache.c:1887 btrfs_remove_free_space+0x329/0x350 [btrfs]() [ 37.645600] Modules linked in: btrfs zlib_deflate libcrc32c ext4 jbd2 mbcache crc16

Hi all, Did someone have met this problem before. When doing the tests, I hit the WARN_ON. Is this log make sense or someone had fixed the problem. If needed, I can supply the detail log and the testcase source file. Version: the latest codes at linus git tree. [ 2140.981293] use_block_rsv: 336 callbacks suppressed [ 2140.981295] ------------[ cut here ]------------ [ 2140.981308]

Is this useful to anyone? Got this after a crash/reboot: if (block_rsv) { WARN_ON(block_rsv->size > 0); <<<<<<<<<<<<<<<<<<<<<< btrfs_free_block_rsv(root, block_rsv); } ------------[ cut here ]------------ WARNING: at fs/btrfs/inode.c:2165 btrfs_orphan_commit_root+0xcb/0xdf() Hardware name: 2429A78 Modules linked in:

I know df does not report the correct size for btrfs raid systems. Is there any other way to find out the total capacity of a btrfs file system? Or at least the raid level for data / metadata? My test system is Ubuntu 10.10 alpha with btrfs 0.19 and a 2.6.35 kernel (don''t know which rc). # uname -a Linux ubuntu 2.6.35-12-generic #17-Ubuntu SMP Mon Jul 26 18:48:06 UTC 2010 x86_64