jensen@adobe.com (Freddy Jensen) (12/13/90)
Hi Folks,
When I run fsck (AIX 3.1.1, RS/6000) I sometimes get a whole
bunch of these messages:
Unref file (NOT CLEARED)
Unref file I=55565 owner=root mode=120777
size=24 mtime=Dec 05 11:34 1990 (NOT RECONNECTED)
Unref file (NOT CLEARED)
Unref file I=55566 owner=root mode=120777
size=24 mtime=Dec 05 11:34 1990 (NOT RECONNECTED)
Unref file (NOT CLEARED)
Unref file I=55567 owner=root mode=120777
size=24 mtime=Dec 05 11:34 1990 (NOT RECONNECTED)
Unref file (NOT CLEARED)
Unref file I=55568 owner=root mode=120777
size=24 mtime=Dec 05 11:34 1990 (NOT RECONNECTED)
Unref file (NOT CLEARED)
Unref file I=55569 owner=root mode=120777
size=24 mtime=Dec 05 11:34 1990 (NOT RECONNECTED)
.
.
.
etc.
I have not been able to get fsck to reconnect the seemingly
lost files (fsck -p /dev/hd4 won't do it).
All suggestions welcome.
Thanks
Freddy
-------------
Freddy Jensen
Display Postscript Group
Adobe Systems Incorporated
1585 Charleston Road, P.O. Box 7900
Mountain View, CA 94039-7900
email: jensen@adobe.com
adobe!jensen@sun.com
adobe!jensen@decwrl.dec.com
...!{decwrl,sun,uunet,apple}!adobe!jensen
phone: (415) 962-3869 / 961-4400jensen@adobe.com (Freddy Jensen) (12/15/90)
>Article 2827 of comp.unix.aix: >Path: adobe!jensen >From: jensen@adobe.com (Freddy Jensen) >Newsgroups: comp.unix.aix >Subject: fsck problems on RS/6000 >Date: 12 Dec 90 22:34:49 GMT >Lines: 47 > >Hi Folks, > > When I run fsck (AIX 3.1.1, RS/6000) I sometimes get a whole > bunch of these messages: > >Unref file (NOT CLEARED) >Unref file I=55565 owner=root mode=120777 >size=24 mtime=Dec 05 11:34 1990 (NOT RECONNECTED) >Unref file (NOT CLEARED) >Unref file I=55566 owner=root mode=120777 >size=24 mtime=Dec 05 11:34 1990 (NOT RECONNECTED) > . > . > . > etc. > >I have not been able to get fsck to reconnect the seemingly >lost files (fsck -p /dev/hd4 won't do it). > >All suggestions welcome. > >Thanks > >Freddy Hi again, I just noticed that I get this message from fsck, when I start it up: ** Checking /dev/hd4 (/) MOUNTED FILE SYSTEM; WRITING SUPPRESSED; ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Is this the reason that fsck refuses to reconnect the lost files ? If that's the case, how to I get around this problem (it's hard to unmount the root filesystem ;-). Thanks Freddy
gs26@prism.gatech.EDU (Glenn R. Stone) (12/16/90)
In <9150@adobe.UUCP> jensen@adobe.com (Freddy Jensen) writes: > > When I run fsck (AIX 3.1.1, RS/6000) I sometimes get a whole > > bunch of these messages: > > > >Unref file (NOT CLEARED) > >Unref file I=55565 owner=root mode=120777 > >size=24 mtime=Dec 05 11:34 1990 (NOT RECONNECTED) > I just noticed that I get this message from fsck, when I start it up: > ** Checking /dev/hd4 (/) MOUNTED FILE SYSTEM; WRITING SUPPRESSED; Boot from floppy, select system maintenance, run /etc/continue, and fsck from there. That way you're running off the ramdisk, not the root file system. -- Glenn R. Stone (gs26@prism.gatech.edu)
marc@arnor.uucp (12/17/90)
Reminder - you should not expect fsck to work correctly on a mounted file system in AIXV3. To actually check/repair /dev/hd4, which is mounted as root, you must 1. boot from diskette. 2. select maint. mode 3. type /etc/continue hdisk0 exit (replace hdisk0 with boot disk if not hdisk0) 4. now fsck /dev/hd4 -- Marc Auslander
dcm@nostromo.austin.ibm.com (craig miller) (12/18/90)
One more point about fsck on mounted filesystems: the behaviour is pretty much unpredictable, especially if the filesystem is active. Also there is no way to get fsck to modify a mounted filesystem on AIXV3. We decided a long time ago that this was not A Good Thing(tm) due to the journaling. Craig ------ Craig Miller Locus Computing Corporation, Austin, TX. UUCP: ..!cs.utexas.edu!ibmchs!auschs!slaughter!dcm "I do not represent LCC or IBM. I represent myself (usually)."
bware@slate.mines.colorado.edu (Bob Ware) (12/19/90)
We have had problems with corrupted filesystems on RS/6000's running AIX 3.1 with the 3001 update. We just got the word from IBM that there is a problem with the stdout stream that can cause filesystem corruption under 3001. The word is that it is fixed in 3002 (the fsck file is not what is changed, though). My advice: DO NOT RUN FSCK UNTILL YOU HAVE 3002 INSTALLED! -- Bob Ware, Colorado School of Mines, Golden, Co 80401, USA (303) 273-3987 bware@mines.colorado.edu bware@slate.mines.colorado.edu bware@mines.bitnet