home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sun.admin
- Path: sparky!uunet!wupost!darwin.sura.net!sgiblab!daver!quack!mrapple
- From: mrapple@quack.sac.ca.us (Nick Sayer)
- Subject: Dangerous scenario (was Re: mounting 4.1.1 fs on a 4.1.2 sys)
- Message-ID: <fSvFS8O@quack.sac.ca.us>
- Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'.
- References: <2328@itexjct.jct.ac.il> <1992Sep8.215827.6808@zia.aoc.nrao.edu>
- Date: Sat, 12 Sep 1992 15:57:45 GMT
- Lines: 23
-
- How's this for a scary scenario:
-
- Mount a 4.1.2 file system on a 4.1.1 machine.
-
- The 4.1.1 machine crashes leaving a corruption behind in the file
- system (something fsck would catch and fix when it preens on reboot).
-
- Mount the file system BACK on a 4.1.2 machine and reboot.
-
- 4.1.2's fsck will see that the 'clean' flag hasn't changed since
- it was last mounted on a 4.1.2 system and pass the file system
- without checking it.
-
- Is this a possibility?
-
- If so, the moral is to manually run fsck anytime you move a file system
- from one OS rev to another.
-
- --
- Nick Sayer <mrapple@quack.sac.ca.us> |
- N6QQQ @ N0ARY.#NOCAL.CA.USA.NA | "Hubba hubba hubba, pig bastard."
- 37 19 49 N / 121 57 36 W |
- +1 408 249 9630, log in as 'guest' | -- Scorpio (from Dirty Harry)
-