From: Wolfgang Weisselberg <weissel@netcologne.de>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] read_intr errors
Date: Thu, 18 Oct 2001 02:09:32 +0200 [thread overview]
Message-ID: <20011018020932.A18634@tiger.bigcats.invalid> (raw)
In-Reply-To: <000901c15751$8839ee70$0300000a@pacbell.net>; from e@arix.com on Wed, Oct 17, 2001 at 02:20:23PM -0700
Hi, Erick!
Erick Calder (e@arix.com) wrote:
> From Karl
> > Have you tried mke2fs with the -c option in LVM and on the drive without
> I haven't tried that but if I unmount the filesystem and check it:
> # umount /dev/LVM/mp3z
> # fsck /dev/LVM/mp3z
> it comes up clean.... is that not an equivalent test?
No. Definitively not. mke2fs -c also runs badblocks(8),
which tries to read every single byte in the partition.
(Optionally you can even have it do a write test. There is
even a non-destructive write test in newer badblocks. Use with
care and do have current backups.)
fsck just checks that the metadata (directories, space used
by files, etc) looks OK.
-Wolfgang
next prev parent reply other threads:[~2001-10-18 0:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-17 20:21 [linux-lvm] read_intr errors Karl
2001-10-17 21:20 ` Erick Calder
2001-10-18 0:09 ` Wolfgang Weisselberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-24 11:36 Karl
2001-10-17 22:27 Karl
2001-10-16 21:40 [linux-lvm] Remount a LVM Vol after a system crash Heinz J . Mauelshagen
2001-10-17 9:27 ` [linux-lvm] read_intr errors Erick Calder
2001-10-17 14:29 ` Patrick Caulfield
2001-10-17 20:08 ` Erick Calder
2001-10-18 7:42 ` Patrick Caulfield
2001-10-23 23:19 ` Erick Calder
2001-10-24 4:25 ` Patrick Caulfield
2001-10-26 2:13 ` Erick Calder
2001-10-26 3:29 ` Patrick Caulfield
2001-10-26 16:16 ` Erick Calder
2001-10-30 2:55 ` Patrick Caulfield
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=20011018020932.A18634@tiger.bigcats.invalid \
--to=weissel@netcologne.de \
--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