On 02/04/2020 21:55, Helper Son wrote: > Hello, > > I'm running a fully updated Manjaro install on kernel > 5.5.13-1-MANJARO, but this problem occurs on other kernel versions as > well. I believe I tried 5.4 and 5.6. > > I have a btrfs filesystem that looks like this: > > Overall: > Device size: 14.55TiB ... > > When the system was at only a couple terabytes of usage, everything > was fine. But, as it got progressively filled with more data, it > started to take longer to mount during bootup. At one point it > extrapolated the 90 second limit and the system failed to boot because > of that; I then added nofail to the fstab entry so boot would continue > while the system mounted. > > However, even after taking around two minutes to mount, it still fails: I see the same problem (I am running Debian Testing - Bullseye). I *think* (I haven't bothered to test carefully) the problem is that when the 90 second default mount timer runs out, systemd cancels the mount. The fix is simple: increase the systemd timeout for that mount. In fstab, add the option: x-systemd.mount-timeout=N with N long enough (I am using 180). More info is available (at least in my distribution) in systemd.mount(5). If anyone else is a Debian user, they may want to add a comment to my bug report (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955413) asking for a warning to that effect to be added to the NEWS file for btrfs-progs and the bullseye release notes.
