[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
|
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
10031.0. "Why does /usr insist on an fsck after controlled shutdown" by NNTPD::"[email protected]" (Ken Miller) Tue Jun 03 1997 12:31
Hi,
I've got a customer who's running V3.2G on a 4000 (C2 Security, special
auditing appl) and a system disk with 6 ufs disk partitions and a swap
partition all on one disk (none of them overlapping).
The problem is starting about 2 weeks ago, /usr declares "Dirty File System"
whenever they reboot. Even sync;sync;sync followed by a "shutdown -h now",
and then >>> boot drops them in single-user reporting a "dirty /usr". An
fsck -Y /usr always yields no errors, and can be mounted and used with no
problems until the next reboot.
The only processes running are system processes (including ypserv & audit) and
the customer's audit appl, but they'd all been running with no updates for
several months before this started happening.
Any ideas on how to further nail down the problem? It's a secure site, so
it's
rather difficult to get access to. Thus, I'd like to collect several ideas
before I get back on the machine.
Thanks in advance,
== ken miller ==
----------------------------------------------------------
[email protected] http://www.gsg.dec.com/miller
Digital (Metro DC Area) FGR Engineering, COP Facility
PGP '96 1F 82 38 7A 38 6C ED E5 9C 81 D2 D2 74 87 04'
[Posted by WWW Notes gateway]
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 10031.1 | | finder.uvo.dec.com::COFFEYJ | La Feline Flooz - a unix cat | Tue Jun 03 1997 13:00 | 12 |
| >Even sync;sync;sync followed by a "shutdown -h now",
The prefered way to shut down a system is to use init if you
want a clean shutdown rather than litterally just shut it all
down now.
Init runs the rc*.d shutdown scripts and generally should shut
off all those little processes that are still writing to or
reading from /usr and causing it to be unclean when you reboot.
Jo
|
| 10031.2 | | WONDER::REILLY | Sean Reilly, Alpha Servers, DTN 223-4375 | Thu Jun 05 1997 14:21 | 2 |
|
So does shutdown, if you take away the "-h" option.
|