| 28 Jan 2023 |
 @lily:lily.flowers | * It would, yes. I like that idea better | 22:25:28 |
 @elvishjerricco:matrix.org | or, realistically, we can mount the file system readonly and extract it from there. That would avoid dangers with mounting before resume | 22:25:32 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
or, realistically, we can mount the file system readonly and extract it from there. That would avoid dangers with mounting before resume It does not. The kernel faq page for resume says that still would eat your data | 22:26:05 |
| @lily:lily.flowers | Iirc | 22:26:10 |
| @elvishjerricco:matrix.org | oh really? | 22:26:14 |
| @elvishjerricco:matrix.org | even if you unmount it? | 22:26:16 |
| @elvishjerricco:matrix.org | does just having stuff in the page cache pre-resume fuck with it? | 22:26:34 |
| @elvishjerricco:matrix.org | where is that faq? | 22:27:04 |
| @lily:lily.flowers | About initrd resume:
It is vital that this be done prior to remounting any filesystems (even as read-only) otherwise data may be corrupted.
At https://www.kernel.org/doc/html/latest/power/swsusp.html | 22:27:45 |
| @lily:lily.flowers | In reply to @elvishjerricco:matrix.org
does just having stuff in the page cache pre-resume fuck with it? Maybe. I'm not quite sure, it doesn't elaborate | 22:28:03 |
| @elvishjerricco:matrix.org | Yea, that's annoying. If you're going to warn about it, you should explain it | 22:28:45 |
| @elvishjerricco:matrix.org | * Yea, that's annoying. If they're going to warn about it, they should explain it | 22:28:52 |
| @lily:lily.flowers | (I would hope mounting an unrelated disk that wasn't present at hibernation would be fine, but idk why it's a problem to begin with so maybe not) | 22:29:15 |
| @elvishjerricco:matrix.org | An EFI variable should work, right? lol | 22:29:44 |
| @lily:lily.flowers | You know, that's an even better idea | 22:30:16 |
| @lily:lily.flowers | Cursed, but better | 22:30:23 |
| @elvishjerricco:matrix.org | lol great | 22:30:38 |
| @elvishjerricco:matrix.org | I did not mean for that to be taken seriously | 22:30:44 |
| @elvishjerricco:matrix.org | but yea it might be better | 22:30:49 |
| @elvishjerricco:matrix.org | Well, the issue author created a version of the hibernate test that exhibits the issue | 22:31:33 |
| @elvishjerricco:matrix.org | they just hard coded the resume offset | 22:31:38 |
| @elvishjerricco:matrix.org | so that's fragile and we can't actually have that in nixpkgs :P | 22:31:52 |
| @elvishjerricco:matrix.org | but it helps diagnose for now | 22:31:57 |
| @lily:lily.flowers | I wonder if one of the more esoteric filesystems in the kernel allows you to either deterministically know or set a specific offset for a file | 22:32:58 |
| @elvishjerricco:matrix.org | oh | 22:33:59 |
| @elvishjerricco:matrix.org | oh no | 22:34:00 |
| @elvishjerricco:matrix.org | best bad idea yet | 22:34:03 |
| @elvishjerricco:matrix.org | networking | 22:34:06 |
| @elvishjerricco:matrix.org | the test machine tells a server machine the offset, which remembers it until initrd (using initrd networking) asks for it | 22:34:41 |
| @elvishjerricco:matrix.org | absolutely cursed | 22:34:45 |
