l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2003 Feb 12 10:49

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [Fwd: [vox-tech] corrupted ext3 filesystem]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Fwd: [vox-tech] corrupted ext3 filesystem]

hi jonathan,

i think people didn't respond because nobody really had an answer.  i
sure don't.  some ideas to be tossed around:

* have you googled for the problem of umount errors during shutdown?

* does anyone know if there are any issues with winxp causing problems
   for non-MS filesystems?

* perhaps the first thing to try would be to experiment mounting and
   umounting partitions on your own.  start by fscking all your
   partitions so you know you're starting with a clean slate.  start to
   experiment with umounting things like /home, /var (in single user
   mode), remounting root as read only.  stuff like that.   see if you
   can REPRODUCE the error.  if you can reproduce the error under
   controlled circumstances, that's a big step in solving the problem.

* you say that you occaisionally get umount errors but they fly across
   the screen too quickly to be wrote down.  personally, i've found that
   when that happens to me, a nice digital camera (turn the flash off)
   will help capture the messages.


begin Jonathan Stickel <jjstickel@netscape.net> 
> -------- Original Message --------
> Subject: [vox-tech] corrupted ext3 filesystem
> Date: Tue, 11 Feb 2003 16:03:32 -0800
> From: Jonathan Stickel <jjstickel@netscape.net>
> Reply-To: vox-tech@lists.lugod.org
> To: vox-tech <vox-tech@lists.lugod.org>
> Thanks, Pete, for correctly guessing that my xmms/rpm problems were due
> to a corrupted filesystem.  I have managed to fix the filesystem with
> fsck (many, many errors) and reload the two affected programs with rpm.
> I would like to solicit some help and comments about what may have
> caused my system to become corrupt and how to prevent this from
> happening in the future.  Please know that I am relatively new to Linux.
> A while back I posted a message asking about some occasional umount
> errors during shutdown.  My post must have seemed uninteresting because
> no one responded, which was fine because it didn't seem to be causing
> any problems.  However, I now wonder if this is related my filesystem
> corrupting on me.  Every time I shutdown or reboot, I get this message:
> kjournald[150] exited with preempt count 1
> _Occasionaly_  I get half a dozen umount and umount2 errors that fly by
> so quickly I can't write them down.  As I posted before, I am not able
> to find a system log file with these shutdown messages either.  During
> bootup of Linux after these umount errors, it lets me know that there
> was a problem and does a filesystem check.  This was actually how I was
> able to run fsck today to fix the problem.
> Does anyone know if these types of messages are common?  Could they be
> related to a filesystem corrupting?
> I should mention that my machine is a laptop which does get jostled
> quite a bit during my bike commute.  In the old days of DOS, I remember
> "parking" hardrives on shutdown to prevent damage.  Is this at all
> related to unmounting filesystems on shutdown?  I am definitely showing
> my ignorance here.
> _______________________________________________
> I meant to also add these points.  Pete suggested I look in my system 
> logs for "diskseek" errors.  The only thing I thought was close was this 
> error:
> Feb 11 09:07:24 chms-hp4 kernel: isofs_read_super: bread failed, 
> dev=0b:00, iso_blknum=16, block=16
> This error did occur at about the time of my first noticeable problem.
> Also, my system is dual boot WinXP pro, and RH8, with a custom kernal. 
> The mounted partitions are:
> Filesystem    Type    Size  Used Avail Use% Mounted on
> /dev/hda3     ext3    6.2G  3.2G  2.7G  54% /
> /dev/hda2     ext3     99M   13M   81M  14% /boot
> none         tmpfs    235M     0  235M   0% /dev/shm
> /dev/hda5     vfat    5.8G  2.3G  3.5G  40% /Documents
> with /dev/hda1 being WinXP, which I normally do not mount.
> Thanks in advance for reading this long message and for any comments you 
> have.
> Jonathan
> _______________________________________________
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech

First they ignore you, then they laugh at you, then they fight you,
then you win. -- Gandhi, being prophetic about Linux.

Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D
vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Appahost Applications
For a significant contribution towards our projector, and a generous donation to allow us to continue meeting at the Davis Library.