From: Patrick Boutilier <boutilpj@ednet.ns.ca>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] e2fsck on logical volume?
Date: Mon, 12 Mar 2001 15:43:11 -0400 [thread overview]
Message-ID: <3AAD26CF.4AA5EC86@ednet.ns.ca> (raw)
In-Reply-To: F36jtQUGUzLhG4YalgQ0000abf4@hotmail.com
All you should have to do is unmount the ext2 filesystem in question and then
run e2fsck on it. The filesystem level is above the LV level so there should be
no problem there. Unless I am missing something LVM should not interfere with
or care about the filesystem running on top of it.
hail narcissus wrote:
> I asked a similar question a little while back and was told all I can run is
> vgck. So I just ignored the warning message on bootup:
>
> EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
>
> Well I've extended my Logical Volume and I was just about done. Until I
> tried to run 'ext2resize'. It gives me a warning message about problems
> with my EXT2 partition and to run e2fsck.
>
> I figure I can do a force with ex2resize or I can run umount my volume and
> run e2fsck. Me not being all that bold with 500 gigs of data that hasn't
> been backed up, I have done neither.
>
> I would think the best thing would be to umount my volume and run e2fsck,
> but I don't know if that is going to destroy my logical volume or if it is
> all compatible.
>
> Thanks!!
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
next prev parent reply other threads:[~2001-03-12 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-12 19:07 [linux-lvm] e2fsck on logical volume? hail narcissus
2001-03-12 19:43 ` Patrick Boutilier [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-12 19:49 hail narcissus
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=3AAD26CF.4AA5EC86@ednet.ns.ca \
--to=boutilpj@ednet.ns.ca \
--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).