Date: Fri, 16 Nov 2001 09:02:42 -0600 From: "Joshua B. Derck" <JOSH@nph.com> Subject: RE: Unattached Inode Message-id: <0BC5797545B3D311BB00009027DCCBA70255B460@ZETA>
Thank you for all you help my box is back up
-----Original Message-----
From: Brian Densmore [mailto:DensmoreB@ctbsonline.com]
Sent: Friday, November 16, 2001 8:57 AM
To: Joshua B. Derck
Cc: KCLUG (E-mail)
Subject: RE: Unattached Inode
Well, sometimes that happens. You need to boot the system, log in as root
and run fsck (file system check). It will scan your harddrive, and fix the
errors hopefully. It's interactive, so just follow along. If there is
something seriously wrong the boot process will stop, dump you in single
user mode and force you to run fsck.
[jumps up on journaled file system soap box]
This is why I recommend using ext3 or reiserfs. I have had my computer lock
up or the power go off with this system and it comes up and says something
like "oh, the computer went down and there were transactions outstanding,
hold on while I fix that". That is the power of a real operating system
something called "journaled file systems". There is the IBM jfs, reiserfs,
ext3, and a few others. What they do is protect the system from crashes and
unorderly shutdowns, by adding a new layer to the file system. They keep a
"journal" of transactions and if something unusual happens, the file system
isn't screwed up just maybe the journal. I don't know all the technical
details, and this may not be 100% correct, but it should give you an idea of
what the do. Someone else on the list may be able to explain it better.
[steps of soap box]
Brian
-----Original Message-----
From: Joshua B. Derck [mailto:JOSH@nph.com]
Sent: Friday, November 16, 2001 8:41 AM
To: Brian Densmore
Subject: RE: Unattached Inode
My Machine was lock this morning I could not shut it down properly what do
know
-----Original Message-----
From: Brian Densmore [mailto:DensmoreB@ctbsonline.com]
Sent: Friday, November 16, 2001 8:33 AM
To: Joshua B. Derck
Cc: KCLUG (E-mail)
Subject: RE: Unattached Inode
This is serious. You need to make sure you do an orderly shutdown before
turning off your PC. Hopefully you already do. This is an indication that
there is a problem with your file system. You need to run fsck "before you
dot another i Mr. Cratchit"! I also recommend that you run one of the more
robust file systems like ext3 or reiserfs. These help prevent these kinds of
issues. You should also run fsck anytime your system goes down.
Good luck,
Brian
-----Original Message-----
From: Joshua B. Derck [mailto:JOSH@nph.com]
Sent: Friday, November 16, 2001 8:14 AM
To: 'kclug@kclug.org'
Subject: Unattached Inode
Dose this sound fimilar to any one
Joshua B. Derck
IS Help Desk
Nazarene Publishing House
2923 Troost Ave.
Kansas City, MO 64141
816-931-1900 ext.429
josh@nph.com
--------------157BAA2AF01AAD9484619C3E