I have a ThinkPad 560, 24/2.1, with a new RedHat 5.0 (2.0.30, I think)
installation and a Windows partition...  right now I'm running Windows,
because Linux just died on me and I can't get it back up...

I had an ongoing problem where "shutdown -h now" would always complain
that it couldn't umount /dev/hda4 because /usr was busy, even though
-- fuser -k /usr returned nothing right before typing shutdown, and
-- I added "mount -o remount,ro /dos" and "mount -o remount,ro /usr"
   to /etc/rc.d/init.d/halt right before "umount -a".
This meant that the system was never properly halted and had to be
switched off, after which fsck would run on reboot (normally just fixing
a few problems on its own, or not finding any problems).  I hadn't
succeeded in resolving this problem when...

...this morning, fsck dropped me into a shell to run fsck "MANUALLY (i.e.,
without -a or -p options".  So I did (e2fsck /dev/hda4).  After several
hundred pages of (if I recall correctly) unattached inodes (I just kept
the "y" key pressed until it was done), it came to

--------------------------------------------------------------
Pass 4: Checking reference counts
Unattached inode 370009
Connect to /lost+found<y>? yes

No room in lost+found directory.  Expand<y>? yes

Segmentation fault (core dumped)
[root@localhost /root]#
--------------------------------------------------------------

The funny thing is

[root@localhost /root]# df
Filesystem         1024-blocks  Used Available Capacity Mounted on
/dev/hda2              99539   50894    43505     54%   /

..so you would think there would be some space in /lost+found.  :(

If anyone has any idea how to go about fixing this, short of wiping it and
reinstalling from scratch, I'd be very grateful if you'd email me at
[EMAIL PROTECTED]

Thanks!
Rohan.


-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
         To unsubscribe: mail [EMAIL PROTECTED] with 
                       "unsubscribe" as the Subject.

Reply via email to