Linux LVM users
 help / color / mirror / Atom feed
From: Rainer krienke <rainer@krienke.org>
To: linux-lvm@redhat.com,
	"Chris Doherty" <chris.doherty@adelaide.edu.au>,
	"Måns Rullgård" <mru@kth.se>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm]Re: corrupt /dev/lvm - bizzare properties
Date: Sun Feb  8 17:50:14 2004	[thread overview]
Message-ID: <200402081354.15872.rainer@krienke.org> (raw)
In-Reply-To: <1076241638.402624e656f43@pandani.services.adelaide.edu.au>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1313 bytes --]

Am Sonntag, 8. Februar 2004 13:00 schrieb Chris Doherty:
> Quoting Måns Rullgård <mru@kth.se>:
> > Chris Doherty <chris.doherty@adelaide.edu.au> writes:
> > > I've been using LVM happily for several months without any
> > > complaints or problems.  This morning that all changed.  The boot
> > > process stopped cold when lvm-mod (w|c)ouldn't load.  My first
> > > impulse was to fsck, which I did as a matter of course.  Eventually,
> > > I stumbled across what appears to be the source of my problem:
> > >
> > > root@connect4:~# ls -la /dev/lvm
> > > ?---rws-w-  8306 840966198 976250230 875573298 Sep 24  2004 /dev/lvm
> >
> > Your filesystem seems to have taken some heavy blows.  You should fsck
> > it properly.  You might need the -f flag to fsck to force a complete
> > check if filesystem is marked clean.
>
> the filesystem can't be mounted (which is the really worrying part) so i
> can't fsck it.
>

A filesystem that is to be fscked can and may *never* be mounted when 
performing an fsck. Usually all fsck tools won't do anything but stop if the 
filesystem (fsck was called for)  is currently mounted! If your root 
filesystem is corrupt boot from a rescue CD or similar and then check the 
filesystem. 

Have a nice day
Rainer
-- 
Rainer Krienke, rainer@krienke.org

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-02-08 12:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-08  1:00 [linux-lvm]corrupt /dev/lvm - bizzare properties Chris Doherty
2004-02-08  6:29 ` [linux-lvm]Re: corrupt " Måns Rullgård
2004-02-08  7:01   ` Chris Doherty
2004-02-08 17:50     ` Rainer krienke [this message]
2004-02-08  8:46       ` Chris Doherty
2004-02-08  8:51         ` Måns Rullgård
2004-02-08 22:29           ` Chris Doherty
2004-02-09  4:26             ` Måns Rullgård
2004-02-11  3:16             ` [linux-lvm] " Chris Doherty
2004-02-11 14:33               ` [linux-lvm] LVM Statistics John

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=200402081354.15872.rainer@krienke.org \
    --to=rainer@krienke.org \
    --cc=chris.doherty@adelaide.edu.au \
    --cc=linux-lvm@redhat.com \
    --cc=linux-lvm@sistina.com \
    --cc=mru@kth.se \
    /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