November 26, 20187 yr "BTRFS info (device dm-1): found 1 extents" is coming up in my syslog over and over again.. Is one of my cache drives failing? veyron-diagnostics-20181126-0531.zip Just got back up and running after this... Edited November 26, 20187 yr by BrandonG777 A little history...
November 26, 20187 yr Community Expert That's not an error, and it's normal during a balance, which apparently was run before: Nov 25 04:30:11 Veyron kernel: BTRFS info (device dm-1): relocating block group 177222975488 flags data|raid1 Nov 25 04:30:12 Veyron kernel: BTRFS info (device dm-1): found 295 extents ### [PREVIOUS LINE REPEATED 1 TIMES] ### Nov 25 04:30:12 Veyron kernel: BTRFS info (device dm-1): relocating block group 176149233664 flags data|raid1 Nov 25 04:30:13 Veyron kernel: BTRFS info (device dm-1): found 3586 extents ### [PREVIOUS LINE REPEATED 1 TIMES] ### Nov 25 04:30:14 Veyron kernel: BTRFS info (device dm-1): found 1 extents ### [PREVIOUS LINE REPEATED 97 TIMES] ### Nov 25 04:30:18 Veyron kernel: btrfs_printk: 40 callbacks suppressed Nov 25 04:30:18 Veyron kernel: BTRFS info (device dm-1): found 1 extents ### [PREVIOUS LINE REPEATED 972 TIMES] ### Nov 25 04:31:19 Veyron kernel: btrfs_printk: 21 callbacks suppressed Nov 25 04:31:19 Veyron kernel: BTRFS info (device dm-1): found 1 extents but not so normal to keep repeating that for so long, assuming no balance is running now reboot to see if it goes away. P.S. lots of call traces mentioning macvlan, these are usually caused by dockers with custom IPs.
November 26, 20187 yr Author Had to force the reboot. Still came back up with the extent messages. Did a btrfsck --repair and that seemed to resolve it. I'm not feeling very comfortable with btrfs since this is the second major issue I've had with it in less than 30 days, are other file systems still available for cache drives? I guess the custom IPs on dockers are a no no? Is there a better way of accomplishing this? I really need them for filtering VPN traffic but maybe I can setup another virtual network for these purposes?
November 26, 20187 yr Community Expert If you have a single cache drive then XFS is an option. If you have multiple drives (I.e. a cache pool) then BTRFS is the only option.
November 26, 20187 yr Author 1 minute ago, itimpi said: If you have a single cache drive then XFS is an option. If you have multiple drives (I.e. a cache pool) then BTRFS is the only option. Yeah, I have two cache drives (mirroring each other for redundancy) but I'm questioning the usefulness of this since it didn't do me any good after last months failure and ended up going back to a nightly backup anyway.
November 26, 20187 yr Community Expert btrfs is not the stablest of filesystems, but if you keep getting issues there are likely underlying hardware issues, I use btrfs an all my Unraid servers, including all data disks, for years now without any issues.
November 29, 20187 yr Author On 11/26/2018 at 5:42 PM, johnnie.black said: btrfs is not the stablest of filesystems, but if you keep getting issues there are likely underlying hardware issues, I use btrfs an all my Unraid servers, including all data disks, for years now without any issues. Ok, that's good info to have, I'll direct my focus on hardware and other things to find the source of these problems then. I don't think it's a hardware issue, but this macvlan trace calls stuff got my attention, somehow I was overlooking in the logs, so thanks for pointing it out. I'm leaning more towards the macvlan trace calls causing something like this continuous extent problem where the logs filled my available drive space and then caused subsequent failures. Digging through this forum, I believe the I found the original bug report where the OP mentioned this issue starting with pihole. It seems most if not all of my call traces are also related to the pihole docker container. Ditching the pihole container and reducing the number of static IPs as much as possible seems to have resolved my issues. Knock on wood, I still have a handful of static IP container but I haven't seen a call trace in almost 2 days.
November 30, 20187 yr Author So i awoke this morning to a couple new call traces. Simply elimating pihole from the mix didn't resolve my issue. If I can't use static IPs for my containers how else might I do port forwarding for my letsencrypt container? I'm must be missing something.Sent from my Pixel 2 XL using Tapatalk
December 7, 20187 yr Author I have removed all static IPs from my docker containers but I'm still getting call traces. Any other ideas where these would be coming from? veyron-diagnostics-20181207-0847.zip
Archived
This topic is now archived and is closed to further replies.