Re: "kernel BUG at /home/apw/COD/linux/fs/btrfs/extent_io.c:2116!" when deleting device or balancing filesystem.

2014-04-27 Thread Duncan
Jaap Pieroen posted on Sun, 27 Apr 2014 18:30:19 +0200 as excerpted: > Hello, > > When I try to delete a device from my btrfs filesystem I always get the > following kernel bug error: > kernel BUG at /home/apw/COD/linux/fs/btrfs/extent_io.c:2116! > invalid opcode: [#3] SMP > See attached lo

Re: Confusing output of btrfs fi df

2014-04-27 Thread Duncan
Stefan Malte Schumacher posted on Sun, 27 Apr 2014 17:37:26 +0200 as excerpted: > Chris and Duncan: I tried both your suggestions but unfortunately > without success. Here is the output: > > mars:~ # btrfs balance start -susage=0 -f -v /mnt/btrfs/ > Dumping filters: flags 0xa, state 0x0, force is

[ANNOUNCE] xfstests: master branch updated to ce0aa2b

2014-04-27 Thread Dave Chinner
Hi folks, The xfstests repository at git://oss.sgi.com/xfs/cmds/xfstests has just been updated. Patches often get missed, so please check if your outstanding patches were in this update. If they have not been in this update, please resubmit them to x...@oss.sgi.com so they can be picked up in the

File system errors

2014-04-27 Thread Niv Gal Waizer
A week ago I installed kernel 3.14 on an existing laptop with btrfs install by ubuntu. I upgraded ubuntu to 14.04 a few days ago. I had problems installing a package, then I removed libc6 by mistake, I could no longer boot the system. I booted from a usb disk with ubuntu 14.04. I ran btrfsck

Re: Lost /home subvolume after btrfs crash

2014-04-27 Thread Martin Wilck
On 04/24/2014 05:15 AM, Chris Murphy wrote: >>> Current stable is 3.14.1, I suggest giving 3.13 or 3.14 a shot at this with >>> -o ro,recovery as a first step and see if it at least mounts. >> >> I will. Note that with 12.3, which was the most recent media I had at >> hand at the time, the FS was

[PATCH] Btrfs: fix leaf corruption caused by ENOSPC while hole punching

2014-04-27 Thread Filipe David Borba Manana
While running a stress test with multiple threads writing to the same btrfs file system, I ended up with a situation where a leaf was corrupted in that it had 2 file extent item keys that had the same exact key. I was able to detect this quickly thanks to the following patch which triggers an asser

[PATCH v2] Btrfs: implement inode_operations callback tmpfile

2014-04-27 Thread Filipe David Borba Manana
This implements the tmpfile callback of struct inode_operations, introduced in the linux kernel 3.11, and implemented already by some filesystems. This callback is invoked by the VFS when the flag O_TMPFILE is passed to the open system call. Signed-off-by: Filipe David Borba Manana --- V2: Updat

"kernel BUG at /home/apw/COD/linux/fs/btrfs/extent_io.c:2116!" when deleting device or balancing filesystem.

2014-04-27 Thread Jaap Pieroen
Hello, When I try to delete a device from my btrfs filesystem I always get the following kernel bug error: [ 809.161020] kernel BUG at /home/apw/COD/linux/fs/btrfs/extent_io.c:2116! [ 809.166761] invalid opcode: [#3] SMP See attached log file for more details. I’m trying t

Re: Can anyone boot a system using btrfs root with linux 3.14 or newer? - RESOLVED

2014-04-27 Thread Martin
On 27/04/14 13:00, Пламен Петров wrote: > The problem reported in this thread has been RESOLVED. > > It's not BTRFS's fault. > > Debugging on my part led to the actual problem in do_mounts.c - some > filesystems mount routines return error codes other than 0, EACCES > and EINVAL and such return c

Re: Confusing output of btrfs fi df

2014-04-27 Thread Stefan Malte Schumacher
Hello Chris and Duncan: I tried both your suggestions but unfortunately without success. Here is the output: mars:~ # btrfs balance start -susage=0 -f -v /mnt/btrfs/ Dumping filters: flags 0xa, state 0x0, force is on SYSTEM (flags 0x2): balancing, usage=0 Done, had to relocate 0 out of 2708 c

RE: Can anyone boot a system using btrfs root with linux 3.14 or newer? - RESOLVED

2014-04-27 Thread Пламен Петров
The problem reported in this thread has been RESOLVED. It's not BTRFS's fault. Debugging on my part led to the actual problem in do_mounts.c - some filesystems mount routines return error codes other than 0, EACCES and EINVAL and such return codes result in the kernel panicking without trying t