From: Kurt <kpalmer@advance.net>
To: reiserfs-list@namesys.com
Subject: Filesystem Corruption
Date: Thu, 06 Jun 2002 18:00:01 +0000 [thread overview]
Message-ID: <85256BD0.0062A314.00@patapsco.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1734 bytes --]
(Embedded
image moved Kurt <kpalmer@advance.net>
to file: 06/06/2002 02:00 PM
pic13835.pcx)
Hello all,
I currently have a system configured as follows :-
1) LVM version 1.0.1-rc4(ish)(03/10/2001)
2) /dev/PROJ/proj on /proj type reiserfs (rw,noatime,notail)
3) /dev/PROJ/proj 239G 142G 97G 60% /proj
4) 2.4.17 with reiserfs tools 3.x.0k
5) Reiserfs compiled in (CONFIG_REISERFS_CHECK set to NO)
6) 256 MB RAM ("sar -r" shows memory usage is not abnormal for this box)
7)Tuns of very small files based on log processing
I am told by my co-worker that the system unresponsive and showed reiserfs
related errors on the console.
Upon restart they noticed that the file
/proj/webtrends/receive/bama/www3/access.01Jun.r.gz was unreadable by root
(permission denied).
I did a reiserfsck on the drive and noticed that access.01Jun.r.gz returned an
error stating the file pointed to nowhere.
I was unable to complete a reiserfsck --fix-fixable because of the length of
time that this (fsck) process took since this was an unscheduled downtime.
During the weekend i will attempt to do the fsck again, however i really
needed to know if this problem has been observed by anyone else, and what
steps they took to fix the problem.
-Kurt
--
================================================
Kurt Palmer SysAdmin
kpalmer@advance.net Advance Internet
201-459-2846
next reply other threads:[~2002-06-06 18:00 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 18:00 Kurt [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-03 9:31 Filesystem Corruption Stefan Malte Schumacher
2018-12-03 11:34 ` Qu Wenruo
2018-12-03 16:29 ` remi
2014-10-31 0:29 filesystem corruption Tobias Holst
2014-10-31 1:02 ` Tobias Holst
2014-10-31 2:41 ` Rich Freeman
2014-10-31 17:34 ` Tobias Holst
2014-11-02 4:49 ` Robert White
2014-11-02 21:57 ` Chris Murphy
2014-11-03 3:43 ` Zygo Blaxell
2014-11-03 17:11 ` Chris Murphy
2014-11-04 4:31 ` Zygo Blaxell
2014-11-04 8:25 ` Duncan
2014-11-04 18:28 ` Chris Murphy
2014-11-04 21:44 ` Duncan
2014-11-04 22:19 ` Robert White
2014-11-04 22:34 ` Zygo Blaxell
2014-11-03 2:55 ` Tobias Holst
2014-11-03 3:49 ` Robert White
2011-01-03 1:58 Patrick H.
2011-01-03 3:16 ` Neil Brown
[not found] ` <4D214B5C.3010103@feystorm.net>
2011-01-03 4:56 ` Neil Brown
2011-01-03 5:05 ` Patrick H.
2011-01-04 5:33 ` NeilBrown
2011-01-04 7:50 ` Patrick H.
2011-01-04 17:31 ` Patrick H.
2011-01-05 1:22 ` Patrick H.
2011-01-05 7:02 ` CoolCold
[not found] ` <AANLkTinL_nz58f8rSPuhYvVwGY5jdu1XVkNLC1ky5A65@mail.gmail.com>
2011-01-05 14:28 ` Patrick H.
2011-01-05 15:52 ` Spelic
2011-01-05 15:55 ` Patrick H.
2007-06-06 3:10 Filesystem corruption Xu CanHao
2007-06-06 12:16 ` Ingo Bormuth
2007-05-30 20:13 devsk
2007-05-30 17:22 devsk
2007-05-30 19:24 ` Toby Thain
2007-05-30 20:03 ` David Masover
2007-05-31 0:11 ` Ingo Bormuth
2007-06-02 23:10 ` Edward Shishkin
2007-06-04 2:55 ` Ingo Bormuth
2007-06-04 9:41 ` Edward Shishkin
2007-06-05 23:20 ` Ingo Bormuth
2007-05-27 13:18 Laurent CARON
2007-05-28 12:23 ` Vladimir V. Saveliev
2007-05-28 14:10 ` Laurent CARON
2007-05-28 17:13 ` Vladimir V. Saveliev
2007-05-28 17:27 ` Laurent CARON
[not found] ` <Pine.LNX.4.64.0705280025570.10429@sheep.housecafe.de>
2007-05-28 17:31 ` Christian Kujau
2007-05-28 18:16 ` Laurent CARON
2007-05-28 23:19 ` Christian Kujau
2007-05-29 8:39 ` Vladimir V. Saveliev
[not found] ` <465BA9AC.8040805@ultraviolet.org>
2007-05-29 8:15 ` Vladimir V. Saveliev
2007-05-29 12:36 ` Toby Thain
2007-05-30 13:25 ` David Masover
2007-05-30 16:02 ` Vladimir V. Saveliev
2007-05-30 20:06 ` David Masover
2007-05-30 16:42 ` Toby Thain
2007-05-30 19:42 ` David Masover
2007-05-30 16:08 ` Vladimir V. Saveliev
2003-08-13 16:05 Locke
2003-08-14 7:49 ` Oleg Drokin
2002-09-05 15:57 Filesystem Corruption Brian Tinsley
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-06 18:00 Kurt
2002-06-07 7:15 ` Oleg Drokin
2002-06-11 16:49 ` Kurt
2001-02-05 16:00 Filesystem corruption Ian Chilton
2001-02-05 13:16 Ian Chilton
2001-01-31 14:20 Carsten Langgaard
2001-01-31 15:52 ` Florian Lohoff
2001-01-31 16:24 ` Carsten Langgaard
2001-01-31 16:48 ` Florian Lohoff
2001-02-05 10:02 ` Ralf Baechle
2001-02-05 12:10 ` Alan Cox
2001-02-05 12:10 ` Alan Cox
2001-02-05 12:56 ` Geert Uytterhoeven
2001-02-05 13:01 ` Alan Cox
2001-02-05 13:01 ` Alan Cox
2001-02-05 22:01 ` Ralf Baechle
2001-02-05 22:01 ` Ralf Baechle
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=85256BD0.0062A314.00@patapsco.com \
--to=kpalmer@advance.net \
--cc=reiserfs-list@namesys.com \
/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.