public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Root on NFS Suspend/Resume support
Date: Tue, 11 Dec 2018 18:37:04 +0000	[thread overview]
Message-ID: <A92C55B9-01FC-4854-824F-6477B143D9A2@antarean.org> (raw)
In-Reply-To: <DM5PR15MB1722C76411BE1C802695C6C1F0A60@DM5PR15MB1722.namprd15.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 4165 bytes --]

On December 11, 2018 11:23:27 AM UTC, Tsukasa Mcp_Reznor <mcp_reznor@hotmail.com> wrote:
>________________________________________
>From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
>Sent: Monday, December 10, 2018 10:14 PM
>To: gentoo-user@lists.gentoo.org
>Subject: Re: [gentoo-user] Root on NFS Suspend/Resume support
>
>On 12/10/18 8:03 PM, Tsukasa Mcp_Reznor wrote:
>&gt; Has anyone managed to get suspend/resume to work on diskless
>machines
>&gt; using NFS as the root?
>
>~blink~
>
>I haven't tried to suspend / resume diskless machines.  (I've not done
>much with diskless machines, but it's on my to do list.)
>
>But I don't think I would have thought about trying to suspend / resume
>a diskless machine.
>
>Are we talking about a wired Ethernet network connection with static
>IP(s)?  Or something more complex?
>
>Aside: I'm wondering why a diskless machine is using suspend / resume.
>If you're bored, I'd like to have my (apparently limited) world view
>expanded.
>
>&gt; Suspend works like normal, but resume hard locks, can't seem to
>get any
>&gt; error's or anything as it's not sending to any log files
>naturally.
>
>Have you tried using any network based logging?
>
>Can syslog log to a network block device?
>
>Doesn't the kernel have some network logging?  Or the ability to log
>debug info somewhere other than a file?
>
>&gt; I have 3 machines currently running this setup, just trying to
>save
>&gt; some power.  If it helps they are all using Realtek NICs.
>
>Okay.  I conceptually get saving power.
>
>How are you waking them up?  User interaction?  Clock?  Magic packet?
>
>&gt; My google-fu hasn't turned up anything in the last 5 years.
>
>So, you've been working on it for a while.
>
>Are any of your problems related to stale file handles?  I.e. the
>diskless NFS client disagreeing with the NFS server about the state of
>the files?  Is the NFS server closing the files after a timeout?
>
>&gt; Thanks
>
>You're welcome.  But I'm not sure I helped.  I would like to learn what
>you figure out.
>
>
>
>
>You're totally correct, more information would be beneficial, here
>goes.
>All machines are Wired 1Gbps connections.
>Uefi IP4 network stack sends dhcp request, gets boot file pxelinux.efi,
>the default entry sends the linux kernel (no initramfs needed, firmware
>added to kernel image).
>Another good note is the kernel contains the command line built-in for
>using root on NFS.
>Machine loads, mounts the required mount points through NFS4.2 (so much
>better than the old NFS 3 speeds).
>LightDM loads and users are free to work, in this case family members
>playing Steam/Diablo 3/etc.
>I switched to using Root on NFS for alot of reasons.
>
>Maintaining 4 gentoo installs on machines of varying specs and
>remembering to update each with good updates added a fair amount of
>administration time. (4, because the server is included)
>
>Using chroots on the server as binary build hosts for each machine
>solves some problems, but increases space requirements quite a bit, and
>adds latency if you want to use it while it's emerging anything, plus
>compiling say Libreoffice or whatever 3+ times in a row is pretty slow.
>
>Side note, If anyone else runs diskless I have a patch for wine I can
>send out that returns the nfs mount as a fixed hard drive, there are a
>few apps/games that refuse to install/run on a network share, and a
>patch for steam that removes the file locking issues so updates run
>quick and smooth (neither will ever be upstreamable, people have tried
>in the past)
>
></gtaylor@gentoo.tnetconsulting.net>
>
>Thanks for your response, I'd love to help if you have any more
>questions, it's been a fun experience for me for sure. Also,
>cachefilesd if there's a drive available, makes everything feel like
>it's not a networked machine at all here.

If you want to resume from NFS, you will need an initramfs that correctly passes the swap device for resuming.
I would try the same method as resuming from encrypted swap.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 4462 bytes --]

  parent reply	other threads:[~2018-12-11 18:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11  3:03 [gentoo-user] Root on NFS Suspend/Resume support Tsukasa Mcp_Reznor
2018-12-11  3:14 ` Grant Taylor
2018-12-11 11:23   ` Tsukasa Mcp_Reznor
2018-12-11 18:04     ` Grant Taylor
2018-12-11 22:53       ` Tsukasa Mcp_Reznor
2018-12-11 23:26         ` Grant Taylor
2018-12-11 18:37     ` J. Roeleveld [this message]
2018-12-11 22:59       ` Tsukasa Mcp_Reznor
2018-12-13 21:03         ` J. Roeleveld
2018-12-13 21:08           ` Tsukasa Mcp_Reznor
2018-12-14 14:58             ` Daniel Frey
2018-12-14 20:37               ` Tsukasa Mcp_Reznor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=A92C55B9-01FC-4854-824F-6477B143D9A2@antarean.org \
    --to=joost@antarean.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox