From: "Måns Rullgård" <mru@kth.se>
To: Chris Doherty <chris.doherty@adelaide.edu.au>
Cc: Rainer krienke <rainer@krienke.org>,
linux-lvm@redhat.com, linux-lvm@sistina.com
Subject: [linux-lvm]Re: corrupt /dev/lvm - bizzare properties
Date: Sun Feb 8 08:51:03 2004 [thread overview]
Message-ID: <yw1xbro9u1c7.fsf@kth.se> (raw)
In-Reply-To: <1076247930.40263d7a87098@pandani.services.adelaide.edu.au> (Chris Doherty's message of "Mon, 9 Feb 2004 00:15:30 +1030")
Chris Doherty <chris.doherty@adelaide.edu.au> writes:
>> > > > 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
>
> oops, sorry my last statement was ambiguous. what i meant was that the
> filesystem can't be mounted *and* fsck refuses to acknowledge that it is (or
> was?) a filesystem.
The filesystem containing /dev has been damaged somehow. You should
fsck it. Most likely fsck will remove /dev/lvm so you'll have to
recreate it with proper values. Don't just rm it. Something bad has
obviously happened and changing things without a proper fsck can make
things worse.
--
M�ns Rullg�rd
mru@kth.se
next prev parent reply other threads:[~2004-02-08 13:51 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
2004-02-08 8:46 ` Chris Doherty
2004-02-08 8:51 ` Måns Rullgård [this message]
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=yw1xbro9u1c7.fsf@kth.se \
--to=mru@kth.se \
--cc=chris.doherty@adelaide.edu.au \
--cc=linux-lvm@redhat.com \
--cc=linux-lvm@sistina.com \
--cc=rainer@krienke.org \
/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