From: Fredrik Tolf <fredrik@dolda2000.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] fsck for LVM?
Date: Fri, 07 Apr 2006 04:03:51 +0200 [thread overview]
Message-ID: <1144375431.8601.66.camel@pc7.dolda2000.com> (raw)
In-Reply-To: <OF3B16C5BB.0FB8E06C-ON88257148.007618A5-88257148.0077796C@us.ibm.com>
On Thu, 2006-04-06 at 14:44 -0700, Graham Norris wrote:
> I've got a user complaining that his filesystem in an lv is being
> corrupted. It's not clear whether it is the lv that is corrupted or
> the filesystem, I've not actually seen it in this state. I have seen a
> fsck log from when it is formatted with reiserfs failing though.
>
> The user says he's tried both reiserfs and ext3 in this lv, and both
> end up corrupted after a period of time (days). Since this user
> obviously has root (or they couldn't format the lv), I have to suspect
> they're breaking their own filesystem. They, OTOH, seem to think it is
> LVM's fault and want me to fix it.
>
> Is there something which can be run on an LVM setup to verify its
> integrity in much the same way as fsck is used on file systems? I've
> used vgck, vgscan, vgdisplay, lvscan, lvdisplay, pvscan and pvdisplay
> on the various pieces, and can see no problems. I've also scanned the
> physical disk the pv lives on and that shows no problems either.
If I were you, I would firstly go about checking the physical integrity
of the hard drives themselves, and run memtest86 on the system (if it's
a PC, that is). Also, did you check the logs for any kernel messages
about it (filesystem warnings, etc.)?
That might just be me, though. Someone else might have a real idea. :)
Fredrik Tolf
prev parent reply other threads:[~2006-04-07 2:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 21:44 [linux-lvm] fsck for LVM? Graham Norris
2006-04-07 2:03 ` Fredrik Tolf [this message]
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=1144375431.8601.66.camel@pc7.dolda2000.com \
--to=fredrik@dolda2000.com \
--cc=linux-lvm@redhat.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).