similar to: Extent back references pushed to -unstable

Hi All, I''m trying to repair a broken fs using btrfsck and am hitting a failed assertion. I''d appreciate any suggestions for what to do next. Is there any thing I can do to help fix this bug? Any other information from my FS which would help? If the FS could be salvaged that would be a bonus, but I''m more interested in providing a useful bug report before wiping the

Hello everyone, Yan Zheng sent along an update for the new format patch today, and it slightly changed the disk format for backrefs used when balancing space across drives. We decided against supporting an intermediate format that was only a week old, and his update makes a few important features much much easier (snapshot deletion for one). If you''ve tried the newformat branch and run

A user reported that fsck was complaining about unresolved refs for some snapshots. You can reproduce this by doing mkfs.btrfs /dev/sdb mount /dev/sdb /mnt btrfs subvol snap /mnt/ /mnt/a btrfs subvol snap /mnt/ /mnt/b btrfs subvol del /mnt/a umount /mnt btrfsck /dev/sdb and you''d get this unresolved ref root 258 dir 256 index 2 namelen 1 name a error 600 because snapshot b has a dir

Hi devs, I can''t mount my btrfs-based external disk. I don''t know what happened to the disk, but usually it gets disconnected (usb cable pulled out) buy my 8 months old daughter. Here''s the output from dmesg: [ 299.699543] parent transid verify failed on 528952573952 wanted 22726 found 22728 [ 299.700947] btrfs read error corrected: ino 1 off 528952573952 (dev

Hi all, I''m running btrfs in a 3-disk RAID1 configuration. After a hard power-off, I''m seeing a lot of hung I/O tasks on this volume, apparently due to a corrupt leaf. I first noticed the problem on kernel 3.4.7, and it''s persisted with 3.4.8. Relevant parts of the kernel log follow. [ 85.179621] block group 38684065792 has an wrong amount of free space [

Dear list members, When I tried to recover my partition from the space cache bug (see http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg24360.html ), I issued the command `mount -o clear_cache -t btrfs /dev/sda7 /aaa/aaa`. After 10 minutes the mount command segfaulted. I cloned the latest btrfs-progs from Josef''s Github account and ran the `btrfsck --repair` twice on the

Chris Mason on 10 Feb 13:17: > Excerpts from Ben Gamari''s message of 2011-02-09 21:52:20 -0500: > > Over the last several months there have been many claims regarding > > the release of the rewritten btrfsck. Unfortunately, despite > > numerous claims that it will be released Real Soon Now(c), I have > > yet to see even a repository with preliminary code. Did I

Signed-off-by: Goldwyn Rodrigues <rgoldwyn@gmail.com> --- man/Makefile | 27 +++++++++++++++++++++++++++ man/btrfsck.8.in | 17 +++++++++++++++++ 2 files changed, 44 insertions(+), 0 deletions(-) create mode 100644 man/Makefile create mode 100644 man/btrfsck.8.in diff --git a/man/Makefile b/man/Makefile new file mode 100644 index 0000000..2665dd1 --- /dev/null +++ b/man/Makefile

Split CFLAGS into CFLAGS (user part) and AM_CFLAGS (not-so-user part; variable name taken from automake, but otherwise no relation). Also add LDFLAGS. This allows me to use `make CFLAGS="-O2 -fPIE" LDFLAGS="-pie"` without dropping the other important (AM_CFLAGS) flags. Signed-off-by: Jan Engelhardt <jengelh@computergmbh.de> --- btrfs-progs/Makefile | 17

Now we set @refs to 2 on creating a new extent buffer, meanwhile we allocate the needed free space, but we don''t give enough free_extent_buffer() to reduce the eb''s references to zero so that the eb can finally be freed, so the problem is we has decrease the referene count of backrefs to zero, which ends up releasing the space occupied by the eb, and this space can be allocated

I''ve just pushed out a new integration branch to my git repo. This is purely bugfix patches -- there are no new features in this issue of the integration branch. I''ve got a stack of about a dozen more patches with new features in them still to go. I''ll be working on those tomorrow. As always, there''s minimal testing involved here, but it does at least compile on

Hi! I used to have arch linux running on 1 btrfs partition (sda1, incl. /boot). When switching to 3.2.5 recently the system fails to boot: (after udevd) /etc/rc.sysinit: line 15: 117 Bus error mountpoint -q /proc and so on, no idea. It used to boot with 3.2.4, but 1) I obviously had some corruption in the tree, when I tried to delete a certain file I hit e.g. "kernel BUG at

Signed-off-by: Yan Zheng <zheng.yan@oracle.com> --- diff -urp btrfs-progs-unstable/btrfsck.c btrfs-progs-2/btrfsck.c --- btrfs-progs-unstable/btrfsck.c 2009-09-28 15:54:55.980479398 +0800 +++ btrfs-progs-2/btrfsck.c 2010-01-31 09:46:24.645485459 +0800 @@ -581,7 +581,6 @@ again: } ret = insert_existing_cache_extent(dst, &ins->cache); if (ret == -EEXIST) { - WARN_ON(src ==

add man/btrfs-image.8.in Signed-off-by: Peng Tao <bergwolf@gmail.com> --- man/Makefile | 5 ++++- man/btrfs-image.8.in | 34 ++++++++++++++++++++++++++++++++++ 2 files changed, 38 insertions(+), 1 deletions(-) create mode 100644 man/btrfs-image.8.in diff --git a/man/Makefile b/man/Makefile index 2665dd1..b7a7340 100644 --- a/man/Makefile +++ b/man/Makefile @@ -6,7 +6,7 @@

So I''m having a bit of trouble with one of my btrfs filesystems. It isn''t mounting after a power failure. I can''t get restore or btrfsck to run, even on backup supers. I''ve pasted some output below. My btrfs-progs below come from git this morning, running on linux 3.2.0. # mount /dev/md2 /media/test/ mount: wrong fs type, bad option, bad superblock on

Hi everyone, I''ve pushed out my current kernel git tree to a new branch called integration-test. This is meant for integration testing only and should not be run by anyone who doesn''t love crashes. I''ve pulled together a lot of important work from a lot of different people. It includes: The new inode number allocator Delayed inode and directory item updates Scrub,

The new xfstests will run fsck against the volume to make sure we didn''t introduce any inconsistencies, which is nice except we will error out immediately if we mount with inode_cache. We need to make btrfsck skip the special free space cache items and then just assume that we have a link for the free space cache inode item. This makes btrfsck pass with success on a fs with inode cache

Hello everyone, Btrfs v0.10 is now available for download from: http://oss.oracle.com/projects/btrfs/ Btrfs is still in an early alpha state, and the disk format is not finalized. v0.10 introduces a new disk format, and is not compatible with v0.9. The core of this release is explicit back references for all metadata blocks, data extents, and directory items. These are a crucial building

Hello everyone, Btrfs v0.10 is now available for download from: http://oss.oracle.com/projects/btrfs/ Btrfs is still in an early alpha state, and the disk format is not finalized. v0.10 introduces a new disk format, and is not compatible with v0.9. The core of this release is explicit back references for all metadata blocks, data extents, and directory items. These are a crucial building

Hi, I thought that I would attempt a quick little patch that will make btrfsck into a No-op when called as fsck.btrfsck. The reasoning is that the FAQ states that it is recommended and safe to do so, and the current 12.04 version of Ubuntu just symlinks fsck.btrfsck to btrfsck instead of /bin/true. PS - Apologies if I mess this git send-email up! Dan McGrath (1): btrfs-progs: No-op when