And even with the regression to the -27 kernel on my 8.04.4 servers, I
have 25 nbd-server processes laying around with only 3 users logged in
as of this morning.

r...@www:~# ps auxw |grep nbd |grep tmp
nobody    3655  0.0  0.0   9864  1068 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.DgDqzq3650 -C /dev/null
nobody    3866  0.0  0.0   9860  1068 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.ygbtQm3863 -C /dev/null
nobody    3911  0.0  0.0   9860  1068 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.TuPsaV3908 -C /dev/null
nobody    4283  0.0  0.0   9864  1068 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.jaLfkL4280 -C /dev/null
nobody    5614  0.0  0.0   9864  1068 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.VShxTw5611 -C /dev/null
nobody    6962  0.0  0.0   9860  1176 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.avKZON6957 -C /dev/null
nobody   10618  0.0  0.0   9864  1068 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.xsCkl10615 -C /dev/null
nobody   11135  0.0  0.0   9860  1068 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.YQdfV11132 -C /dev/null
nobody   12123  0.0  0.0   9860  1068 ?        S    07:38   0:00
/bin/nbd-server 0 /tmp/tmp.peNhQ12120 -C /dev/null
nobody   12931  0.0  0.0   9856  1064 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.VLZyX12925 -C /dev/null
nobody   13709  0.0  0.0   9860  1068 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.LNcpp13705 -C /dev/null
nobody   14133  0.0  0.0   9860  1068 ?        S    08:24   0:00
/bin/nbd-server 0 /tmp/tmp.TObSR14130 -C /dev/null
nobody   14292  0.0  0.0   9856  1064 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.BwhOz14289 -C /dev/null
nobody   14819  0.0  0.0   9856  1064 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.JcPXj14816 -C /dev/null
nobody   14843  0.0  0.0   9860  1064 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.EpLtc14840 -C /dev/null
nobody   15276  0.0  0.0   9860  1176 ?        S    08:42   0:00
/bin/nbd-server 0 /tmp/tmp.DMRHu15273 -C /dev/null
nobody   15698  0.0  0.0   9856  1064 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.MDpZc15692 -C /dev/null
nobody   15776  0.0  0.0   9864  1068 ?        S    08:46   0:00
/bin/nbd-server 0 /tmp/tmp.xPtsW15773 -C /dev/null
nobody   16367  0.0  0.0   9864  1068 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.UUjlV16361 -C /dev/null
nobody   16593  0.0  0.0   9856  1064 ?        S    08:56   0:00
/bin/nbd-server 0 /tmp/tmp.RNdWy16590 -C /dev/null
nobody   17296  0.0  0.0   9860  1176 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.PYHfd17293 -C /dev/null
nobody   19399  0.0  0.0   9860  1068 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.xGqYB19396 -C /dev/null
nobody   26419  0.0  0.0   9860  1064 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.FxzGu26415 -C /dev/null
nobody   27489  0.0  0.0   9860  1064 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.YLeae27486 -C /dev/null
nobody   32566  0.0  0.0   9864  1176 ?        S    Aug05   0:00
/bin/nbd-server 0 /tmp/tmp.yCUde32563 -C /dev/null


As I understand it, you can safely kill the processes that relate to
users no longer logged in. The problem is that this was done
automagically up until a few weeks ago. So, the problem was not
introduced with kernel 2.6.24-28

-Michael


