No Space left / Transaction aborted error -28 (4.19.59 kernel)

Hi, Kernel 4.19.59. % btrfs fi us /backups/ Overall:     Device size:           4.00TiB     Device allocated:           3.44TiB *    Device unallocated:         572.95GiB*     Device missing:        0.00B     Used:               3.43TiB *    Free (estimated):         576.36GiB    (min: 576

Transaction aborted (error -28) - at fs/btrfs/extent-tree.c:6953

I've just hit this on a backup server. I suspect something would have been trying to remove/create a snapshot at the time. I'll ignorantly assume it's similar to the last one I posted ( https://www.spinics.net/lists/linux-btrfs/msg82636.html ) although the trace is different. David. --

Transaction aborted error -28 clone_finish_inode_update

While trying to run/use bedup ( https://github.com/g2p/bedup ) I hit this : [Thu Oct  4 15:34:51 2018] [ cut here ] [Thu Oct  4 15:34:51 2018] BTRFS: Transaction aborted (error -28) [Thu Oct  4 15:34:51 2018] WARNING: CPU: 0 PID: 28832 at fs/btrfs/ioctl.c:3671 clon

Transaction aborted - 4.16.17 kernel

I've just spotted this on one server. Running : umount /backups && mount /backups seems to allow it to become r/w again, but it does write : BTRFS error (device xvdj): cleaner transaction attach returned -30 to 'dmesg'. David. [ cut here ] BTRFS: Transaction aborted

Re: extent-tree.c no space left (4.9.77 + 4.16.2)

On 21/04/2018 10:18, Martin Svec wrote: Hi David, this looks like the bug that I already reported two times: https://www.spinics.net/lists/linux-btrfs/msg54394.html https://www.spinics.net/lists/linux-btrfs/msg75104.html The second thread contains Nikolay's debug patch that can confirm if you

4.9.83 - btrfs_truncate_inode_items - nospace left -> transid / csum issues.

Hi My volume ran out of space, and that seems to have triggered csum errors. Kernel 4.9.83 % btrfs fi us /backup/ Overall:     Device size:           4.12TiB     Device allocated:           4.12TiB     Device unallocated:           2.00MiB     Device missing:        0.00B     Used:       

extent-tree.c no space left (4.9.77 + 4.16.2)

Hi, I'm running a 3TiB EBS based (2+1TiB devices) volume in EC2 which contains about 500 read-only snapshots. btrfs-progs v4.7.3 There are two dmesg trace things below. The first one from a 4.9.77 kernel - [ cut here ] BTRFS: error (device xvdg) in btrfs_run_delayed_r

Re: kernel btrfs file system wedged -- is it toast?

That shell is still hung in the kernel, on a "disk sleep" fifteen minutes later, and one of my CPU cores is pegged at 100%, and the disk activity light is not coming on at all. .. This is not disk bound activity ... it's kernel code bound. That's insane ... and sad. 'perf top' is my f

kernel 4.1.15 balance => oops. out of memory.

kernel 4.1.15 balancing a fs led to this oops. after a reboot, the balance resumed without problem. presumably there wasn't enough real memory available David [ cut here ] WARNING: CPU: 1 PID: 16560 at fs/btrfs/super.c:260 __btrfs_abort_transaction+0x4b/0x120 [btrfs

device removal seems to be very slow (kernel 4.1.15)

Using btrfs progs 4.3.1 on a Vanilla kernel.org 4.1.15 kernel. time btrfs device delete /dev/xvdh /backups real13936m56.796s user0m0.000s sys 1351m48.280s (which is about 9 days). Where : /dev/xvdh was 120gb in size. /backups is a single / "raid 0" volume that now looks like :

kernel 4.1.13 - balance bug?

Hi, Trying to run a balance on a filesystem results in the below dmesg output. Kernel is 4.1.13 from kernel.org. System is running in AWS (hence the Xen stuff). INFO: task btrfs:28938 blocked for more than 120 seconds. Not tainted 4.1.13-dg1 #1 "echo 0 > /proc/sys/kernel/hung_task_timeo

kernel 4.1.12 - hung_task_timeout

Hi, See below for oops messages from a 4.1.12 kernel. The system would probably have been running a balance or scrub at the time. Processes trying to use subvolumes blocked and it eventually needed rebooting via sysrq to fix. Kernel is a vanilla one from kernel.org. thanks, David. INFO:

Re: Periodic kernel freezes

On 30/10/2015 16:25, Alex Adriaanse wrote: I have an EC2 instance on AWS that tends to freeze several times per week. When it freezes it stops responding to network traffic, disk I/O stops, and CPU goes to 100%. The system comes back fine after a reboot. I was finally able to get a kernel backtr

oops - fs/btrfs/extent-tree.c:2025 - kernel 4.2.0-rc3 - __btrfs_inc_extent_ref:2025: errno=-17 Object already exists

Filesystem was being balanced with : btrfs balance start -dusage=55 -musage=55 $filesystem when this happened : [ cut here ] WARNING: CPU: 2 PID: 31502 at fs/btrfs/extent-tree.c:2025 __btrfs_inc_extent_ref.isra.51+0x210/0x280 [btrfs]() BTRFS: Transaction aborted (error

kernel oops report

0x107/0x110 RSP ---[ end trace fcc878a87658ea75 ]--- -- David Goodwin http://codepoets.co.uk -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Mount multiple file system with the same UUID

On 17/04/15 10:20, WangMike wrote: Dear all, We know that one cannot mount multiple btrfs file systems which contain the same UUID (for example, snapshot ). Is it possible to make use of "mount namespace" achieve that? means, if the btrfs file system in different namespace can contain the sam