Do you try: nofail,noauto,x-systemd.automount ? 2016-08-29 9:28 GMT+03:00 Stefan Priebe - Profihost AG <s.pri...@profihost.ag>: > Hi Qu, > > Am 29.08.2016 um 03:48 schrieb Qu Wenruo: >> >> >> At 08/29/2016 04:15 AM, Stefan Priebe - Profihost AG wrote: >>> Hi, >>> >>> i'm trying to get my 60TB btrfs volume to mount with systemd at boot. >>> But this always fails with: "mounting timed out. Stopping." after 90s. >> >> 60TB is quite large, and under most case it will already cause mount >> speed problem. >> >> In our test environment, filling a fs with 16K small files to 2T (just >> 128K files)will already slow the mount process to 10s. >> >> For larger fs, or more specifically, large extent tree, will slow the >> mount process obviously. >> >> The root fix will need a rework of extent tree. >> AFAIK Josef is working on the rework. >> >> So the btrfs fix will need some time. > > thanks but i've no problem with the long mount time (in my case 6 > minutes) i'm just wondering how to live with it with systemd. As it > always cancels the mount process after 90s and i see no fstab option to > change this. > > Greets, > Stefan > >> >> Thanks, >> Qu >>> >>> I can't find any fstab setting for systemd to higher this timeout. >>> There's just the x-systemd.device-timeout but this controls how long to >>> wait for the device and not for the mount command. >>> >>> Is there any solution for big btrfs volumes and systemd? >>> >>> Greets, >>> Stefan >>> -- >>> 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 >>> >>> >> >> > -- > 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
-- Have a nice day, Timofey. -- 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
