HP3000-L Archives

July 2004, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Matthew Perdue <[log in to unmask]>
Reply To:
Date:
Wed, 28 Jul 2004 01:36:11 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
donna garverick <[log in to unmask]> wrote:

>hi all!
>
>a couple of questions...
>
>on a USER volume, if free space is consumed...what happens?  does the
>system crash (i suspect 'can the system crash' would be true...)?  for
>accounts residing on that volume, what happens to any users/jobs of
>those accounts?  any good war stories?
>
>in the same way....for an account with a LIMIT, what happens when the
>limit it met.  i suspect the system would be fine (no crashes) but what
>about users or jobs?         - d

Writing on speculation, as I've not seen a USER private volume actually
completely fill up and have 0 free space (I've seen them come very,
very close, though) I would imagine the XM would queue the file
transactions and then jobs and sessions would start aborting as no more
extents can be allocated. I imagine Jeff Vance, someone at the vCSY
labs or on the HP3000-L can be more definitive.

However, speaking from actual experience, when an account with a disc
space limit reaches that limit, jobs and sessions will abort as the
file system attempts to allocate new extents with "out of disc space"
errors. If the LIMIT is cpu seconds or connect minutes, the limits are
checked when a session or job logs on; no jobs or sessions will be
aborted if the limits are reached during their execution and they will
proceed to normal EOJ or EOS respectively.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2