All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Amit D. Chaudhary" <amit_ml@comcast.net>
To: fedora-list@redhat.com, linux-kernel@vger.kernel.org
Subject: ext3 filesystem corruption with Fedora Core 2, Test 3 with latest 2.6.6.x kernel
Date: Thu, 29 Jul 2004 18:11:55 -0700	[thread overview]
Message-ID: <4109A05B.6080900@comcast.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]

What happened:
I got filesystem corrupted yesterday when using a Fedora Core 3, Test 3 
with linux kernel 2.6.6-1.435.

The filesystems were /boot and /, particularly files under /bin were 
missing including /bin/sh, /etc/fstab, etc.
kernel images, and other files under /boot had disappeared.

Setup:
The desktop is a HP with a P3 700 with 512 MB RAM, 2 HDD, this happenned 
on ide0 (hda1 and hda3)
The ext3 filesystems had the default journaling mode.

How I ran into it:
I ran vncserver from one of the mingetty (text) consoles, I am still 
trying it out and probably used an incorrect xstartup, attached incase 
it might be useful. Anyways, I did not connect to it, decided to log 
onto another mingetty (CTRL+ALT+2), this took the login name and hung. 
Now the computer went into a hard hang (No Oops, CTRL+ALT+DEL, etc did 
not work.)
On a reboot using grub directly went into Windows (it is a dual boot 
system). Using the rescue disk, I noticed, since it did not mount 
/dev/hda1 as /boot, the old /boot was being effective and suprisingly 
did not have a link entry.

I have reinstalled the OS, so no direct help is needed.
Thought should email it to the list for information and if someone knows 
which release this happens in and is there a fix to it.

Thanks
Amit

[-- Attachment #2: xstartup --]
[-- Type: text/plain, Size: 653 bytes --]

#!/bin/sh

# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
#Original commands
#xsetroot -solid grey
#vncconfig -iconic &
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
#twm &

#/usr/bin/gdm-binary  -nodaemon&
/usr/bin/gnome-keyring-daemon&
metacity&
/usr/libexec/gnome-settings-daemon&
xscreensaver -nosplash&
magicdev&
#nautilus&
gnome-panel&
eggcups&

konsole&

/usr/libexec/gnome-vfs-daemon&
dcopserver --nosid --suicide&
/usr/libexec/mapping-daemon&
kded&
klauncher&

                 reply	other threads:[~2004-07-30  1:16 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=4109A05B.6080900@comcast.net \
    --to=amit_ml@comcast.net \
    --cc=fedora-list@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.