On Fri, Aug 6, 2010 at 9:14 AM, grant <gr...@ajrs.com> wrote:
>
> Ok checked today and I have 17 nbdrootd processes running.
>
> ps aux | grep nbdrootd | grep -v grep
> nobody    8390  0.0  0.0   4092   640 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8396  0.0  0.0   4092   640 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8399  0.0  0.0   4092   644 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8406  0.0  0.0   4092   640 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8424  0.0  0.0   4092   644 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8434  0.0  0.0   4092   644 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8438  0.0  0.0   4092   640 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8444  0.0  0.0   4092   640 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8448  0.0  0.0   4092   640 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8454  0.0  0.0   4092   640 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8466  0.0  0.0   4092   640 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8474  0.0  0.0   4092   640 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8480  0.0  0.0   4092   640 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8483  0.0  0.0   4092   644 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody    8493  0.0  0.0   4092   644 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody   22423  0.0  0.0   4092   644 ?        Ss   Aug04   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
> nobody   28640  0.0  0.0   4092   640 ?        Ss   Aug05   0:00 /bin/sh
> /usr/sbin/nbdrootd /opt/ltsp/images/i386.img
>
>
> This is after I killed all but te one I was sure a user was using
> yesterday.  A client that runs displays around the office was also
> connected to that server at the time I killed the processes yesterday.
> It is still running fine, I did not search out it's process because I
> did not care if it needed to be restarted.  So are these process's
> really still needed?
>
> Grant
>
>
>
> On 08/05/2010 09:07 AM, grant wrote:
> > Michael,
> >
> > Yes, I end up with a /tmp dir full of swap files. To remedy I made a
> > second swap server, but I still have a large number of nbdrootd
> > processes running.  There was a entry in the /etc/hosts.allow for
> >
> > # nbdrootd: ALL: keepalive
> >
> > as you see  I commented it out yesterday but I still have a large number
> > of those jobs - 67 to be exact.
> >
> > I just killed all but the one I could determine was a user from today
> > and will see if that helped out.  I am not really sure what to do on the
> > /tmp swap files, I had not been deleting any of those myself because I
> > thought they were made on boot of the client, not on logon.
> >
> > grant
> >
> > On 08/04/2010 08:23 AM, Michael Blinn wrote:
> >
> >> I also have this issue in 8.04.4  --  was researching the issue and
> >> then fell to pneumonia.
> >>
> >> Are you say, the tmp files created by nbdswapd are also still left
> >> around because nbdswapd processes are still running. This is what got
> >> me - 8 GB of /tmp fills in a few days, killing the server.
> >>
> >> Now that I'm back among the living I'll start doing some more research.
> >>
> >> On Wed, Aug 4, 2010 at 8:55 AM, grant<gr...@ajrs.com>   wrote:
> >>
> >>
> >>> Hello,
> >>>
> >>> I have recently had some issues with nbd and was wondering if this was
> >>> normal.
> >>>
> >>> The first is one of my ubuntu 10.04 servers has about 65 nbdrootd
> >>> processes running right now, they are all for serving the image, moved
> >>> nbd swap to swap server a bit ago.  I only have about 10 users per day
> >>> on that server at max.  Some of these proceses are going on 15 days
> >>> old.  Is there something I am missing that cleans these up or when is it
> >>> safe to remove these?
> >>>
> >>>
> >>> The second issue  I had actually came before, and was related to the nbd
> >>> swap issue. It is actually what drove me to move the nbd swap. I was
> >>> testing some get_hosts scripts and soon noticed that I had a 100% full
> >>> hard drive on my machine, I looked in the /tmp directory and saw quite a
> >>> few swap files. I started to delete cautiously as I did not want to
> >>> interrupt any users. The space would not become available to me, not
> >>> until I went through and killed the nbd process.
> >>>
> >>> Is there some point that it is safe to delete a nbd swap file and kill
> >>> off it's process? I was thinking no because I am under the impression
> >>> that file is created on client boot, not on logon.
> >>>
> >>> Thank you.
> >>>
> >>> Grant
> >>>
> >>> ------------------------------------------------------------------------------
> >>> The Palm PDK Hot Apps Program offers developers who use the
> >>> Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> >>> of $1 Million in cash or HP Products. Visit us here for more details:
> >>> http://p.sf.net/sfu/dev2dev-palm
> >>> _____________________________________________________________________
> >>> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
> >>>        https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> >>> For additional LTSP help,   try #ltsp channel on irc.freenode.net
> >>>
> >>>
> >>>
> >>
> >>
> >>
> > ------------------------------------------------------------------------------
> > The Palm PDK Hot Apps Program offers developers who use the
> > Plug-In Development Kit to bring their C/C++ apps to Palm for a share
> > of $1 Million in cash or HP Products. Visit us here for more details:
> > http://p.sf.net/sfu/dev2dev-palm
> > _____________________________________________________________________
> > Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
> >        https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> > For additional LTSP help,   try #ltsp channel on irc.freenode.net
> >
> >
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _____________________________________________________________________
> Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
>      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help,   try #ltsp channel on irc.freenode.net



--
Michael Blinn
People Places, Inc.
---
CONFIDENTIALITY NOTICE:
This message, and any attachments that may accompany it, contain
information that is intended for the use of the individual or entity
to which it is addressed and may contain information that is
privileged, confidential, or otherwise exempt from disclosure under
applicable law. If the recipient of this message is not the intended
recipient, any disclosure, copying, or other use of this communication
or any of the information, which it contains is unauthorized and
prohibited.  If you have received this message in error, please notify
the original sender by return mail and delete this message, along with
any attachments, from your computer. Thank you.

------------------------------------------------------------------------------
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.freenode.net

Reply via email to