From: Shriram R <shriram1976@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Effect of deleting executables of running programs
Date: Wed, 18 Aug 2004 13:11:00 -0700 (PDT) [thread overview]
Message-ID: <20040818201100.54131.qmail@web11413.mail.yahoo.com> (raw)
In-Reply-To: <200408181901.i7IJ1FK08538@orbit-fe.eng.netapp.com>
Yes, the nodes were accessing the executable over NFS.
-shriram
--- Brian Pawlowski <beepy@netapp.com> wrote:
> How were the nodes accessing the executable? Over
> NFS?
>
> > Hi,
> >
> > Newbie here. I am not sure if I am sending this
> email
> > to the right list. My apologies if I am not and I
> > would be happy if someone can point me to the
> right
> > mailing list.
> >
> > We have a 24 node/48 processor cluster in our lab
> with
> > the following specs.
> >
> > AMD Athlon
> > Redhat 7.3
> > Kernel version - 2.4.19
> >
> > I had around 10 jobs that had been running on the
> > cluster for about 15 or so days. These were
> > using a common executable "abcd.out" (compiled in
> > fortran 90). After they had been running for
> > about 15 days, I made the mistake of deleting
> > abcd.out. Immediately about
> > 3 or 4 of my jobs crashed with a "bus error".
> But,
> > some 6-7 of my jobs
> > continued running. I had 2 questions with regards
> to
> > this :
> >
> > a) I always thought that once a job is running,
> the
> > executable is
> > entirely loaded into memory and the abcd.out
> file
> > is no longer needed.
> > If so, then why does the a running job crash on
> > deleting abcd.out ?
> >
> > b) To what extent can I trust that the rest of the
> 6-7
> > jobs that are
> > running have not been affected by this deletion
> of
> > "abcd.out" ?
> >
> > Thanks in advance,
> > shriram.
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > New and Improved Yahoo! Mail - 100MB free storage!
> > http://promotions.yahoo.com/new_mail
> > -
> > To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
next parent reply other threads:[~2004-08-18 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200408181901.i7IJ1FK08538@orbit-fe.eng.netapp.com>
2004-08-18 20:11 ` Shriram R [this message]
2004-08-18 23:41 ` Ryan Cumming
2004-08-18 18:16 Shriram R
2004-08-18 19:18 ` Chris Wedgwood
2004-08-23 13:30 ` jlnance
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=20040818201100.54131.qmail@web11413.mail.yahoo.com \
--to=shriram1976@yahoo.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome