| 1 |
On 12/10/18 8:03 PM, Tsukasa Mcp_Reznor wrote: |
| 2 |
> Has anyone managed to get suspend/resume to work on diskless machines |
| 3 |
> using NFS as the root? |
| 4 |
|
| 5 |
~blink~ |
| 6 |
|
| 7 |
I haven't tried to suspend / resume diskless machines. (I've not done |
| 8 |
much with diskless machines, but it's on my to do list.) |
| 9 |
|
| 10 |
But I don't think I would have thought about trying to suspend / resume |
| 11 |
a diskless machine. |
| 12 |
|
| 13 |
Are we talking about a wired Ethernet network connection with static |
| 14 |
IP(s)? Or something more complex? |
| 15 |
|
| 16 |
Aside: I'm wondering why a diskless machine is using suspend / resume. |
| 17 |
If you're bored, I'd like to have my (apparently limited) world view |
| 18 |
expanded. |
| 19 |
|
| 20 |
> Suspend works like normal, but resume hard locks, can't seem to get any |
| 21 |
> error's or anything as it's not sending to any log files naturally. |
| 22 |
|
| 23 |
Have you tried using any network based logging? |
| 24 |
|
| 25 |
Can syslog log to a network block device? |
| 26 |
|
| 27 |
Doesn't the kernel have some network logging? Or the ability to log |
| 28 |
debug info somewhere other than a file? |
| 29 |
|
| 30 |
> I have 3 machines currently running this setup, just trying to save |
| 31 |
> some power. If it helps they are all using Realtek NICs. |
| 32 |
|
| 33 |
Okay. I conceptually get saving power. |
| 34 |
|
| 35 |
How are you waking them up? User interaction? Clock? Magic packet? |
| 36 |
|
| 37 |
> My google-fu hasn't turned up anything in the last 5 years. |
| 38 |
|
| 39 |
So, you've been working on it for a while. |
| 40 |
|
| 41 |
Are any of your problems related to stale file handles? I.e. the |
| 42 |
diskless NFS client disagreeing with the NFS server about the state of |
| 43 |
the files? Is the NFS server closing the files after a timeout? |
| 44 |
|
| 45 |
> Thanks |
| 46 |
|
| 47 |
You're welcome. But I'm not sure I helped. I would like to learn what |
| 48 |
you figure out. |
Archives