From: Pavel Machek <pavel@suse.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: ext2fs corruption again
Date: Sun, 16 Sep 2001 21:33:53 +0200 [thread overview]
Message-ID: <20010916213353.E216@bug.ucw.cz> (raw)
In-Reply-To: <3BA3156C.9050704@korseby.net> <20010915144236.V26627@khan.acc.umu.se> <20010916001943.A984@bug.ucw.cz> <20010915175100.D1541@turbolinux.com>
In-Reply-To: <20010915175100.D1541@turbolinux.com>; from Andreas Dilger on Sat, Sep 15, 2001 at 05:51:00PM -0600
Hi!
> > Install crc loop device, and if disk does silent errors, you'll know.
>
> Where do you store the CRCs? It appears that they are written to another
> block device. Also, how do you initialize the CRC table for an existing
> filesystem?
You just read the device in special mode. That forces it to recompute
crc-s.
> What would make this considerably more useful is to be able to write the
> CRCs into a regular file, as it would be a bit of a pain to have a partition
> for each CRC loop device to store the CRCs in.
By -o loop, you can turn regular file into blockdevice ;-).
> Otherwise, it looks very useful, and could be handy in tracking down
> reports like this where it is unclear where the data corruption is.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
next prev parent reply other threads:[~2001-09-16 19:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-15 8:46 ext2fs corruption again Kristian
2001-09-15 12:42 ` David Weinehall
2001-09-15 17:19 ` David Rees
2001-09-15 17:55 ` Kristian Peters
2001-09-15 22:19 ` Pavel Machek
2001-09-15 23:51 ` Andreas Dilger
2001-09-16 19:33 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-15 10:44 Kristian
2001-09-15 11:14 Kristian Peters
2001-09-15 12:21 ` Roeland Th. Jansen
2001-09-15 14:49 ` Kristian
2001-09-15 21:04 ` Mike Fedyk
2001-09-15 15:48 ` Mohammad A. Haque
2001-09-15 16:19 ` Kristian Peters
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=20010916213353.E216@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.