From: Jasmeet Sidhu <jsidhu@arraycomm.com>
To: linux-kernel@vger.kernel.org (Linux Kernel)
Subject: Rebooting a system with a bad filesystem (2.4.2 + ReiserFS)
Date: Tue, 20 Mar 2001 11:15:31 -0800 [thread overview]
Message-ID: <5.0.2.1.2.20010320110527.022dfe28@pop.arraycomm.com> (raw)
Hi guys,
I have a system here with the following setup:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda3 19072868 6260156 11843848 35% /
/dev/hda1 198313 18161 169898 10% /boot
/dev/md0 525461076 89626136 435834940 18% /raid
/raid is the reiserfs volume. / is ext2.
The only thing on /raid is some pcbackup stuff. The system entirely runs
from the root drive (ext2 filesystem).
Lately, reiserfs has been giving me problems. If I try to do anything on
/raid - like vi a text file, the kernel will oops. But the system will
stay up. All the services are there, and I can login.
However, I cannot unmount the partition, or do anythinh else. Even if I
call sync, it never returns. I can't even reboot the system, or shutdown
my nfs services. Since all of the stuff is on the root drive, shouldn't
linux be able to cope with such a situation? I know that filesystems do
get corrupted every now and then, especially if they are in the beta
stage. But such a malfunction should not keep the whole system from being
shutdown.
The only way now is to hit the magic reset button. With this, I loose a
lot of data. I dont know when sync was called last, but when I tried to
call it manually, it never returned.
All the processes that are dealing with the /raid partition, are in STATE
D, uninterruptible sleep, and cannot be killed.
root 828 46.7 11.0 29628 28172 ? D 02:00 258:15
/opt/legato/usr/sbin/save -s lester.arraycomm.com -g Linux Servers -LL -f -
-m bertha.arraycomm.com -l full -q -W 78 -N /raid /raid
root 1599 0.0 0.2 1452 548 pts/4 D 10:40 0:00 umount /dev/md0
root 1634 0.0 0.2 1452 548 pts/6 D 10:45 0:00 umount /dev/md0
I'd appreciate any help. Thank you.
Jasmeet.
reply other threads:[~2001-03-20 19:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.0.2.1.2.20010320110527.022dfe28@pop.arraycomm.com \
--to=jsidhu@arraycomm.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox