3 ms·
> I was debugging the boot on a server recently. It mounts a bunch of NFS filesystems Don't do that. It's a bag of hurt. (Still sore about the hours that work
by B1FF_PSUVM 11y ago
> I was debugging the boot on a server recently. It mounts a bunch of NFS filesystems
Don't do that. It's a bag of hurt.
(Still sore about the hours that workstations with not-working-fs mounts spent waiting for each other on boot after power failures, ages ago. Nevermore.)
- deleted 11y ago[deleted]
- ibotty 11y agoSo you just don't use remote filesystems? That's a solution! Honestly, whenever the init system is configured correctly, you don't run into these problems all ops know a story about. It helps that systemd makes it easier to configure dependencies so that only the units depending on remote fs stall when it is unavailable.
- TheyW0ntL1sten 11y agoOne time I was writing this long story in a text editor that crashed so I stopped writing. Nevermore.
- jabl 11y ago> So you just don't use remote filesystems? That's a solution! No, you mount them with autofs, of course.
- snuxoll 11y agoautofs is great, combined with NFS4 and FreeIPA it's even not a total pain in the butt to configure on a whole farm of servers (having my home directory easily available with my ZSH configuration from every system I log into is great.)
- karlshea 11y agoI found out about autofs when I was trying to figure out some SMB issues while mounting NAS shares on a media server. It was so ridiculously easy to set up. All of the "copy and paste" newbie answers always involve modifying fstab and there are always issues on boot, but autofs just works. It makes me wonder why it's not recommended as often.