From: Theodore Tso <tytso@mit.edu>
To: "Jason A. Lixfeld" <jlixfeld@fastvibe.com>
Cc: ext3-users@redhat.com, linux-lvm@sistina.com
Subject: [linux-lvm] Re: What really works?
Date: Mon Oct 22 14:37:01 2001 [thread overview]
Message-ID: <20011022153819.A2744@thunk.org> (raw)
In-Reply-To: <002501c15a66$34f8d010$836788cf@industry>; from jlixfeld@fastvibe.com on Sun, Oct 21, 2001 at 03:25:56PM -0400
On Sun, Oct 21, 2001 at 03:25:56PM -0400, Jason A. Lixfeld wrote:
> Previous attempts at stock kernels and
> various LVM/EXT3/FastTrack patches resulted in all kinds of errors
> ranging from ATARAID errors to LVM errors to physical hard drive errors.
If you see physical disk errors or LVM errors, it's likely that the
filesystem may have been corrupted. Sometimes the filesystem
corruption may not be noticeable until much later, and the longer you
wait, the worse your data may get scrambled. So if you were seeing
all sorts of disk or LVM errors, don't just assume that the problems
all went away when you moved to a "stable" kernel.
So after seeing this kind of disk problems, *always* run fsck -f to
make sure the filesystem is in a sane state before you continue. Any
journaling filesystem, like ext3, will protect you against needing to
run fsck after an unclean shutdown, but they all won't save you if you
have low-level disk/LVM errors. In those cases, you still need to
have a filesystem checker to try to pick up the pieces caused by
hardware problems, kernel bugs, etc.
> One of the lost+founds is stuck on my LVM and I can't delete it.
> Every time I try, it gives me permission denied errors. Chattr -I
> doesn't work either (that's another problem, how the hell do I get
> rid of all that stuff in there now).
It's "chattr -i" (case matters).
Also, what version of e2fsprogs are you using? Recent versions should
have offered to get rid of corrupted files for you.
> Why is all this happening? What do I need to do to get this all
> working? This isn't complicated, is it? 10 drives, 3 LVMs and one
> ATARAID?!
Umm.... you're using bleeding edge 2.4 kernels, LVM's, and ext3? Err,
yeah, this is still complicated. Given all of the changes going into
the kernel, even though a lot of work had gone into making earlier
versions of LVM and ext3 play nicely together, your milage may
definitely vary (and I haven't even included the ATARAID aspects).. I
wouldn't put any production data on it just yet, until things have
done a little settling down.
- Ted
next prev parent reply other threads:[~2001-10-22 14:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E15vISM-0005YX-00.2001-10-21-14-15-58@mail5.svr.pol.co.uk>
2001-10-21 14:25 ` [linux-lvm] What really works? Jason A. Lixfeld
2001-10-22 14:37 ` Theodore Tso [this message]
2001-10-22 14:42 ` [linux-lvm] " Bryan-TheBS-Smith
2001-10-22 21:13 ` [linux-lvm] " Jason A. Lixfeld
2001-10-23 5:35 ` [linux-lvm] " Stephen C. Tweedie
2001-10-22 17:04 ` Stephen C. Tweedie
2001-10-22 17:22 ` Andreas Dilger
2001-10-23 5:32 ` Stephen C. Tweedie
2001-10-23 4:42 ` Joe Thornber
2001-11-02 9:40 ` Stephen C. Tweedie
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=20011022153819.A2744@thunk.org \
--to=tytso@mit.edu \
--cc=ext3-users@redhat.com \
--cc=jlixfeld@fastvibe.com \
--cc=linux-lvm@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).