[03:49] <dirtycajun> So i have a zfs mount that is mounted at /mnt/media and a ext4 mount mounted at /mnt/media/storage. I need to ensure that the ext4 mount does not mount until zfs mounts. Is there a more graceful way then @reboot crontab hacky script
[03:54] <tds> dirtycajun: what version of ubuntu and zfs?
[03:54] <sarnold> dirtycajun: if /mnt/media is mounted by zfs and /mnt/media/storage is listed in /etc/fstab, there's a pretty good chance the right thing will already happen
[03:55] <sarnold> dirtycajun: if /mnt/media is LEGACY then you ought to be able to stick both lines in /etc/fstab and I'd expect that to work too
[03:56] <dirtycajun> Ubuntu 18.04.3 and zfs 0.7.5-1ubuntu16.4
[03:56] <dirtycajun> unfortunately it literally NEVER does it in the right order. And since the second happens first, the first cannot happen as its in use
[03:57] <dirtycajun> and yes, zfs is mounted by zfs and ext4 is mounted by fstab in this case
[03:57] <tds> ah, so before zfs-mount-generator, i think that's only in 0.8 (and actually fixes this)
[03:58] <tds> you could probably use the x-systemd options in fstab so your mount only happens after zfs-mount.service though?
[03:59] <dirtycajun> ,x-systemd.requires=zfs-mount.service
[03:59] <dirtycajun> i have that currently tho
[03:59] <dirtycajun> and damn. does 20.04 bundle with 8.* zfs ?
[04:00] <dirtycajun> erm 0.8.*
[04:00] <sarnold> yes, that the moment it's a 0.8.2 https://launchpad.net/ubuntu/+source/zfs-linux
[04:00] <dirtycajun> so hack it for 4 months then upgrade. could be worse
[04:01] <dirtycajun> thank yall.
[04:03] <tds> hmm, that is odd - and the generated mount unit has requires set properly and everything?
[04:03] <sarnold> dirtycajun: if you've got the time this might be worth a bug report; 18.04 will live on for a while, and maybe it'd be nice for this to be fixed (no promises of course, but an unfiled bug can't be fixed :)
[04:04] <dirtycajun> True. I would need to dig through bootup and logs to see exactly where its shitting the bed though to file the report. Its a longstanding issue. It actually causes castcading problems that i have fixed like docker starting which lets k8s pods schedule which cant reach a mount etc
[04:06] <dirtycajun> tds looks like 0.7.13 is the release of zfs-mount-generator
[04:06] <dirtycajun> still not at that freeze but an fyi
[04:07] <sarnold> dirtycajun: ubuntu-bug zfsutils-linux    will probably get to the right place
[07:26] <lordievader> Good morning
[09:59] <tilerendering> not sure whether this is the right channel to ask, but: am I correct in the assumption that Ryzen-based servers are not really made for that purpose? i.e. the Ryzen being a workstation cpu (low latency) rather than one assuring high throughput?
[10:37] <tomreyn> tilerendering: Yes, that's correct. As Intels has a server CPU line, Xeon, AMD also has one, called Epyc.
[10:40] <tomreyn> this said, there are also companies running datacenters with intel desktop/workstation cpu based dedicated 'servers', since this can still be worthwhile for the cheaper segment.
[10:42] <tomreyn> oh, you cross-posted :-/
[10:59] <tilerendering> tomreyn: I wonder whether I should migrate my proxmox on ryzen to proxmox on xeon
[11:01] <tomreyn> tilerendering: i don't think i can help you make this decision.
[18:57] <dannf> where can i find docs on netbooting subiquity? google wasn't much help there
[21:31] <albech> just spun up a backup of an old server. Within that snapshot is the system disk which is accessible, but there is also another disk which is marked data on the hypervisor.. That particular disk doesnt appear in fstab and when i try to mount it i get an error that it is: wrong fs type, bad option, bad superblock. Looking and the disk in fstab doesnt reveal anything else.. Could this some encrypted partition.?
[21:32] <albech> Note that I had to chroot into the system and create a new sudo user
[21:32] <albech> and I didnt build the system initially
[21:33] <albech> went through old history and no signs of mounting this other drive
[21:50] <ahasenack> what does fdisk -l say about that disk?
[23:46] <albech> ahasenack: https://paste.ubuntu.com/p/bC4xqbPTsn/