home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.sun.admin
- Path: sparky!uunet!paladin.american.edu!howland.reston.ans.net!zaphod.mps.ohio-state.edu!cs.utexas.edu!torn!nott!cunews!mikey
- From: mikey@yoho.carleton.ca (Mike G McFaul)
- Subject: Re: tunefs on /usr
- Message-ID: <1992Dec22.154837.21652@cunews.carleton.ca>
- Sender: news@cunews.carleton.ca (News Administrator)
- Organization: Carleton University, Ottawa, Canada
- References: <ByG0ny.KK1@uxa.ecn.bgu.edu> <1992Dec6.000641.3438@nic.csu.net>
- Date: Tue, 22 Dec 1992 15:48:37 GMT
- Lines: 39
-
- >In article <ByG0ny.KK1@uxa.ecn.bgu.edu> mflll@uxa.ecn.bgu.edu (Dr. Laurence Leff) writes:
- >>I am trying to run tunefs on the /usr file system. Of course this
- >>is part of the two file systems (/root and /usr) that are brought up
- >>on bootup.
- >>
- >>Thus, we can't dismount it to run tunefs. This is even true when we
- >>come up single user (boot with -s option)
- >>
- >>We are on 4.1.1 operating system on Sun III's.
- >>
- >>Does anyone know a method of running tunefs on the /usr file system.
- >>We want to reduce the disk space allocated to root on this file system.
- >>
-
- Well it can be done, without unmounting anything...
-
- What you do is come up in single user mode, then SYNC your disks, then
- perform your 'tunefs' command, then interrupt your system, with either
- 'L1-A' or a break (for those machines without a sun console), then
- boot your system without SYNCing your disks. Yes this sounds
- dangerours, but it works because you have SYNC'ed the disks prior to
- the tunefs and the only extra thing you have done is the 'tunefs'
- command. And since your in single-user mode, there is no other
- activity other than you doing the tunefs to worry about.
-
- From the 'BUGS' section of manpage on 'tunefs'
-
- BUGS
- This program should work on mounted and active file systems.
- Because the super-block is not kept in the buffer cache, the
- program will only take effect if it is run on dismounted
- file systems; if run on the root file system, the system
- must be rebooted.
-
- The last line there gave me the hint I needed to try this out... I
- have performed this on a number of machines running 4.1.2 and 4.1.3
- and they all worked...
-